mcpField
M
MCP Security & Vulnerability Auditor

MCP Security & Vulnerability Auditor

Remote
neoninnovationlab.comSecurity0Updated 6w ago

About MCP Security & Vulnerability Auditor

An MCP security auditing server for coding agents that checks MCP repositories and local code before installation or deployment. It uses static AST analysis without executing the code and returns CWE-linked findings and remediation guidance.

Key features

  1. 01Static AST vulnerability scanning
  2. 02Audit Git repositories and local directories
  3. 03Detect command injection and path traversal
  4. 04Find hardcoded secrets and missing authentication
  5. 05Return risk scores and remediation reports

Use cases

  1. 01Review an MCP repository before installation
  2. 02Audit local server code before deployment

MCP support

The MCP server exposes repository and local-directory auditing tools to clients through MCP tools/list and tools/call.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://neon_innovation_lab--mcp-security-auditor.apify.actor/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://neon_innovation_lab--mcp-security-auditor.apify.actor/mcp
SSEhttps://neoninnovationlab.com/api/mcp-security

Tools

Details

From the project README

MCP Security Auditor Server

Model Context Protocol Glama Quality Score Python 3.12 License: MIT Transport: stdio

A production-ready Model Context Protocol (MCP) Server providing AI coding assistants (Claude Desktop, Cursor, Windsurf, Cline) with native security analysis tools. It enables AI agents to statically audit other MCP servers, tool repositories, and local codebases for critical security vulnerabilities before onboarding or executing them.


🛠️ MCP Tools Exposed

This server implements the official Model Context Protocol specification (tools/list and tools/call):

1. audit_mcp_repository

Performs an automated, zero-execution static Abstract Syntax Tree (AST) security audit on a Git repository containing an MCP server implementation.

  • Parameters:
    • repository_url (string, required): Public Git URL of the MCP server repository to audit (e.g. https://github.com/example/mcp-server).
    • sub_directory (string, optional): Specific subdirectory within the repository to inspect (useful for monorepos).
  • Vulnerability Checks Conducted:
    • CWE-78 (Command Injection): Detects unsanitized subprocess.run, child_process.exec, shell invocation in tool execution blocks.
    • CWE-22 (Path Traversal): Flags unrestricted file read/write operations lacking path canonicalization (os.path.realpath, boundary checks).
    • CWE-798 (Hardcoded Secrets): Identifies leaked API keys, tokens, and corporate credentials in tool schemas or server definitions.
    • CWE-306 (Missing Authentication): Flags public HTTP/SSE transports exposing destructive capabilities without bearer auth.
    • CWE-1336 (Tool & Prompt Injection): Flags tool descriptions susceptible to prompt hijacking.
  • Returns:
    • trust_score (0–100): Weighted security index.
    • grade ("A+", "A", "B", "C", "F"): Security letter grade.
    • findings (array): Line-by-line vulnerability records with CWE identifiers and remediation instructions.
    • markdown_report (string): Pre-formatted human-readable audit report.
2. audit_local_directory

Audits a local filesystem directory containing MCP server source code before deployment.

  • Parameters:
    • directory_path (string, required): Absolute or relative filesystem path to the target directory.
  • Returns: Structured JSON audit record and remediation checklist.

🚀 Client Configuration & Quickstart

1. Claude Desktop Setup

Add the server to your claude_desktop_config.json:

{
  "mcpServers": {
    "mcp-security-auditor": {
      "command": "python3",
      "args": ["/path/to/mcp-security-auditor/server.py"]
    }
  }
}
2. Cursor IDE / Windsurf Setup

In Cursor, go to Settings → Features → MCP → Add New MCP Server:

  • Name: mcp-security-auditor
  • Type: command
  • Command: python3 /absolute/path/to/server.py
3. Docker Container Execution

Run isolated via Docker using the pre-configured Dockerfile:

{
  "mcpServers": {
    "mcp-security-auditor": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/ansarii/mcp-security-auditor"
      ]
    }
  }
}

💻 Example Agent Usage

Once connected, your AI assistant can execute security pre-flight checks before installing tools:

User: "Audit the MCP server at https://github.com/modelcontextprotocol/servers before I install it."

Claude (Tool Call):
audit_mcp_repository({
  "repository_url": "https://github.com/modelcontextprotocol/servers",
  "sub_directory": "src/fetch"
})

Result:
{
  "status": "success",
  "target_name": "servers:src/fetch",
  "trust_score": 95,
  "grade": "A+",
  "findings_count": 0,
  "recommendation": "SAFE_TO_CONNECT"
}

🔒 Security Guarantee: Zero Execution

Unlike runtime scanners that execute arbitrary stdio binaries (creating direct Remote Code Execution risks on the host), this MCP server uses pure static Abstract Syntax Tree (AST) analysis. It inspects Python, TypeScript, and JSON-RPC implementations without ever executing untrusted code.


📜 License

MIT License — Copyright (c) 2026 Neon Innovation Lab.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.