Sieve MCP vs Codeinspectus — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Sieve MCP vs Codeinspectus
In-depth architectural comparison of the Sieve 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
Sieve MCP
Security · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Codeinspectus
Security · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Sieve 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 Sieve 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).
Local AI chat history secret scanner for macOS. Finds API keys and secrets leaked into Claude Code, Cursor, Copilot Chat, Cline, Codex, Gemini CLI, and other AI tool transcripts. 9 MCP tools: findings list with redacted previews, boolean secret detection (sievechecktext), placeholder-only redaction (sieveredacttext returns sieve://project/key, never raw values), vault-backed command execution, and scan health. Local-only stdio transport, macOS Keychain vault, no plaintext secrets in any tool response. Mac App Store.
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.
Tools & Capabilities Breakdown
Sieve MCP Tools (9)
sieve_health_status
Returns service health and finding counts.
sieve_self_test
Verifies scanner rules and transcript source coverage are healthy.
Sieve MCP is categorized under Security and uses a local stdio subprocess. In contrast, Codeinspectus belongs to Security using local stdio subprocess. Select Sieve MCP when you need capabilities focused on security and Codeinspectus when you require tools for security.
Returns status of the current or most recent scan.
sieve_check_text
Checks whether text contains secrets. **Returns boolean only — never echoes input or detected values.**
sieve_redact_text
Redacts secrets from text, replacing values with `sieve://` placeholders.
sieve_vault_run
Executes a command with macOS Keychain-resolved secrets injected as env vars. Secrets never transit the MCP channel.
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.
codeinspectus_explain_finding
Return a deep explanation and full remediation plan for a single finding id from a prior scan: what the weakness is, why it matters, concrete fix steps, and references.
codeinspectus_generate_sbom
Generate a CycloneDX or SPDX SBOM for the target project using Trivy plus the first-party offline Pub lockfile inventory, with native Pub fallback when Trivy is unavailable. Writes the SBOM file to the chosen output path and returns its location and component count. Offline.
codeinspectus_list_rules
List the active detectors and engine versions, the CodeInspectus detection-database version and date, Trivy vulnerability-DB freshness, bundled Pub advisory-database provenance/freshness, and the custom CodeInspectus AI-code rules and native detector packs currently shipped.