Remote MCP · Endpoint

Latitude 10 Agent Readiness MCP server

No. Latitude 10 Agent Readiness answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://latitude10.tech/mcp/readiness

The last check completed an MCP handshake.

Registry name
tech.latitude10/agent-readiness
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.65 s
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Scores how well AI agents will use your API, 0-100, from its OpenAPI spec. Free and read-only.
Listing
From the official MCP registry (active).
Recent checks of Latitude 10 Agent Readiness
CheckedResultHandshake
1 hour agoHandshake completed2.65 s
2 days agoHandshake completed4.69 s
5 days agoHandshake completed2.23 s
7 days agoHandshake completed1.14 s
9 days agoHandshake completed751 ms
11 days agoHandshake completed764 ms
13 days agoHandshake completed890 ms
16 days agoHandshake completed1.00 s
18 days agoHandshake completed1.31 s
19 days agoHandshake completed540 ms
21 days agoHandshake completed938 ms
22 days agoHandshake completed1.06 s
23 days agoHandshake completed572 ms
26 days agoHandshake completed152 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 Latitude 10 Agent Readiness and makes no claim about it beyond what these checks measured.