Provides a comprehensive security framework and testing methodology for evaluating Model Context Protocol implementations and boundaries.
Also known as OWASP/MCP-Security-Testing-Guide
- Stars
- 62
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 9, 2026
- License
- GPL-3.0
What is OWASP MCP Security Testing Guide MCP?
OWASP MCP Security Testing Guide provides a comprehensive security framework and testing methodology for evaluating Model Context Protocol implementations and boundaries.
Summary generated from the project's README
About OWASP MCP Security Testing Guide MCP server
Evaluating the security boundaries of Model Context Protocol implementations is the primary function of this resource. It serves developers, AppSec professionals, red teams, and SOC teams by providing a structured framework to analyze the entire connection chain from the user and model through the client to the server and target system.
Users can access a collection of security knowledge including threat taxonomies, secure development practices, and incident response strategies. The guide features eighty specific tests located within the third chapter to help identify attack patterns. It also includes review checklists, case studies, and guidance on using safe lab fixtures or synthetic environments for testing purposes. This framework helps teams identify vulnerabilities in host and client controls, supply chain security, and enterprise gateways.
What you can do with it
- 1Perform security testingA red team can execute eighty specific tests to identify vulnerabilities in an MCP implementation.
- 2Develop secure MCP applicationsDevelopers can follow established methodologies to build more secure connections between LLMs and external tools.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableowasp/mcp-security-testing-guide is public and reachablegithub.com/owasp/mcp-security-testing-guide ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)GPL-3.0spdx.org/licenses/GPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-09github.com/owasp/mcp-security-testing-guide ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubOWASP MCP Security Testing Guide
The Model Context Protocol (MCP) is an open protocol that lets LLM applications connect to external data sources, tools, prompts, workflows, and services. This guide treats MCP as a security boundary: the chain from the user, through the model and MCP client, to the MCP server, the connected tool, and the target system.
It is a living collection of MCP security knowledge for developers, AppSec, red teams, and SOC teams. It covers threats, secure development, host and client controls, supply chain, enterprise gateways, detection, incident response, taxonomy, public incidents, case studies, and review checklists. Host and client controls are in Chapter 3.
This work is licensed under GPL-3.0.
Chapters
Read the guide in this order. Chapter 3 holds the threat write-ups and 80 tests in sections 3.1–3.19.
- Project Overview
- MCP Fundamentals
- MCP Threats and Attack Patterns
- Secure MCP Development
- MCP Security Taxonomy
- Hacks, News, and Public Incidents
- Appendix A — Glossary
- Appendix B — Suggested Reading
- Appendix C — Security Review
- Appendix D — Safe Lab Fixtures
- Appendix F — Testing Tools
Do not use it to test systems without explicit written authorization. Use synthetic lab environments and placeholders or try this MCP Goat
Related OWASP projects
Appendix E is unused so the Appendix D and Appendix F links already used by the Chapter 3 tests stay stable. Report a finding with the finding template and Appendix C.
OWASP MCP Security Testing Guide MCP questions
What does this guide cover?
It covers threats, secure development, host and client controls, supply chain, enterprise gateways, detection, incident response, taxonomy, public incidents, case studies, and review checklists.
How many security tests are included in the guide?
Chapter 3 contains 80 specific security tests distributed across sections 3.1 to 3.19.
Is it safe to use this guide to test live systems?
No, you should not use it to test systems without explicit written authorization; instead, use synthetic lab environments or MCP Goat.