Remote MCP · Endpoint

Tempo Atlas Projects MCP server

No. Tempo Atlas Projects answered an MCP handshake 22 minutes ago.

UpLast checked 22 minutes ago

Server URL

https://tempoatlas.net/mcp

The last check completed an MCP handshake.

Registry name
io.github.zeit-dev/tempoatlas-projects
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
425 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search Tempo ecosystem projects, retrieve project details, and list categories.
Listing
From the official MCP registry (active).
Recent checks of Tempo Atlas Projects
CheckedResultHandshake
22 minutes agoHandshake completed425 ms
9 days agoHandshake completed428 ms
10 days agoHandshake completed439 ms
11 days agoHandshake completed439 ms
12 days agoHandshake completed415 ms
14 days agoHandshake completed415 ms
14 days agoHandshake completed505 ms
15 days agoHandshake completed413 ms
17 days agoHandshake completed453 ms
19 days agoHandshake completed683 ms
21 days agoHandshake completed412 ms
24 days agoHandshake completed496 ms
26 days agoHandshake completed587 ms
28 days agoHandshake completed788 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 Tempo Atlas Projects and makes no claim about it beyond what these checks measured.