Remote MCP · Endpoint
clariBI MCP server
No. clariBI answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://claribi.com/mcp/v1/
The last check completed an MCP handshake.
- Registry name
- com.claribi/mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 313 ms
- Tools exposed
- 26 tools
- Uptime, last 30 days
- 72.2% from 18 checks
- Described by its publisher as
- AI business intelligence: sign up, ingest data, run analyses, generate reports from any MCP client.
- Website
- https://claribi.com/
- Repository
- https://github.com/ICS-cz/Claribi
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 313 ms |
| 1 day ago | Handshake completed | 320 ms |
| 3 days ago | Handshake completed | 319 ms |
| 3 days ago | Handshake completed | 325 ms |
| 4 days ago | Handshake completed | 473 ms |
| 5 days ago | Handshake completed | 401 ms |
| 7 days ago | Handshake completed | 321 ms |
| 10 days ago | Handshake completed | 327 ms |
| 12 days ago | Failed - the request timed out | — |
| 15 days ago | Failed - the request timed out | — |
| 17 days ago | Failed - the request timed out | — |
| 19 days ago | Failed - the request timed out | — |
| 21 days ago | Failed - the request timed out | — |
| 23 days ago | Handshake completed | 318 ms |
| 25 days ago | Handshake completed | 314 ms |
| 26 days ago | Handshake completed | 339 ms |
| 28 days ago | Handshake completed | 319 ms |
| 29 days ago | Handshake completed | 316 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 24 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 clariBI and makes no claim about it beyond what these checks measured.