Dvalincode vs Codeinspectus
A side-by-side look at the Dvalincode and Codeinspectus MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dvalincode for security work as a local process; choose Codeinspectus for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dvalincode when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
Choose Codeinspectus when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
codeinspectus_scan, codeinspectus_setup, codeinspectus_rescan.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 49/100 · Fair | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 117 | 48 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View Dvalincode | View Codeinspectus |
Tools & capabilities
Dvalincode tools
No tool names declared yet. Check the project README from the listing page.
Codeinspectus tools 7
codeinspectus_scanRun 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.codeinspectus_setupInspect 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_rescanRe-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_reportProduce 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_findingReturn 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_sbomGenerate 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_rulesList 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.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Dvalincode
{
"mcpServers": {
"dvalincode": {
"command": "npx",
"args": [
"-y",
"dvalincode"
]
}
}
}
Codeinspectus
{
"mcpServers": {
"synvoya-codeinspectus": {
"command": "npx",
"args": [
"-y",
"codeinspectus"
]
}
}
}
Frequently asked questions
Dvalincode is categorized under Security and uses a local stdio subprocess. Codeinspectus belongs to Security and uses a local stdio subprocess. Pick Dvalincode for security work and Codeinspectus for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Dvalincode has no declared pricing — check the project's own site. Codeinspectus is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dvalincode and synvoya-codeinspectus as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dvalincode has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 117 GitHub stars. Codeinspectus has 68/100 (Great) with 6 views, 0 installs and 48 GitHub stars.
