veritasacta-verify — Claude Code MCP server: setup guide
An MCP server that verifies Ed25519 signatures on Acta receipts offline without external network calls. Useful for validating cryptographic audit records right inside the agent terminal.
claude mcp add veritasacta-verify -- npx -y @veritasacta/verifyWhat veritasacta-verify does
This MCP server gives your coding assistant local validation capabilities for Acta receipts and audit bundles adhering to draft-farley-acta-signed-receipts-03. It runs entirely on your local machine. You do not need accounts, sign-in tokens, network daemons, or proxies to evaluate files. The underlying parser rejects duplicate JSON keys upfront and accepts files up to 50 MiB with an object depth limit of 128.
Signature checks require an external 64-character hexadecimal public key supplied through a separate trusted channel. The verifier deliberately refuses to evaluate a receipt against public keys embedded within the record itself, returning a key_mismatch error instead. Because it halts on self-signed payload keys by default, validating untrusted files without an explicit external pin is impossible.
What it helps with
- Verify Ed25519 cryptographic signatures on audit receipts
- Check Acta record integrity offline without network requests
- Flag issuer identifier mismatches against signing keys
- Parse audit files up to 50 MiB with strict JSON duplicate detection
Example prompts for the agent
- Verify the signature in
receipt.jsonusing the public keyebb8cf3efc78717c50e7c438c0ad5498f8fa4e09607fea1e030ac129b5965225. - Check whether the audit bundle
audit.jsonpasses validation and report any non-zero exit code. - Inspect
run-manifest.jsonagainst the Acta specification without contacting remote services.
How to install veritasacta-verify
Platform CLI
claude mcp add veritasacta-verify -- npx -y @veritasacta/verifyPlatform CLI
codex mcp add veritasacta-verify -- npx -y @veritasacta/verifyConfig file
{
"mcpServers": {
"veritasacta-verify": {
"command": "npx",
"args": [
"-y",
"@veritasacta/verify"
]
}
}
}Config file
{
"servers": {
"veritasacta-verify": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@veritasacta/verify"
]
}
}
}Platform CLI
gemini mcp add veritasacta-verify npx -y @veritasacta/verifyStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about veritasacta-verify
How do I install veritasacta-verify in Claude Code?
Run the following command in your terminal: claude mcp add veritasacta-verify -- npx -y @veritasacta/verify. The environment must have Node.js and npx available.
Why does the verifier demand an independent public key?
The tool requires an independently sourced 64-hex-character key to ensure trust. Evaluating an entry with keys stored directly inside the file triggers a key_mismatch failure.
What does exit code 1 mean during verification?
Exit code 1 indicates that a check failed. It does not automatically prove file tampering, as supplying the wrong verification key yields the exact same exit status.
