Mcp Maigret vs Codeinspectus — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mcp Maigret vs Codeinspectus
In-depth architectural comparison of the Mcp Maigret 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
Mcp Maigret
Security · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Codeinspectus
Security · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Mcp Maigret 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 Mcp Maigret 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).
You have access to required keys: MAIGRET_REPORTS_DIR.
MCP server for maigret, a powerful OSINT tool that collects user account information from various public sources. This server provides tools for searching usernames across social networks and analyzing URLs.
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
Mcp Maigret Tools (7)
search_username
username
format
use_all_sites
tags
parse_url
url
Codeinspectus Tools (6)
codeinspectus_scan
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).
Mcp Maigret is categorized under Security and uses a local stdio subprocess. In contrast, Codeinspectus belongs to Security using local stdio subprocess. Select Mcp Maigret when you need capabilities focused on security and Codeinspectus when you require tools for security.
Full local scan of a path (engines + AI checks). Returns CWE-keyed findings, detected technologies, exact native-pack and Pub dependency coverage, remediations, framework tags, and three-state repository evidence for supported runtime controls.
codeinspectus_rescan
Re-scan after fixes; diffs vs a prior scan → resolved / remaining / introduced, with fresh technology and pack coverage.
codeinspectus_compliance_report
Per-framework **code-level control coverage** (not certification).
codeinspectus_explain_finding
Deep explanation + full remediation for one finding.
codeinspectus_generate_sbom
CycloneDX/SPDX SBOM using Trivy plus native Pub inventory/fallback (written to the managed dir by default, or a path you choose).
codeinspectus_list_rules
Active detectors, native-pack inventory/rule ownership, engine versions, detection-DB + Trivy/Pub DB provenance and freshness, and structured machine setup/repair state.