What is the key difference between Codeinspectus and MCP Security Audit?

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

How do I install Codeinspectus or MCP Security Audit 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 Codeinspectus and MCP Security Audit free or paid?

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

Which MCP server has more tools and community activity?

Codeinspectus lists 6 tools with 6 views and 45 GitHub stars. MCP Security Audit lists 6 tools with 4 views and 57 GitHub stars.

Can I use both Codeinspectus and MCP Security Audit 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

Codeinspectus vs MCP Security Audit

In-depth architectural comparison of the Codeinspectus and MCP Security Audit 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

Codeinspectus

Security · Local stdio

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

MCP Security Audit

Security · Local stdio

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

Verdict Summary: Choose Codeinspectus if you need specialized Security tools running via a local process. Choose MCP Security Audit 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 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

Choose MCP Security Audit 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: Remote npm registry security checks, Critical-to-low severity reporting, CVE, CVSS, CWE, and advisory references.

Explore MCP Security Audit Details

Feature & Specification Comparison

Specification	Codeinspectus Synvoya Security	MCP Security Audit qianniuspace Security
Summary	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.	A powerful MCP (Model Context Protocol) Server that audits npm package dependencies for security vulnerabilities. Built with remote npm registry integration for real-time security checks.
Category & Scope

Tools & Capabilities Breakdown

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

Re-run a scan after fixes were applied and diff against a prior scan_id (or the most recent scan of the same path). Reports which findings are resolved, which remain, and which were newly introduced, plus fresh technology and native-pack execution coverage. Use this to verify fixes. Never writes to your code or repo.

codeinspectus_compliance_report

Produce a per-framework code-level control-coverage view for a prior scan (NIST CSF 2.0, ISO 27001:2022, SOC 2, CIS v8.1, Essential Eight, OWASP Web/LLM). Reports 'X of N code-visible controls have findings' with the code-visible subset as the explicit denominator. This is NOT a compliance audit, certification, or attestation — code-level evidence only.

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

Codeinspectus Configuration

mcpServers (Claude Desktop / Cursor)

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

MCP Security Audit Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "qianniuspace-mcp-security-audit": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Codeinspectus More alternatives to MCP Security Audit Security category hub Canonical compare URL