Remote MCP · Endpoint

Atlas absence index MCP server

No. Atlas absence index answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://atlas.geosensor.tech/mcp

The last check completed an MCP handshake.

Registry name
tech.geosensor.atlas/absence-index
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
366 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Measured rates at which web services lack machine-readable capabilities. Research demonstrator.
Listing
From the official MCP registry (active).
Recent checks of Atlas absence index
CheckedResultHandshake
3 hours agoHandshake completed366 ms
2 days agoHandshake completed328 ms
4 days agoHandshake completed382 ms
6 days agoHandshake completed330 ms
8 days agoHandshake completed373 ms
10 days agoHandshake completed330 ms
12 days agoHandshake completed364 ms
14 days agoHandshake completed324 ms
15 days agoHandshake completed380 ms
16 days agoHandshake completed325 ms
18 days agoHandshake completed335 ms
20 days agoHandshake completed325 ms
22 days agoHandshake completed329 ms
24 days agoHandshake completed333 ms

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

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