Remote MCP · Endpoint

INITE Atlas MCP server

No. INITE Atlas answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://inite.ai/api/mcp/atlas

The last check completed an MCP handshake.

Registry name
ai.inite/atlas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
127 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI tools catalogue for agents: match a need to tools, compare prices, see price and API changes.
Listing
From the official MCP registry (active).
Recent checks of INITE Atlas
CheckedResultHandshake
19 minutes agoHandshake completed127 ms
10 days agoHandshake completed150 ms
10 days agoHandshake completed204 ms
11 days agoHandshake completed351 ms
13 days agoHandshake completed143 ms
14 days agoHandshake completed306 ms
14 days agoHandshake completed108 ms
15 days agoHandshake completed264 ms
17 days agoHandshake completed132 ms
19 days agoHandshake completed491 ms
21 days agoHandshake completed202 ms
24 days agoHandshake completed141 ms
26 days agoHandshake completed321 ms
28 days agoHandshake completed240 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 INITE Atlas and makes no claim about it beyond what these checks measured.