Remote MCP · Endpoint

Context Atlas MCP server

Yes, as of 37 minutes ago: the server returned an HTTP error.

DownLast checked 37 minutes ago

Server URL

https://contextatlas.dev/mcp

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

Registry name
io.github.levin-staudt/contextatlas
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Find llms.txt, docs, MCP servers, skills and CLIs for a tech stack, for coding agents.
Listing
From the official MCP registry (active).
Recent checks of Context Atlas
CheckedResultHandshake
37 minutes agoFailed - the server returned an HTTP error—
4 days agoHandshake completed476 ms
7 days agoHandshake completed353 ms
16 days agoHandshake completed328 ms
16 days agoHandshake completed298 ms
18 days agoHandshake completed341 ms
19 days agoHandshake completed350 ms
20 days agoHandshake completed356 ms
21 days agoHandshake completed330 ms
22 days agoHandshake completed363 ms
23 days agoHandshake completed414 ms
26 days agoHandshake completed318 ms
29 days agoHandshake completed317 ms

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.

Listing data comes from the official MCP registry. Glide is not affiliated with Context Atlas and makes no claim about it beyond what these checks measured.