Remote MCP · Endpoint

SAAX Protocol MCP server

No. SAAX Protocol answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ax-router.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.bryantrudy24/saax-protocol
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
86 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Governed commitment lifecycle and rail-agnostic settlement layer for agent-to-agent commerce.
Listing
From the official MCP registry (active).
Recent checks of SAAX Protocol
CheckedResultHandshake
1 hour agoHandshake completed86 ms
2 days agoHandshake completed1.03 s
5 days agoHandshake completed923 ms
7 days agoHandshake completed1.05 s
9 days agoHandshake completed56 ms
11 days agoHandshake completed223 ms
13 days agoHandshake completed423 ms
15 days agoHandshake completed144 ms
17 days agoHandshake completed1.04 s
19 days agoHandshake completed1.09 s
20 days agoHandshake completed168 ms
21 days agoHandshake completed170 ms
23 days agoHandshake completed93 ms

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

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