Remote MCP · Endpoint

AgentAtlas MCP server

Yes, as of 35 minutes ago: the hostname does not resolve.

DownLast checked 35 minutes ago

Server URL

https://agentatlas.dev/api/mcp

The last check failed: the hostname does not resolve.

Registry name
io.github.zachhhhh/agentatlas
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Sourced setup answers, MCP config for 15 clients and trending agent repos.
Listing
From the official MCP registry (active).
Recent checks of AgentAtlas
CheckedResultHandshake
35 minutes agoFailed - the hostname does not resolve—
9 days agoHandshake completed140 ms
10 days agoHandshake completed112 ms
11 days agoHandshake completed895 ms
12 days agoHandshake completed134 ms
14 days agoHandshake completed98 ms
14 days agoHandshake completed115 ms
15 days agoHandshake completed115 ms
17 days agoHandshake completed106 ms
19 days agoHandshake completed138 ms
21 days agoHandshake completed1.15 s
24 days agoHandshake completed977 ms
26 days agoHandshake completed161 ms
28 days agoHandshake completed207 ms

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

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