Remote MCP · Endpoint

Agent Service Atlas MCP server

No. Agent Service Atlas answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://agentserviceatlas.com/mcp

The last check completed an MCP handshake.

Registry name
com.agentserviceatlas/agent-service-atlas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
130 ms
Tools exposed
10 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Find any agent service, and check it before you pay for it or rely on it.
Listing
From the official MCP registry (deprecated).
Recent checks of Agent Service Atlas
CheckedResultHandshake
19 minutes agoHandshake completed130 ms
10 days agoHandshake completed548 ms
10 days agoHandshake completed975 ms
11 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed102 ms
14 days agoHandshake completed445 ms
14 days agoHandshake completed385 ms
15 days agoHandshake completed706 ms
17 days agoHandshake completed116 ms
19 days agoHandshake completed162 ms
21 days agoHandshake completed103 ms
24 days agoHandshake completed72 ms
26 days agoHandshake completed281 ms
28 days agoHandshake completed291 ms

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

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