In-depth architectural comparison of the Feranor Resilience 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
Feranor Resilience
Security · Remote HTTP/SSE
Quality: 69/100 (Great) | Auth: No auth required
Codeinspectus
Security · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Feranor Resilience if you need specialized Security tools running via a hosted cloud SSE transport. 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 Feranor Resilience when:
You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Freemium).
Primary tools included: Invisible Unicode and homoglyph detection, Text cleanup with before-and-after risk comparison, Domain scores across TLS, DNS, headers, and speed.
Scan/purge hidden text & score web domains: TLS, DNS, headers, speed. Free scans, $0.01 actions.The Tools:
text_scan_v1 — free
Scans a text string for invisible Unicode characters, homoglyphs, and normalization issues. Returns a risk score, a list of flagged characters, and detected homoglyphs. Never modifies the input text.
text_purge_v1 — $0.01 per call
Removes invisible Unicode characters and replaces homoglyphs in a text string, then normalizes the result. Returns the cleaned text plus a before-and-after risk comparison.
domain_check_score_v1 — free
Overall score, per-category scores, and how many findings each category raised. Use it to triage: rank a list of domains, confirm one is healthy, or decide whether the full report is worth pulling. It tells you which categories are weak and how many issues they hold, but not what the issues are.
domain_check_score_batch_v1 — free
The same triage scores for up to 100 domains in a single call. One score summary per distinct domain: overall score, per-category scores, and how many findings each category raised. Never the findings themselves.
domain_check_v1 — $0.01 per call
Full report for one domain: weighted score out of 100, per-category breakdown, and every individual finding with a prioritised remediation order.
domain_check_batch_v1 — from $0.005 per domain
The same full report for up to 100 domains in a single call, with one payment for the whole batch instead of one per domain. Both cheaper per domain and much faster than calling domain_check_v1 in a loop.
Tools & Capabilities Breakdown
Feranor Resilience Tools (5)
Invisible Unicode and homoglyph detection
Text cleanup with before-and-after risk comparison
Domain scores across TLS, DNS, headers, and speed
Single-domain detailed findings with remediation priority
Batch scoring and reporting for up to 100 domains
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).
Feranor Resilience is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Codeinspectus belongs to Security using local stdio subprocess. Select Feranor Resilience when you need capabilities focused on security and Codeinspectus when you require tools for security.
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
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. Repository-trust artifacts are diffed separately with fail-closed resolved, remaining, introduced and not-rechecked states. Use this to verify approved 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.