Side-by-Side Model Context Protocol Comparison
Privacyscrubber MCP vs Codeinspectus
In-depth architectural comparison of the Privacyscrubber 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
Privacyscrubber MCP
Security · Local stdio
Quality: 48/100 (Fair) | Auth: API Key required
Codeinspectus
Security · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Privacyscrubber 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 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.
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.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Privacyscrubber MCP Tools (5)
Local PII and secret tokenization
Text sanitization with selectable profiles
Sanitization for text and supported local files
Local token restoration with reveal_text
License and tier status reporting
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.
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).
Privacyscrubber MCP Configuration
Codeinspectus Configuration