Remote MCP · Endpoint

thePaymentsNotes Ledger MCP server

No. thePaymentsNotes Ledger answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tpn-gateway.alwaysarafath.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.alwaysarafath/thepaymentsnotes-ledger
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
532 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verified agentic-commerce protocol status + merchant agent-readiness reports. Free on testnet.
Listing
From the official MCP registry (active).
Recent checks of thePaymentsNotes Ledger
CheckedResultHandshake
1 hour agoHandshake completed532 ms
1 day agoHandshake completed656 ms
2 days agoHandshake completed121 ms
2 days agoHandshake completed438 ms
4 days agoHandshake completed525 ms
7 days agoHandshake completed332 ms
9 days agoHandshake completed430 ms
12 days agoHandshake completed802 ms
14 days agoHandshake completed450 ms
16 days agoHandshake completed430 ms
18 days agoHandshake completed448 ms
20 days agoHandshake completed448 ms
22 days agoHandshake completed460 ms
24 days agoHandshake completed560 ms

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

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 thePaymentsNotes Ledger and makes no claim about it beyond what these checks measured.