What is the key difference between Checker MCP and Codeinspectus?

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

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

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

Which MCP server has more tools and community activity?

Checker MCP lists 3 tools with 2 views and 0 GitHub stars. Codeinspectus lists 7 tools with 6 views and 47 GitHub stars.

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

Checker MCP vs Codeinspectus

In-depth architectural comparison of the Checker 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

Checker MCP

Security · Local stdio

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

Codeinspectus

Security · Local stdio

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

Verdict Summary: Choose Checker 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 Checker 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).
Primary tools included: check_domain, list_checks, explain_check.

Explore Checker MCP Details

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

Feature & Specification Comparison

Specification	Checker MCP OksigeniaSL Security	Codeinspectus Synvoya Security
Summary	Domain security & privacy checker: 17 live checks (SPF, DMARC, DKIM, DNSSEC, TLS, CAA, security headers) scored 0-100 with remediation. Local-first, zero telemetry. In the official MCP Registry as com.oksigenia/checker-mcp; npm @oksigenia/checker-mcp.	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

Checker MCP Tools (3)

check_domain

Scan a domain or URL and return a scored report from real live checks.

list_checks

List every check grouped by category, with the reason each one matters.

explain_check

Explain a single check by id, why it matters, and how to remediate a failure.

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.

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

Checker MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "oksigeniasl-checker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@oksigenia/checker-mcp"
      ]
    }
  }
}

Codeinspectus Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Checker MCP More alternatives to Codeinspectus Security category hub