Boolsai Scan / status

Boolsai Scan status

Operational · last checked 18:18 UTC · 446 ms · checked every about 5 minutes

Uptime

24 hours

100.000%

7 days

100.000%

30 days

100.000%

90 days

98.57%

90 days agotoday

Handshake latency p50 1252 ms · p95 3263 ms · mean time to recover 367 min

Incidents (90 days)

Outage · 2026-09-21 23:12 UTC · 6.1 h · rate_limit

Outage · 2026-09-18 23:13 UTC · 6.2 h · rate_limit

Outage · 2026-09-16 23:58 UTC · 6.1 h · rate_limit

Outage · 2026-09-15 21:44 UTC · 6.1 h · rate_limit

Outage · 2026-09-13 23:03 UTC · 6.1 h · rate_limit

Outage · 2026-09-11 15:18 UTC · 18.2 h · rate_limit

How this is measured

Checked by Glimind's probe (initialize + tools/list, never a tool call) from one region. Uptime counts a server as up when it completes the handshake, including when it asks for credentials. An outage starts at the first failed check, so short blips between checks are not seen. Every server is measured the same way; an owner's plan never changes these numbers. Owner updates are the owner's own words and sit next to the measurements, not in place of them.

JSON: /v1/status/mcp-registry/ai.boolsai/scan · signed proof: /v1/proof/mcp-registry/ai.boolsai/scan · Own this server?