Draft v0.1 · open spec · no custody

MCP server for agent spend

Nidhipati MCP server: verify a Proof of Spend receipt, audit spend, reserve NAV, prediction evidence and reconcile stablecoin books. Read-only, no keys, no network.
Written scope and written report — no calls. No wallet access for the first scan.

Five read-only tools for an agent

An agent does not run a shell. The MCP server exposes the same checks as the CLI over JSON-RPC stdio. Input is data only: no file paths, no network, no chain access, no keys.

  • verify_receipt — Proof of Spend checks
  • audit_spend — CSV rows → findings
  • reserve_report — RWA NAV / proof of reserve
  • resolve_report — prediction evidence
  • reconcile_books — invoices ↔ transfers

Run it

python3 -m nidhipati_proof.mcp_stdio
# or
docker build -t nidhipati-mcp .
docker run -i --rm nidhipati-mcp

Read-only tools. A failed check returns isError with the report, not a protocol failure.

Client config

{
  "mcpServers": {
    "nidhipati": {
      "command": "python3",
      "args": ["-m", "nidhipati_proof.mcp_stdio"]
    }
  }
}

No API key, no account, no outbound network. The agent sends data; the server returns a report.

Official MCP Registry: io.github.mrpkk/nidhipati · Glama: glama.ai/mcp/servers/mrpkk/nidhipati · OCI: ghcr.io/mrpkk/nidhipati:0.6.0

Why MCP

Catalog discovery is the one channel that already produced measured traffic for our attest server. MCP lets an agent call the audit without a shell — and lets a catalog list it. The server is intentionally read-only: it cannot move money.

Free scan

Prefer a human-written report? Send a CSV/JSON; no keys.

Request a free scan