numproof
Integrates with LangChain as a tool and output checker for agents to verify numeric claims and reject false statements.
Integrates with OpenAI Agents SDK as an output guardrail that triggers on REFUTE verdicts to prevent incorrect numeric outputs.
Integrates with Pydantic AI as an output validator that raises a retry with counterexample when a numeric claim is refuted.
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., "@numproof verify that a 50% loss needs a 100% gain to break even"
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.
NumProof
The deterministic numeric truth layer for AI agents and spreadsheets.
Your agent writes "gross margin improved from 42.1% to 44.8%" or "the workbook is internally consistent" — NumProof tells you, deterministically, whether that number is VERIFY, REFUTE, or ABSTAIN, with a counterexample, cell/formula provenance, and a signed, machine-checkable audit bundle. It's exact arithmetic and symbolic math — not an LLM judging another LLM.
✅ Verify a single math/finance claim, or batch thousands in CI
✅ Audit
xlsx/csvrows: footing, cross-footing, balance-sheet ties, margins, formula cells — with provenance✅ Diff two report versions; evaluate covenant rule packs (DSCR, Debt/EBITDA, current ratio, …)
✅ Signed evidence bundle (JSON + HTML/PDF/ZIP) anyone can re-verify offline
✅ API · CLI · MCP server · optional x402 pay-per-call
This repo is the open-source client (SDK + MCP). The verification engine runs as a hosted service —
pip install numproof, point it at the API, done. (Same shape asstripe-python: the SDK is open, the engine is the service.)
Live demo (no key): https://numproof.com · Docs: https://numproof.com/docs
30-second start
pip install numprooffrom numproof import NumProof
np = NumProof.from_env() # NUMPROOF_API_KEY (get a free key: see below)
print(np.verify("120 + 90 + 340 + 15 == 565"))
# {'verdict': 'VERIFY', 'certificate': 'EXACT_ARITHMETIC', ...}
print(np.verify("a 50% loss needs a 100% gain to break even")) # VERIFY: (1-0.5)*(1+1.0)==1
print(np.verify("two 10% raises equal a 21% total increase")) # VERIFY
print(np.verify("operating margin is 18% when EBIT is 180 and revenue is 1000")) # VERIFYNo install? It's just HTTP:
curl -s https://numproof.com/demo -H 'Content-Type: application/json' \
-d '{"claim":"gross margin is 60% when gross profit is 600 and revenue is 1000"}'Free API key:
curl -s https://numproof.com/signup -X POST -H 'Content-Type: application/json' -d '{}'Related MCP server: agent-gate
Audit a spreadsheet (with provenance)
rows = [["Revenue", 1000], ["COGS", 400], ["Gross Profit", 600], ["Gross Margin", "60%"]]
print(np.audit_rows(rows)["verdict"]) # PASS (600/1000 == 60%, footing, ties, ...)
# covenant rule packs: DSCR, Debt/EBITDA, current ratio, custom thresholds
print(np.covenant_rows(
[["EBITDA", 500], ["Debt Service", 300], ["Debt", 1200]],
rule_pack="credit_covenants_basic",
)["verdict"])Every audit/diff/covenant result can be returned as a signed bundle + human-readable HTML/PDF
report (format="zip"). Recipients verify it without trusting you or NumProof:
curl -s https://numproof.com/audit/verify -H 'Content-Type: application/json' -d @bundle.json
# {"valid": true, "verdict": "PASS", "signer": "0x...", ...}Use it from an AI agent (MCP)
NumProof ships an MCP server so Claude / OpenAI-style agents can call it as a tool — gate every numeric claim before it reaches a user, report, or auditor.
python -m numproof.mcp{ "mcpServers": { "numproof": { "command": "python", "args": ["-m", "numproof.mcp"] } } }Or point any MCP client at the hosted descriptor: https://numproof.com/mcp.json.
See examples/ for runnable scripts (verify, audit, covenants, agent-gate, MCP).
Drop-in guardrails for agent frameworks
Verify the numbers your agent emits before it acts, in the framework you already use
(numproof/integrations/ — each lazily imports its framework, so the numproof client stays stdlib-only):
# OpenAI Agents SDK — output guardrail that trips on REFUTE
from agents import Agent
from numproof.integrations.openai_agents import numproof_output_guardrail
agent = Agent(name="...", instructions="...", output_guardrails=[numproof_output_guardrail()])OpenAI Agents SDK —
numproof.integrations.openai_agents(output guardrail / tripwire)Pydantic AI —
numproof.integrations.pydantic_ai(output validator; raisesModelRetrywith the counterexample so the model self-corrects)LangChain —
numproof.integrations.langchain(a NumProofTool+ an output checker)DeepEval (Confident AI) —
numproof.integrations.deepeval(a deterministicNumProofMetric: VERIFY → score 1.0, REFUTE → score 0.0 with the counterexample on.reason)Guardrails AI —
numproof.integrations.guardrails(a HubValidator: REFUTE →FailResultwith the counterexample, so youron_failaction — reask/fix/exception — fires)
VERIFY → pass · REFUTE → block/retry with the counterexample · ABSTAIN → pass-through (configurable). Runnable examples in examples/; install only the framework you use.
Independently re-checkable receipts (the part you can't fake)
Any verdict can be returned as a signed Verification Receipt — and you re-check it offline, trusting neither the transport nor NumProof:
pip install "numproof[verify]"
numproof-verify receipt.json --signer 0x<published-NumProof-signer>
# OK independently re-derived + signature validIt recovers the EIP-191 signer (tamper-evident) and, for value/agg/identity/sequence
claims, independently re-derives the verdict with stdlib Fraction + sympy. A tampered
field, a wrong signer, or a verdict that doesn't actually hold all fail loudly — even a receipt
NumProof itself mis-signed is caught by the re-derivation. An agent can recompute a number for
itself; it cannot issue an independent, signed attestation a second party will accept. That
independence — not the arithmetic — is the product. Format + spec: RECEIPT_FORMAT.md.
Why deterministic (and why it matters)
Generic "AI guardrails" use a model to grade a model — probabilistic, and itself can hallucinate.
NumProof recomputes the math exactly (rational arithmetic + symbolic identity checking) and
returns a reproducible verdict with a trace. When it can't prove something it says ABSTAIN
rather than guess. For finance, regulated, and agent workflows, "the number is provably right"
beats "another model thinks it looks right." Full table: comparison.md.
Pricing
Plan | Price | For |
Sandbox | $0 | web demo + free credits |
x402 PAYG | $0.005 / call | agent-to-tool, no subscription |
Builder | $29/mo | API + MCP + CLI, 2k credits |
Pro | $99/mo | batch, webhooks, CI, signed exports, 10k credits |
Finance Team | $299/mo | 5 seats, version diff, covenant packs, branded exports |
What's in this repo
The numproof Python SDK (NumProof client), the MCP server, and runnable examples — all thin
HTTP clients to the hosted API. MIT licensed. The verification engine, finance audit logic,
formal (Lean) proof tier, and signing are the hosted service and are not in this repo.
Found a wrong verdict? Open an issue with the exact claim — correctness is the whole product.
Available Tools
4 toolsaudit_rowsBInspect
Audit spreadsheet-like rows for footing, margins, formula cells, and cell provenance.
Inputs: rows (required).
covenant_rulesBInspect
Check finance covenant rules (e.g. DSCR, Debt/EBITDA) over labeled rows; rule_pack selects a built-in pack such as credit_covenants_basic. Returns a signed covenant bundle.
Inputs: rows (required), rules, rule_pack.
diff_rowsBInspect
Compare two report versions by numeric row labels with provenance.
Inputs: rows_after (required), rows_before (required).
verify_claimAInspect
Exactly verify a math/finance claim -> VERIFY/REFUTE/ABSTAIN with certificate and counterexample.
Inputs: claim (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool addresses a distinct aspect of numeric proof: auditing row-level consistency, verifying standalone claims, comparing versions, and checking covenant compliance. There is no noticeable overlap in purpose.
Three tools follow the verb_noun pattern (audit_rows, verify_claim, diff_rows), but covenant_rules is a noun_noun construction, breaking the pattern. Despite this, all names use consistent lowercase underscores, so the deviation is minor.
With four tools, the server is well-scoped for its specialized domain. Each tool covers a core operation without redundancy, and four is within the ideal range for a focused utility.
The tools cover the primary needs of numeric proof work: auditing rows, verifying claims, diffing versions, and evaluating covenant rules. No obvious missing operations for the stated purpose are apparent.
Maintenance
Related MCP Connectors
Ledger of record for AI spend: verifiable receipts, waste auditor & model arbitrage MCP.
A paid remote MCP for ZeroLang, built to return verdicts, receipts, usage logs, and audit-ready JSON
Governed MCP: agent audit, provenance, deterministic checks, and receipt-backed FragGate execution.
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceCryptographic proof of every AI decision. An immutable, verifiable audit trail MCP server.1MIT
- AlicenseBqualityCmaintenanceAn MCP server that enforces fail-closed deterministic checks, independent refute-first review, and tamper-evident hash-chained receipts for AI agent outputs before claiming completion.43MIT
- AlicenseNot gradedqualityCmaintenanceMCP server providing deterministic accounting tools for AI agents, including bank statement parsing, document classification, money math, and webhook verification.2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server for double-entry bookkeeping with idempotent writes, immutable entries, and audit trail. Enables trustworthy financial recording and verification through natural language.31 npmMIT