mcp-implementation-security-review
Review the implementation source code of MCP (Model Context Protocol) servers, clients, and tool handlers against a security baseline — authentication, sessions, rate limiting, input-schema validation, official-SDK usage, RCE vectors, and the OWASP MCP Top 10 — producing a report with file/line evidence. Use this skill when: - Reviewing an MCP server implementation for security before release - Checking a server against the baseline controls (MCP-01 to MCP-05) and the OWASP MCP Top 10 - Auditing tools for RCE vectors (command/code injection, unsafe deserialization, path traversal, SSTI, depend
Profile →npx skills add github/awesome-copilot --skill mcp-implementation-security-review --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MCP Implementation Security Review ## Process ### Step 1 — Classify the target - Check **MCP protocol version [2025-03-26](https://modelcontextprotocol.io/specification/2025-03-26) or later** (current: [2025-11-25](https://modelcontextprotocol.io/specification/2025-11-25)). Flag older versions as a finding but continue the review. - Determine whether the target is a **server** or **client**. - Classify transport as **network-exposed** or **local-only** using the transport reference below. - Record transport, protocol version, and whether sessions exist. **Completion criterion:** Target type, protocol status, and transport are identified. ### Step 2 — Filter false positives - Apply the **False Positive Filters** before opening findings. - Keep docs only when they describe the repo's own server behavior, deployment, transport, or auth posture. - For framework/SDK repositories, scope findings to the **default configuration** and **public API surface**. **Completion criterion:** Remaining evidence is in-scope code, repo-owned docs, or public API behavior. ### Step 3 — Check baseline controls - For **network-exposed servers**, check **MCP-01** through **MCP-05**. - For **local/STDIO s
- Process
- Step 1 — Classify the target
- Step 2 — Filter false positives
- Step 3 — Check baseline controls
- Step 4 — Check RCE vectors
- Step 5 — Check OWASP MCP Top 10
- Step 6 — Report
- Reference
- Decision rules
- Transport classification
- False Positive Filters
- Controls Reference
- MCP-01 — Identity isolation
- MCP-02 — Sessions
What does the mcp-implementation-security-review skill do?
Review the implementation source code of MCP (Model Context Protocol) servers, clients, and tool handlers against a security baseline — authentication, sessions, rate limiting, input-schema validation, official-SDK usage, RCE vectors, and the OWASP MCP Top 10 — producing a report with file/line evidence. Use this skill when: - Reviewing an MCP server implementation for security before release - Checking a server against the baseline controls (MCP-01 to MCP-05) and the OWASP MCP Top 10 - Auditing tools for RCE vectors (command/code injection, unsafe deserialization, path traversal, SSTI, depend
How do I install it?
Run `npx skills add github/awesome-copilot --skill mcp-implementation-security-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.