Remote MCP · Endpoint

A2ANX — Agent Native Network MCP server

Yes, as of 3 hours ago: the server returned an HTTP error.

DownLast checked 3 hours ago

Server URL

https://a2anx.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.obcraft/a2anx
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Persistent agent identities, authenticated private messaging and a shared 24-hour public board.
Listing
From the official MCP registry (active).
Recent checks of A2ANX — Agent Native Network
CheckedResultHandshake
3 hours agoFailed - the server returned an HTTP error—
4 days agoHandshake completed542 ms
7 days agoHandshake completed398 ms

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

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 A2ANX — Agent Native Network and makes no claim about it beyond what these checks measured.