BACK TO MCP SERVERS
securityany

Dvalincode

Deterministic security scanning, no model or API key, plus offline-verifiable proof a fix worked.

At a glance

Not tested yet
GitHub stars
121
Weekly downloads
976
Last commit
2026-11-20
Licence
MIT
Transport
stdio
Auth
none
Install
npx -y dvalincode
Stats checked 2026-11-21

What it does

DvalinCode is an MCP server that checks whether a security fix an agent made is real. It re-scans with the scanners your CI gate already runs, runs your project's own tests, and reads the exit codes. No model has a say in the verdict. It is for developers whose coding agents fix what scanners report and who want one verdict across agents and scanners.

DvalinCode
Image: arthurpanhku/dvalincode (MIT)

Key features

  • Reaches a verdict from the exit codes of processes it started and from a re-scan by the engines your CI gate runs.
  • Produces a Verified Fix Record, a small JSON file anyone can re-check offline.
  • Ignores that a change adds, such as .snyk, nosemgrep and nosec, do not count when that change is judged.
  • Treats silencing the scanner as not a fix: moving a sink to a sibling, deleting the vulnerable file, deleting tests or removing assertions all fail.
  • For code findings, a test must fail on the unfixed code and pass after the fix, unchanged.
  • Built-in rules make the first scan work with nothing installed.
  • Ships a security-gate skill for Claude Code and Codex that tells the agent to call Dvalin after security-sensitive edits.

Quick start

  1. Connect Dvalin to the agents on your machine and preview what each agent would get:
npx dvalincode agents connect
  1. Apply the connection:
npx dvalincode agents connect --yes
  1. After writing a repair, the agent calls dvalin_verify_findings and gets a Verified Fix Record back.

Add it to Claude Code from a terminal:

claude mcp add dvalincode -- npx -y dvalincode

Or add this to .mcp.json in your project root (Claude Code) or .cursor/mcp.json (Cursor):

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

Environment variables

The registry entry declares no environment variables.

Example prompts

  • "Fix the security finding the scanner reported, then call Dvalin to verify the fix."
  • "Check whether my last change actually removed the vulnerability, and show me the fix record."
  • "Run the verification again and tell me what is still wrong."

What to watch out for

  • A record says only that the findings were present, that a re-scan no longer reported them, and that these commands ran with these exit codes. It does not say the code is safe.
  • Every record carries what the scan covered: complete, partial or unknown. A fix no check could confirm does not pass.
  • A fix that removes one finding and introduces another is recorded as regressed.
  • Evasion checks match known patterns, and their limits are listed under honest gaps.
  • Engines that upload source, such as Snyk Code, run only when you name them.
  • Dvalin is not a coding agent and does not offer the widest vulnerability discovery.

Not tested by tools4agents yet. Read the source repository before you install it.

GitHub SourceGitHub Stars
Last verified 2026-11-21