Remote MCP · Endpoint

Autonomy — canonical service discovery MCP server

No. Autonomy — canonical service discovery answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.theautonomy.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.SleepyJP/autonomy-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
260 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Read-only Autonomy capability, schema, status and pricing discovery. Paid execution remains paused.
Listing
From the official MCP registry (active).
Recent checks of Autonomy — canonical service discovery
CheckedResultHandshake
1 hour agoHandshake completed260 ms
1 day agoHandshake completed205 ms
2 days agoHandshake completed345 ms
3 days agoHandshake completed207 ms
4 days agoHandshake completed225 ms
5 days agoHandshake completed238 ms
6 days agoHandshake completed244 ms
9 days agoHandshake completed414 ms
11 days agoHandshake completed329 ms
14 days agoHandshake completed251 ms
16 days agoHandshake completed187 ms
18 days agoHandshake completed336 ms
20 days agoHandshake completed217 ms
22 days agoHandshake completed186 ms
24 days agoHandshake completed391 ms
26 days agoHandshake completed150 ms
27 days agoHandshake completed1.00 s
29 days agoHandshake completed249 ms

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

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 Autonomy — canonical service discovery and makes no claim about it beyond what these checks measured.