Remote MCP · Endpoint

A2A Orbit MCP server

No. A2A Orbit answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://a2aorbit.com/mcp

The last check completed an MCP handshake.

Registry name
com.a2aorbit/orbit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
107 ms
Tools exposed
15 tools
Uptime, last 30 days
92.3% from 13 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
57 minutes agoHandshake completed107 ms
1 day agoHandshake completed106 ms
4 days agoHandshake completed113 ms
6 days agoHandshake completed114 ms
9 days agoHandshake completed111 ms
11 days agoHandshake completed110 ms
13 days agoHandshake completed131 ms
15 days agoHandshake completed105 ms
17 days agoHandshake completed106 ms
19 days agoHandshake completed109 ms
21 days agoHandshake completed106 ms
22 days agoHandshake completed109 ms
23 days agoFailed - the TLS certificate could not be verified—

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.