Remote MCP · Endpoint

nidhipati — proof of spend for AI agents MCP server

No. nidhipati — proof of spend for AI agents answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://rta.lat/nidhipati/mcp

The last check completed an MCP handshake.

Registry name
io.github.mrpkk/nidhipati
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
592 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Proof-of-spend and reserve checks for AI agents: receipts, spend audit, NAV, reconciliation.
Listing
From the official MCP registry (active).
Recent checks of nidhipati — proof of spend for AI agents
CheckedResultHandshake
39 minutes agoHandshake completed592 ms
3 days agoHandshake completed643 ms
13 days agoHandshake completed539 ms
13 days agoHandshake completed863 ms
15 days agoHandshake completed686 ms
16 days agoHandshake completed1.10 s
17 days agoHandshake completed549 ms
18 days agoHandshake completed934 ms
18 days agoHandshake completed742 ms
20 days agoHandshake completed715 ms
22 days agoHandshake completed729 ms
25 days agoHandshake completed925 ms

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with nidhipati — proof of spend for AI agents and makes no claim about it beyond what these checks measured.