Remote MCP · Endpoint

Oliver's mTOR Atlas MCP server

No. Oliver's mTOR Atlas answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mtor-atlas-mcp.mtor-atlas.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.open-mtor-atlas/mtor-atlas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
252 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Evidence-labelled mTOR research: studies, entities, pathway claims, contradictions, open questions.
Listing
From the official MCP registry (active).
Recent checks of Oliver's mTOR Atlas
CheckedResultHandshake
2 hours agoHandshake completed252 ms
2 days agoHandshake completed323 ms
4 days agoHandshake completed173 ms
7 days agoHandshake completed164 ms
9 days agoHandshake completed62 ms
11 days agoHandshake completed343 ms
13 days agoHandshake completed192 ms
15 days agoHandshake completed49 ms
16 days agoHandshake completed69 ms
18 days agoHandshake completed222 ms
19 days agoHandshake completed312 ms
20 days agoHandshake completed189 ms
23 days agoHandshake completed117 ms
24 days agoHandshake completed208 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 Oliver's mTOR Atlas and makes no claim about it beyond what these checks measured.