MCPProxy
Local-first MCP proxy with BM25 tool discovery, security scanning, quarantine & ~99% token savings
Description from the maker (original English)
Security scanner for MCP servers. SSRF, path traversal, injection, auth, secrets. Grade A-F.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"shield": {
"command": "npx",
"args": [
"-y",
"@sophiacave/mcp-shield"
]
}
}
}Run this in your terminal
claude mcp add shield -- npx -y @sophiacave/mcp-shieldPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"shield": {
"command": "npx",
"args": [
"-y",
"@sophiacave/mcp-shield"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"shield": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sophiacave/mcp-shield"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account sophiacave, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.7) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: MCPProxy, ConnectSecure MCP, EchelonGraph CVE & Exposure
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Local-first MCP proxy with BM25 tool discovery, security scanning, quarantine & ~99% token savings
Vulnerability management across all ConnectSecure clients: exposure ranking, CVE impact, blind spots
CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Open-source security scanner for MCP servers. 20 rules across 6 categories. Scan any server in seconds. Get a grade from A to F.
36.7% of MCP servers are SSRF-vulnerable (BlueRock, 2026). 82% have path traversal flaws. Only 17% are production-ready. MCP Shield finds the vulnerabilities before attackers do.
git clone https://github.com/sophiacave/mcp-shield
cd mcp-shield
python3 src/cli.py scan path/to/mcp_server.py
python3 src/cli.py scan path/to/mcp-project/
| Rule | Severity | What It Detects |
|---|---|---|
| SSRF-01 | Critical | User input in HTTP request URLs |
| SSRF-02 | Medium | Dynamic URLs without validation |
| SSRF-03 | Medium | DNS rebinding (URL validated but no IP pinning) |
| PATH-01 | High | User input in file paths |
| PATH-02 | Medium | No path traversal protection |
| PATH-03 | Medium | Symlink following without check |
| INJ-01 | Critical | eval/exec on user input |
| INJ-02 | Critical | SQL string interpolation |
| INJ-03 | High | subprocess with shell=True |
| INJ-04 | High | Template injection via .format() |
| INJ-05 | Critical | Unsafe deserialization (pickle/yaml) |
| AUTH-01 | Medium | No auth on tool handlers |
| AUTH-02 | Critical | Hardcoded secrets/API keys (OpenAI, Stripe, GitHub, AWS) |
| AUTH-03 | Low | No rate limiting on tool endpoints |
| SEC-01 | High | SSL verification disabled |
| SEC-02 | Medium | Wildcard CORS |
| SEC-03 | Medium | Stack traces/error details exposed to client |
| SEC-04 | Low | No input length validation (DoS risk) |
| LOG-01 | Low | No logging/audit trail on tool invocations |
python3 tests/test_integration.py
Add to ~/.claude/mcp.json:
{
"mcpServers": { "mcp-shield": { "command": "python3", "args": ["/path/to/mcp-shield/src/mcp_server.py"] } } }
Claude Code tools: shield_scan_file, shield_scan_directory, shield_scan_code
MCP Shield: my-server/ — 3 finding(s)
[CRIT] SSRF-01: Potential SSRF: Dynamic URL from user input requests call with dynamic URL that may include user input Location: server.py:45 Fix: Validate URL against allowlist. Block internal IPs. CWE: CWE-918
[HIGH] INJ-03: Command injection: subprocess with shell=True subprocess called with shell=True. User input in args = RCE. Location: tools.py:112 Fix: Use subprocess with shell=False and pass args as list. CWE: CWE-78
[MED] AUTH-01: No authentication detected on tool handlers MCP tool handlers found but no auth logic detected Fix: Add authentication middleware. CWE: CWE-306
Grade: F | 1 critical, 1 high, 1 medium
The MCP ecosystem has 9,400+ servers and 97M monthly SDK downloads. Security tooling hasn't kept up. We built MCP Shield because every MCP server deployed without a security scan is a liability.
Built by Like One, a 501(c)(3) nonprofit. Security tooling should be free.
MIT — Like One