MCP Security Scanner
Unclaimed55-tool MCP server for security scanning of MCP servers. Runtime inspection, AST-based SAST, config audit, dependency analysis, OWASP MCP Top 10 compliance. OAuth, TLS, fuzz testing, prompt injection, tool mutation detection. 100% local, zero external API calls.
Set up this server
01 / Choose your client
02 / Before you connect
Authentication is not specified. Check the project instructions before connecting.
Project instructions03 / Add the configuration
claude mcp add --transport stdio 'mcp-security-scanner' -- 'npx' '-y' 'mcp-security-scanner'04 / Check it in your client
Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.
More in Security
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
40 of 40 tools
Documented tools (40)
From project documentation. A server handshake does not verify each tool’s description or behavior.
cfg_audit_mcp_config
Deep audit of an MCP config file — env var exposure, stdio vs SSE transport, argument injection
cfg_auto_discover
Auto-discover all MCP configuration files — Claude Desktop, Cursor, VS Code, Windsurf, custom paths
cfg_check_context_oversharing
Check for context oversharing — configs exposing too many tools or resources to the agent
cfg_check_shadow_servers
Detect shadow MCP servers — unauthorized servers in config that shouldn't be there
cfg_scan_env_files
Scan .env files for secrets, oversharing, and insecure variable patterns
rt_check_ansi_injection
Detect ANSI escape sequences in tool descriptions that can manipulate terminal output or hide content
rt_check_auth
Analyze server authentication and authorization mechanisms
rt_check_callbacks
Detect callback/webhook URL parameters that could enable SSRF — checks for missing URL constraints
rt_check_capabilities
Inspect server capabilities — experimental features, dynamic tool changes (listChanged), logging, sampling
rt_check_cross_origin
Check for cross-origin tool invocation risks between multiple connected MCP servers
rt_check_http_security
Check HTTP response headers — HSTS, CORS, X-Content-Type-Options, Cache-Control, cookie flags
rt_check_instructions
Analyze server instructions from initialization for poisoning, social engineering, excessive length
rt_check_oauth
Test if HTTP/SSE server validates OAuth tokens — sends no token, invalid token, and forged JWT (alg:none)
rt_check_prompt_injection
Fetch prompt content via getPrompt() and scan for injection patterns, template syntax, dangerous arguments
rt_check_protocol_version
Check server name/version from initialization — flags missing info, outdated SDK versions
rt_check_rate_limiting
Send rapid ping() bursts to test rate limiting — flags servers accepting unlimited requests
rt_check_resource_content
Read actual resource content via readResource() and scan for poisoning, ANSI, Unicode stego, oversized content
rt_check_resource_exposure
Check for sensitive resource exposure through MCP resource endpoints
rt_check_scope_creep
Analyze tool schemas for excessive permissions — tools requesting more access than their description implies
rt_check_tls
Inspect TLS certificate — expired, self-signed, weak signature (SHA-1), short key (<2048 bits), plain HTTP
rt_check_tool_mutation
Dual-snapshot comparison with configurable delay — detect tool additions, removals, description changes (rug pull)
rt_check_tool_poisoning
Scan tool descriptions for 15+ poisoning patterns — hidden instructions, prompt injection, data exfiltration triggers
rt_check_tool_shadowing
Detect tools that shadow or override standard tool names to intercept agent actions
rt_check_unicode_steganography
Detect zero-width Unicode characters used to hide instructions in tool descriptions (steganography)
rt_fuzz_tools
Fuzz-test tools with edge-case inputs — path traversal, command injection, SQL injection, type confusion (dry-run by default)
rt_inspect_server
Connect to a running MCP server (stdio/HTTP/SSE) and enumerate all tools, schemas, resources, and prompts
rt_pin_tools
Generate SHA-256 pins for all tool definitions — descriptions, schemas, and metadata
rt_verify_pins
Verify current tool definitions against previously saved pins to detect rug pull modifications
sast_code_execution
Detect code execution vulnerabilities — eval(), Function(), vm.runInNewContext() with user input
sast_command_injection
Detect command injection vulnerabilities — taint tracking from tool inputs to exec/spawn/execFile sinks
sast_hardcoded_secrets
Detect hardcoded secrets — API keys, passwords, tokens, connection strings in source code
sast_info_disclosure
Detect information disclosure — stack traces, debug output, verbose errors exposed to clients
sast_insecure_crypto
Detect insecure cryptographic usage — MD5, SHA1, ECB mode, hardcoded IVs, weak key sizes
sast_missing_logging
Audit logging coverage — detect tool handlers missing audit logging for security events
sast_path_traversal
Detect path traversal vulnerabilities — taint tracking from tool inputs to fs.readFile/writeFile sinks
sast_prototype_pollution
Detect prototype pollution vectors — unsafe object merging, bracket notation with user input
sast_regex_dos
Detect ReDoS-vulnerable regular expressions — catastrophic backtracking patterns
sast_scan_directory
Full SAST scan of a directory — runs all 11 analyzers with AST-based taint tracking via ts-morph
sast_ssrf
Detect SSRF vulnerabilities — taint tracking from tool inputs to fetch/http.request/axios sinks
sast_unsafe_regex
Detect unsafe regex patterns — unescaped user input in RegExp constructors
Tool change history
FAQ
Questions about MCP Security Scanner MCP Server
- How do I connect MCP Security Scanner MCP Server to Claude?
- Run `claude mcp add mcp-security-scanner -- npx -y mcp-security-scanner` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
- Is MCP Security Scanner MCP Server free?
- The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can MCP Security Scanner MCP Server do?
- MCP Security Scanner MCP Server documents 40 tools to the agent, including cfg_audit_mcp_config, cfg_auto_discover, cfg_check_context_oversharing. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.