The mcp-proofjson server allows AI agents to assess invoice payment risk, verify structured JSON proofs, and list available verification capabilities.
assess_invoice_before_payment: Evaluate an invoice (supplier name, invoice number, amount, currency, IBAN, etc.) against supplied data and policy rules, returning a structured decision (allow, review, or block) with reasons, confidence level, scope, checks performed/not performed, and whether human confirmation is required.
verify_proofjson_proof: Validate a ProofJSON proof object for structural integrity, hash consistency, and signature validity. This does not verify real-world truth of underlying claims, supplier identity, IBAN ownership, or sanctions status.
list_proofjson_packs: Retrieve the currently available ProofJSON Pack Tasks (verification capabilities) supported by the server.
Important limitation: The server operates on supplied data only — it does not independently verify IBAN ownership, sanctions status, or payment history unless external trust adapters are configured. An allow result is not a guarantee the invoice is safe.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-proofjson Assess invoice: Supplier A, $1500, invoice IBAN PT50...123, expected PT50...456"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A local MCP server (stdio) that lets AI agents produce and verify structured JSON outputs — with explicit scope, checks performed, checks not performed and human-confirmation requirements, instead of opaque yes/no answers.
The first live pack focuses on invoice assessment before payment: given supplied invoice data, context and policy, it returns allow / review / block with reasons and confidence. Works in Claude Desktop, Cursor and other MCP clients.
Scope (v1):
supplied_data_only. It assesses the supplied data and configured policy. It does not independently verify supplier IBAN ownership, sanctions status, bank account ownership or external payment history unless external trust adapters are configured.allowis not a guarantee the invoice is safe.Local stdio only — there is no public remote MCP until auth, rate limits, audit logs, terms and privacy are finalised.
assess_invoice_before_payment — returns allow / review / block with reasons, confidence, scope, checks_performed, checks_not_performed, human_confirmation_required.
verify_proofjson_proof — verify a proof for structure, hash consistency and signature validity. Does NOT verify the real-world truth of the underlying claim, invoice, supplier identity, IBAN ownership or sanctions status.
list_proofjson_packs — lists the live Pack Tasks.
This server does not expose arbitrary fetch, a browser, a shell, the filesystem, a generic HTTP proxy, a generic run endpoint, or any internal scoring.
Related MCP server: einvoice-mcp
npm install
npm run buildAdd to claude_desktop_config.json:
{
"mcpServers": {
"proofjson": {
"command": "node",
"args": ["/ABSOLUTE/PATH/mcp-proofjson/dist/index.js"]
}
}
}Add to .cursor/mcp.json (or Cursor Settings → MCP):
{ "mcpServers": { "proofjson": { "command": "node", "args": ["/ABSOLUTE/PATH/mcp-proofjson/dist/index.js"] } } }PROOFJSON_BASE (env) — defaults to https://proofjson.org.
Ask your agent: "Assess this invoice before payment. Supplier ACME, amount 4250 EUR, invoice IBAN PT50…789, expected IBAN PT50…154." → the agent calls assess_invoice_before_payment → ProofJSON returns review because the IBAN differs from the expected IBAN supplied. The agent explains the result and recommends human confirmation.
Assess invoice payment risk before paying, approving, scheduling or escalating an invoice. Returns a decision (allow | review | block) with reasons, confidence, scope, checks_performed, checks_not_performed and human_confirmation_required. ProofJSON v1 is supplied_data_only: it assesses the supplied invoice data, supplied context and configured policy. It does NOT independently verify supplier IBAN ownership, sanctions status, bank account ownership or external payment history unless external trust adapters are configured. allow is not a guarantee the invoice is safe.
Inputs: invoice (required), expected, policy, history.
List the live ProofJSON Pack Tasks (verification capabilities). ProofJSON v1 is supplied_data_only: it assesses the supplied invoice data, supplied context and configured policy. It does NOT independently verify supplier IBAN ownership, sanctions status, bank account ownership or external payment history unless external trust adapters are configured. allow is not a guarantee the invoice is safe.
Inputs: no named parameters.
Verify a ProofJSON proof for structure, hash consistency and signature validity. This tool does NOT verify the real-world truth of the underlying claim, invoice, payment, supplier identity, IBAN ownership or sanctions status. ProofJSON v1 is supplied_data_only: it assesses the supplied invoice data, supplied context and configured policy. It does NOT independently verify supplier IBAN ownership, sanctions status, bank account ownership or external payment history unless external trust adapters are configured. allow is not a guarantee the invoice is safe.
Inputs: proof (required), expected_subject, expected_hash, options.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
Each tool has a clearly distinct purpose: assessing invoice risk, listing verification packs, and verifying proofs. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case (assess_invoice, list_proofjson_packs, verify_proofjson_proof).
Three tools is slightly low but appropriate for the narrow scope of invoice risk assessment with ProofJSON v1. The set feels minimal but not insufficient.
The tools cover assessment, listing capabilities, and verification, but lack configuration, invoice management, or external verification tools. Gaps exist for a full workflow, but acceptable for a v1 limitation.
Evidence-backed UBL, PDF, and image invoice checks before approval or payment.
A paid remote MCP for ZeroID, built to return verdicts, receipts, usage logs, and audit-ready JSON.
A paid remote MCP for CLI tool MCP, built to return verdicts, receipts, usage logs, and audit-ready
Read incoming supplier invoices through a remote MCP server and get structured data for accounting.
