What is the key difference between Web Exposure MCP and Codeinspectus?

Web Exposure MCP belongs to the Security category with local stdio execution, while Codeinspectus belongs to the Security category with local stdio execution.

How do I install Web Exposure MCP or Codeinspectus in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Web Exposure MCP and Codeinspectus free or paid?

Web Exposure MCP operates under a Free / Open Source model (No auth required). Codeinspectus operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Web Exposure MCP lists 2 tools with 1 views and 1 GitHub stars. Codeinspectus lists 6 tools with 6 views and 45 GitHub stars.

Can I use both Web Exposure MCP and Codeinspectus together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Web Exposure MCP vs Codeinspectus

In-depth architectural comparison of the Web Exposure MCP and Codeinspectus 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.

At a Glance & Executive Verdict

Web Exposure MCP

Security · Local stdio

Quality: 57/100 (Good) | Auth: No auth required

Codeinspectus

Security · Local stdio

Quality: 68/100 (Great) | Auth: No auth required

Verdict Summary: Choose Web Exposure MCP if you need specialized Security tools running via a local process. Choose Codeinspectus if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Web Exposure MCP when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: scan_web_exposure, list_exposure_checks.

Explore Web Exposure MCP Details

Choose Codeinspectus when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: codeinspectus_scan, codeinspectus_rescan, codeinspectus_compliance_report.

Explore Codeinspectus Details

Feature & Specification Comparison

Specification	Web Exposure MCP Perufitlife Security	Codeinspectus Synvoya Security
Summary	Points an AI agent at a live URL and confirms publicly-served secret files by fetching the bytes — exposed .git, .env, JS source maps, backup/SQL dumps, directory listing, and dotfiles. Zero dependencies, read-only.	Local-first, zero-egress security scanner for AI-generated / "vibe-coded" JS/TS. Bundles Opengrep, Gitleaks & Trivy behind one CWE-keyed schema and adds AI-code-specific checks (client-side secret exposure, Supabase RLS, prompt-injection & LLM-output XSS sinks). No account, no telemetry.
Category & Scope

Tools & Capabilities Breakdown

Web Exposure MCP Tools (2)

scan_web_exposure

Probe a live URL and return only the secret files genuinely served, with evidence. Args: `url` (required), `only` (optional check filter), `timeout_ms`.

list_exposure_checks

List every check id, severity and the paths it probes — feed ids into `only`.

Codeinspectus Tools (6)

codeinspectus_scan

Run a full local security scan of a path: bundled engines (Opengrep SAST, Gitleaks secrets, Trivy SCA/IaC/license), CodeInspectus's offline native Pub SCA, plus AI-code-specific checks (client-side secret exposure, Supabase RLS/inverted-auth, prompt-injection sinks, API-boundary failures, and explicit runtime-control misconfiguration). Returns CWE-keyed findings with fix recommendations, detected repository technologies, explicit native-pack execution counts, compliance tags, and three-state repository evidence for supported runtime controls. Fully offline — zero network egress at scan time. Never writes to your code or repo.

codeinspectus_rescan

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).

Web Exposure MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "perufitlife-web-exposure-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "web-exposure-mcp"
      ]
    }
  }
}

Codeinspectus Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "synvoya-codeinspectus": {
      "command": "npx",
      "args": [
        "-y",
        "codeinspectus"
      ]
    }
  }
}

Frequently Asked Questions

Web Exposure MCP is categorized under Security and uses a local stdio subprocess. In contrast, Codeinspectus belongs to Security using local stdio subprocess. Select Web Exposure MCP when you need capabilities focused on security and Codeinspectus when you require tools for security.

More alternatives to Web Exposure MCP More alternatives to Codeinspectus Security category hub