H
harishsg993010/damn-vulnerable-MCP-server
Damn Vulnerable MCP Server
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# Damn Vulnerable Model Context Protocol (DVMCP)
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
A deliberately vulnerable implementation of the Model Context Protocol (MCP) for educational purposes.
## Overview
The Damn Vulnerable Model Context Protocol (DVMCP) is an educational project designed to demonstrate security vulnerabilities in MCP implementations. It contains 15 challenges of increasing difficulty that showcase different types of vulnerabilities and attack vectors.
This project is intended for security researchers, developers, and AI safety professionals to learn about potential security issues in MCP implementations and how to mitigate them.
## What is MCP?
The Model Context Protocol (MCP) is a standardized protocol that allows applications to provide context for Large Language Models (LLMs) in a structured way. It separates the concerns of providing context from the actual LLM interaction, enabling applications to expose resources, tools, and prompts to LLMs.
## Recommended MCP Clients
CLINE - VSCode Extension
Refer to this Connecting to a Remote Server - Cline for connecting Cline with MCP server
## Quick Start
Once you have cloned the repository, run the following commands:
sh
docker build -t dvmcp .
docker run -p 9001-9015:9001-9015 dvmcp
Each challenge is a Streamable HTTP MCP server. Challenge 1 is http://localhost:9001/mcp, and the rest follow through port 9015.
## Disclaimer
It's not stable in a Windows environment. If you don't want to use Docker then please use Linux environment.
I recommend Docker to run the LAB and I am 100% percent sure it works well in the Docker environment
## Security Risks
While MCP provides many benefits, it also introduces new security considerations. This project demonstrates various vulnerabilities that can occur in MCP implementations, including:
1. Prompt Injection: Manipulating LLM behavior through malicious inputs
2. Tool Poisoning: Hiding malicious instructions in tool descriptions
3. Excessive Permissions: Exploiting overly permissive tool access
4. Rug Pull Attacks: Exploiting tool definition mutations
5. Tool Shadowing: Overriding legitimate tools with malicious ones
6. Indirect Prompt Injection: Injecting instructions through data sources
7. Token Theft: Exploiting insecure token storage
8. Malicious Code Execution: Executing arbitrary code through vulnerable tools
9. Remote Access Control: Gaining unauthorized system access
10. Multi-Vector Attacks: Combining multiple vulnerabilities
## Project Structure
damn-vulnerable-MCP-server/
├── README.md # Project overview
├── requirements.txt # Python dependencies
├── challenges/ # Challenge implementations
│ ├── easy/ # Easy difficulty challenges (1-3)
│ │ ├── challenge1/ # Basic Prompt Injection
│ │ ├── challenge2/ # Tool Poisoning
│ │ └── challenge3/ # Excessive Permission Scope
│ ├── medium/ # Medium difficulty challenges (4-7)
│ │ ├── challenge4/ # Rug Pull Attack
│ │ ├── challenge5/ # Tool Shadowing
│ │ ├── challenge6/ # Indirect Prompt Injection
│ │ └── challenge7/ # Token Theft
│ └── hard/ # Hard difficulty challenges (8-10)
│ ├── challenge8/ # Malicious Code Execution
│ ├── challenge9/ # Remote Access Control
│ └── challenge10/ # Multi-Vector Attack
├── docs/ # Documentation
## Overview
The Damn Vulnerable Model Context Protocol (DVMCP) is an educational project designed to demonstrate security vulnerabilities in MCP implementations. It contains 15 challenges of increasing difficulty that showcase different types of vulnerabilities and attack vectors.
This project is intended for security researchers, developers, and AI safety professionals to learn about potential security issues in MCP implementations and how to mitigate them.
## What is MCP?
The Model Context Protocol (MCP) is a standardized protocol that allows applications to provide context for Large Language Models (LLMs) in a structured way. It separates the concerns of providing context from the actual LLM interaction, enabling applications to expose resources, tools, and prompts to LLMs.
## Recommended MCP Clients
CLINE - VSCode Extension
Refer to this Connecting to a Remote Server - Cline for connecting Cline with MCP server
## Quick Start
Once you have cloned the repository, run the following commands:
sh
docker build -t dvmcp .
docker run -p 9001-9015:9001-9015 dvmcp
Each challenge is a Streamable HTTP MCP server. Challenge 1 is http://localhost:9001/mcp, and the rest follow through port 9015.
## Disclaimer
It's not stable in a Windows environment. If you don't want to use Docker then please use Linux environment.
I recommend Docker to run the LAB and I am 100% percent sure it works well in the Docker environment
## Security Risks
While MCP provides many benefits, it also introduces new security considerations. This project demonstrates various vulnerabilities that can occur in MCP implementations, including:
1. Prompt Injection: Manipulating LLM behavior through malicious inputs
2. Tool Poisoning: Hiding malicious instructions in tool descriptions
3. Excessive Permissions: Exploiting overly permissive tool access
4. Rug Pull Attacks: Exploiting tool definition mutations
5. Tool Shadowing: Overriding legitimate tools with malicious ones
6. Indirect Prompt Injection: Injecting instructions through data sources
7. Token Theft: Exploiting insecure token storage
8. Malicious Code Execution: Executing arbitrary code through vulnerable tools
9. Remote Access Control: Gaining unauthorized system access
10. Multi-Vector Attacks: Combining multiple vulnerabilities
## Project Structure
damn-vulnerable-MCP-server/
├── README.md # Project overview
├── requirements.txt # Python dependencies
├── challenges/ # Challenge implementations
│ ├── easy/ # Easy difficulty challenges (1-3)
│ │ ├── challenge1/ # Basic Prompt Injection
│ │ ├── challenge2/ # Tool Poisoning
│ │ └── challenge3/ # Excessive Permission Scope
│ ├── medium/ # Medium difficulty challenges (4-7)
│ │ ├── challenge4/ # Rug Pull Attack
│ │ ├── challenge5/ # Tool Shadowing
│ │ ├── challenge6/ # Indirect Prompt Injection
│ │ └── challenge7/ # Token Theft
│ └── hard/ # Hard difficulty challenges (8-10)
│ ├── challenge8/ # Malicious Code Execution
│ ├── challenge9/ # Remote Access Control
│ └── challenge10/ # Multi-Vector Attack
├── docs/ # Documentation
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/harishsg993010-damn-vulnerable-mcp-server/)
- Source
- awesome · https://github.com/harishsg993010/damn-vulnerable-MCP-server
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.