clariBI
REMOTE · CLARIBI.COM · 2 COMPONENTS
AI business intelligence: sign up, ingest data, run analyses, generate reports from any MCP client.
Available components
Last scanned (52 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 20 Aug 2026.
Category Data and Analytics
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
Recent critical change
TLS certificate (21 Aug 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS check failed: the certificate is expired or not yet valid (as of 2026-08-20). See how to fix → View diagnostics → Fail
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared sse, but the TLS certificate failed verification. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Aug 26 −5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 24 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Aug 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- HSTS header: pass → unverified ▼ security
- Transport: Transport check failed: declared sse, but the TLS certificate failed verification. security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 +9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Aug 2026 · Probed https://claribi.com/mcp/v1/sse
TLS invalid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
Chain error: expired
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=claribi.com | CN=E8,O=Let's Encrypt,C=US | 22 May 2026 | 20 Aug 2026 | ECDSA 256 | ECDSA-SHA384 | 610c37ca92f0b88a922528c4c72a7f0ac04 |
| SANs: claribi.com, www.claribi.com | ||||||
| CN=E8,O=Let's Encrypt,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 Mar 2024 | 12 Mar 2027 | ECDSA 384 | SHA256-RSA | 63959363c24e7082715918bfc3d7ed56 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of claribi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| claribi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://claribi.com/mcp/v1/sse | TLS failed | ||
| http (plaintext) | http://claribi.com/mcp/v1/sse | HTTPS enforced | 301 | https://claribi.com/mcp/v1/sse |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
No tool schema has been captured from this endpoint yet.
How do I install the clariBI MCP server?
clariBI is a hosted endpoint at https://claribi.com/mcp/v1/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · claribi.com
claude mcp add --transport http com-claribi-mcp-server 'https://claribi.com/mcp/v1/sse'
What is the clariBI MCP server?
clariBI is an MCP server listed in the public MCP registry as com.claribi/mcp-server. AI business intelligence: sign up, ingest data, run analyses, generate reports from any MCP client. This page covers its hosted endpoint (https://claribi.com/mcp/v1/sse).
Does the clariBI MCP server require authentication?
Its publisher declares no required credentials for clariBI. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the clariBI MCP server still maintained?
clariBI has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 20 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.