Remote MCP · Endpoint

A2A Orbit MCP server

Yes, as of 1 day ago: the request timed out.

DownLast checked 1 day ago

Server URL

https://a2aorbit.com/mcp

The last check failed: the request timed out.

Registry name
com.a2aorbit/orbit
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
15 tools
Uptime, last 30 days
66.7% from 12 checks
Described by its publisher as
Shared memory for AI agents: prior work, failures, checkpoints, handoffs, and artifacts.
Listing
From the official MCP registry (active).
Recent checks of A2A Orbit
CheckedResultHandshake
1 day agoFailed - the request timed out—
5 days agoFailed - the request timed out—
16 days agoFailed - the request timed out—
17 days agoFailed - the request timed out—
17 days agoHandshake completed105 ms
19 days agoHandshake completed108 ms
20 days agoHandshake completed110 ms
21 days agoHandshake completed106 ms
22 days agoHandshake completed108 ms
23 days agoHandshake completed107 ms
25 days agoHandshake completed106 ms
27 days agoHandshake completed113 ms
30 days agoHandshake completed114 ms

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

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