● healthy
Public ISO 3166-1 record for BO.
Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-03-26
negotiated, not declared
MCP readiness
B · 80/100
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here A, 99.3/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (94 ms). |
| Protocol revision | 5/10 | Speaks MCP 2025-03-26, 3 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 31/31 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 31 tool(s) with descriptions. |
| Verified identity | 7/10 | Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time). |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive
(94 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.
Compared with peers
Against 52,519 reachable MCP servers in our daily snapshot (2026-11-11 23:06 UTC). Display only; it does not change search order.
- Readiness
- Higher than 45% of peers
- This listing 80 · peer median 81
- Latency
- Faster than 96% of peers
- This listing 66 ms · peer median 362 ms
Where it loses the most points
- Protocol revision −5 — Speaks MCP 2025-03-26, 3 revision(s) behind 2026-07-28.
- Freshness + modern flags −5 — not seen in a source for over 30 days.
- Auth declaration −5 — How to authenticate is not stated.
Adoption signals
Public signals from outside this directory, shown for context. They do not change search order or grades.
Listed in
Directories this entry was found in.
mcp-registry since 2026-09-09
capkey since 2026-10-26
↗
How to connect
MCP endpoint (streamable-http)
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/cc-bo/mcpJSON-RPC initialize probe
curl -X POST https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/cc-bo/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'