Mobb Vibe Shield MCP vs MCP Recon

In-depth architectural comparison of the Mobb Vibe Shield MCP and MCP Recon MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Mobb Vibe Shield MCP when:

• You need dedicated capabilities in the Security domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: API_KEY, API_URL, MVS_AUTO_FIX.
• Primary tools included: Supports SAST tools: Checkmarx, CodeQL, Fortify, Snyk, Two modes: Scan (runs SAST scan) and Analyze (uses existing SAST report), Generates automated code fixes for detected vulnerabilities.

Explore Mobb Vibe Shield MCP Details

Choose MCP Recon when:

• You need dedicated capabilities in the Security domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: .

Feature & Specification Comparison

Specification	Mobb Vibe Shield MCP mobb-dev Security	MCP Recon nickpending Security
Summary	Mobb Vibe Shield identifies and remediates vulnerabilities in both human and AI-written code, ensuring your applications remain secure without slowing development.	Conversational recon interface and MCP server powered by httpx and asnmap. Supports various reconnaissance levels for domain analysis, security header inspection, certificate analysis, and ASN lookup.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "mobb-dev-mobb-vibe-shield-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mobbdev"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE",
        "API_URL": "YOUR_API_URL_HERE",
        "MVS_AUTO_FIX": "YOUR_MVS_AUTO_FIX_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "nickpending-mcp-recon": {
      "command": "docker",
      "args": [
        "run",
        "mcp/recon"
      ],
      "env": {
        "PDCP_API_KEY": "YOUR_PDCP_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons