What is the key difference between Codeinspectus and Privacyscrubber MCP?

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

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

Codeinspectus operates under a Free / Open Source model (No auth required). Privacyscrubber MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Codeinspectus lists 7 tools with 6 views and 47 GitHub stars. Privacyscrubber MCP lists 5 tools with 3 views and 2 GitHub stars.

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

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

Privacyscrubber MCP

Security · Local stdio

Quality: 48/100 (Fair) | Auth: API Key required

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

Explore Codeinspectus Details

Choose Privacyscrubber MCP when:

You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
Primary tools included: Local PII and secret tokenization, Text sanitization with selectable profiles, Sanitization for text and supported local files.

Explore Privacyscrubber MCP Details

Feature & Specification Comparison

Specification	Codeinspectus Synvoya Security	Privacyscrubber MCP moxno 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.	Zero-trust local PII and secrets masking server for Cursor, Windsurf, and Claude Desktop. npx pii-masking-run
Category & Scope

Tools & Capabilities Breakdown

Codeinspectus Tools (7)

codeinspectus_scan

Run a full local security scan of a path: managed 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. Also returns the V3 repository-trust contract with deterministic V3.1 source-integrity evidence for bidi controls, hidden/default-ignorable characters, Unicode tag and variation-selector payloads, and bounded mixed-script confusables. V3.2 additionally audits explicit AI attribution in source/git/media metadata and validates supported local C2PA assets with the official optional Content Authenticity Initiative library. Remote manifests and revocation endpoints are never fetched. Statistical-watermark detection remains explicitly unavailable. Fully offline — zero network egress at scan time. Never writes to your code or repo.

codeinspectus_setup

Inspect external-engine health and exact platform download sizes, save declined choices, or install selected Opengrep/Gitleaks/Trivy components after explicit confirmation. Plan is offline. Install writes only to ~/.codeinspectus, verifies immutable pins/publisher provenance, and never modifies the target repository.

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

Codeinspectus Configuration

mcpServers (Claude Desktop / Cursor)

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

Privacyscrubber MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "moxno-privacyscrubber-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@privacyscrubber/mcp-server"
      ]
    }
  }
}

Frequently Asked Questions

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

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