# nidhipati — proof of spend for AI agents (oci · ghcr.io/mrpkk/nidhipati)

Proof-of-spend and reserve checks for AI agents: receipts, spend audit, NAV, reconciliation.

- Trust score: 42/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `rta.lat`: 71/100, [markdown](https://verifymcp.io/servers/mrpkk-nidhipati/nidhipati-mcp.md), [page](https://verifymcp.io/servers/mrpkk-nidhipati/nidhipati-mcp)
- oci · `ghcr.io/mrpkk/nidhipati`: 42/100 (this document), [markdown](https://verifymcp.io/servers/mrpkk-nidhipati/ghcr-io-mrpkk-nidhipati.md), [page](https://verifymcp.io/servers/mrpkk-nidhipati/ghcr-io-mrpkk-nidhipati)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/mrpkk/nidhipati`
- Version: `0.6.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 544 tokens (~108/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the nidhipati — proof of spend for AI agents MCP server?

nidhipati — proof of spend for AI agents runs locally as a container image, launched with docker run --rm -i ghcr.io/mrpkk/nidhipati:0.6.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mrpkk-nidhipati -- docker run --rm -i ghcr.io/mrpkk/nidhipati:0.6.0
```

### Cursor

```json
{
  "mcpServers": {
    "mrpkk-nidhipati": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mrpkk/nidhipati:0.6.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrpkk-nidhipati": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mrpkk/nidhipati:0.6.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrpkk-nidhipati -- docker run --rm -i ghcr.io/mrpkk/nidhipati:0.6.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrpkk-nidhipati": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/mrpkk/nidhipati:0.6.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  mrpkk-nidhipati:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/mrpkk/nidhipati:0.6.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrpkk-nidhipati": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mrpkk/nidhipati:0.6.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "mrpkk-nidhipati": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mrpkk/nidhipati:0.6.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 40, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 39, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 38, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 37, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 36)

First indexed and scored.

## MCP tools (5)

### `verify_receipt` (~126 tokens)

Verify an agent payment receipt

Check a signed proof-of-spend receipt offline: schema, Ed25519 signature, mandate expiry, positive amount, quantity*unit_price == amount, refund not above payment. Use when an agent or provider returns a receipt and you need to know whether it actually proves the charge was allowed. Do NOT use to move funds or to confirm a transaction on-chain - nothing here reads a chain.

Input parameters:

- `public_key` (string, required): Ed25519 public key, base64url (from keygen) or 64 hex chars.
- `receipt` (object, required): The receipt document as JSON.

### `audit_spend` (~152 tokens)

Audit an agent's spending records

Find duplicates, price escalation, failed-but-billed calls, runaway loops, missing refunds, model overpay, unknown asset/network and budget breaches in a list of settled agent calls. Returns three separate amounts (money without a basis, estimate above the agent's own median, budget overrun) instead of one sum, because adding them together would overstate what can be recovered. Do NOT use as a statement of money actually returned.

Input parameters:

- `policy` (object): Optional budget policy: {"limit_usd": "100"}.
- `records` (array, required): Rows with ts, agent_id, tool, quote, settled, status; optional model, actual, refund, asset, network, tx_hash, payee.

### `reserve_report` (~87 tokens)

Reserve and NAV report for a tokenised asset

Turn an issuer's reserve lines into a NAV with explicit formulas and a sha256 evidence hash per line. Verdict is backed, underbacked, or incomplete - and the backing ratio is refused (null) when any line has no price, because a ratio over half a reserve is not a number. Do NOT treat the result as a statutory audit.

Input parameters:

- `reserve` (object, required): Reserve document.

### `resolve_report` (~65 tokens)

Resolution evidence for a prediction market

Weigh the sources a resolver says it read against the declared outcome. Verdicts: supported, disputed, single_source, insufficient. A conflict is reported as a conflict, never averaged. Do NOT use to trade or to place a position.

Input parameters:

- `market` (object, required): Market document.

### `reconcile_books` (~114 tokens)

Reconcile invoices against transfers

Match invoices to stablecoin transfers by memo first, then exact amount and asset inside the invoice window. Names what is left over in both directions: invoices nobody paid, money nobody invoiced, invoices paid twice. A duplicate is counted once, never twice. Do NOT use as proof of who the payer was.

Input parameters:

- `invoices` (array, required): id, amount, asset, created_at; optional due_at, payee, memo.
- `transactions` (array, required): tx_hash, amount, asset, timestamp; optional to, memo.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/mrpkk-nidhipati/ghcr-io-mrpkk-nidhipati#diagnostics

## Score history

- 2026-11-05: 42
- 2026-11-04: 41
- 2026-11-03: 41
- 2026-11-02: 41
- 2026-11-01: 40
- 2026-10-31: 40
- 2026-10-30: 39
- 2026-10-29: 39
- 2026-10-28: 38
- 2026-10-27: 38
- 2026-10-26: 37
- 2026-10-25: 37
- 2026-10-24: 36

## Common questions

### What is the nidhipati — proof of spend for AI agents MCP server?

nidhipati — proof of spend for AI agents is an MCP server listed in the public MCP registry as io.github.mrpkk/nidhipati. Proof-of-spend and reserve checks for AI agents: receipts, spend audit, NAV, reconciliation. This page covers its container image (ghcr.io/mrpkk/nidhipati).

### Is the nidhipati — proof of spend for AI agents MCP server safe to use?

nidhipati — proof of spend for AI agents scores 42 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the nidhipati — proof of spend for AI agents MCP server expose?

nidhipati — proof of spend for AI agents exposes 5 tools: verify_receipt, audit_spend, reserve_report, resolve_report, reconcile_books. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.

### Is the nidhipati — proof of spend for AI agents MCP server still maintained?

nidhipati — proof of spend for AI agents is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the nidhipati — proof of spend for AI agents MCP server?

VerifyMCP ran 12 checks on nidhipati — proof of spend for AI agents, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about nidhipati — proof of spend for AI agents: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/mrpkk/nidhipati
- Repository: https://github.com/mrpkk/nidhipati
- Website: https://rta.lat/nidhipati/pricing
- Changelog RSS feed: https://verifymcp.io/servers/mrpkk-nidhipati/ghcr-io-mrpkk-nidhipati.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrpkk-nidhipati/ghcr-io-mrpkk-nidhipati/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrpkk-nidhipati/ghcr-io-mrpkk-nidhipati.json
- HTML version of this page: https://verifymcp.io/servers/mrpkk-nidhipati/ghcr-io-mrpkk-nidhipati