Remote MCP · Endpoint

AgentPay Doc Tools MCP server

No. AgentPay Doc Tools answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://agentpay-tools.agentpay-apis.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.noah-silver/agentpay-tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
174 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pay-per-call PDF to text, RSS/Atom to JSON, sitemap to URLs for agents. x402 USDC, Base/Algorand.
Listing
From the official MCP registry (active).
Recent checks of AgentPay Doc Tools
CheckedResultHandshake
2 hours agoHandshake completed174 ms
2 days agoHandshake completed397 ms
4 days agoHandshake completed156 ms
7 days agoHandshake completed229 ms
9 days agoHandshake completed250 ms
11 days agoHandshake completed167 ms
13 days agoHandshake completed211 ms
15 days agoHandshake completed193 ms
16 days agoHandshake completed230 ms
18 days agoHandshake completed205 ms
19 days agoHandshake completed357 ms
20 days agoHandshake completed225 ms
23 days agoHandshake completed47 ms
24 days agoHandshake completed38 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 AgentPay Doc Tools and makes no claim about it beyond what these checks measured.