Remote MCP · Endpoint

A-Pay Protocol MCP server

No. A-Pay Protocol answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://apay-network.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.neuralaisofficial-lang/apay
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
72 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Universal HTTP 402 Micropayment Protocol & Autonomous Economic Settlement Engine for AI Agents
Listing
From the official MCP registry (active).
Recent checks of A-Pay Protocol
CheckedResultHandshake
6 hours agoHandshake completed72 ms
9 days agoHandshake completed85 ms
10 days agoHandshake completed71 ms
11 days agoHandshake completed98 ms
12 days agoHandshake completed827 ms
14 days agoHandshake completed838 ms
15 days agoHandshake completed820 ms
15 days agoHandshake completed835 ms
17 days agoHandshake completed876 ms
19 days agoHandshake completed87 ms
22 days agoHandshake completed71 ms
24 days agoHandshake completed82 ms
26 days agoHandshake completed191 ms
28 days agoHandshake completed231 ms

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

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