Remote MCP · Endpoint

AgentPay (all tools) MCP server

No. AgentPay (all tools) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.noah-silver/agentpay-bundle
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pay-per-call web extract, DNS/WHOIS/IP lookup, PDF/RSS/sitemap tools. x402 USDC on Base/Algorand.
Listing
From the official MCP registry (active).
Recent checks of AgentPay (all tools)
CheckedResultHandshake
2 hours agoHandshake completed151 ms
2 days agoHandshake completed486 ms
4 days agoHandshake completed159 ms
7 days agoHandshake completed180 ms
9 days agoHandshake completed256 ms
11 days agoHandshake completed231 ms
13 days agoHandshake completed218 ms
15 days agoHandshake completed62 ms
16 days agoHandshake completed189 ms
18 days agoHandshake completed243 ms
19 days agoHandshake completed303 ms
20 days agoHandshake completed362 ms
23 days agoHandshake completed59 ms
24 days agoHandshake completed47 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 (all tools) and makes no claim about it beyond what these checks measured.