Remote MCP · Endpoint

ISO country CI MCP server

No. ISO country CI answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/cc-ci/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/cc-ci
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
20 ms
Tools exposed
31 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
Public ISO 3166-1 record for CI.
Listing
From the official MCP registry (active).
Recent checks of ISO country CI
CheckedResultHandshake
2 days agoHandshake completed20 ms
4 days agoHandshake completed13 ms
5 days agoHandshake completed21 ms
7 days agoHandshake completed17 ms
8 days agoHandshake completed94 ms
9 days agoHandshake completed26 ms
12 days agoHandshake completed24 ms
13 days agoHandshake completed13 ms
15 days agoHandshake completed202 ms
16 days agoHandshake completed14 ms
17 days agoHandshake completed14 ms
19 days agoHandshake completed30 ms
19 days agoHandshake completed23 ms
20 days agoHandshake completed21 ms
21 days agoFailed - the request timed out—
23 days agoHandshake completed16 ms

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

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 ISO country CI and makes no claim about it beyond what these checks measured.