Is the Claribi MCP server down?

mcp-registry/com.claribi/mcp-server · v1.0.0

down
Last checked 2026-10-15 12:24 UTC · handshake 11.2s

As of 2026-10-15 12:24 UTC, the Claribi MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
99.7%
checks observed
3,222
outages (90d)
7
tools
26

AI business intelligence: sign up, ingest data, run analyses, generate reports from any MCP client.

Point your MCP client at this streamable-http endpoint: https://claribi.com/mcp/v1/

Agent-readiness: B (85/100)

B (85/100): 1 error(s), 2 warning(s) across 26 tool(s); ~5,509 tokens of tool definitions.
Scores higher than 52% of 15,272 MCP servers Glimind has audited.
Its tool list costs an agent ~5,509 tokens per session — more than 60% of servers.
no tool-poisoning patterns
Schemas100
Descriptions77
Safety hints100
Token cost100
Client compatibility100
Protocol100
Reliability0
Stability96

What to fix (4)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.

11 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: create_forecast, get_forecast_run, get_forecast_trust, regenerate_forecast_narrative, run_forecast

Handshake + tools/list takes ~2,349 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.claribi/mcp-server"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.claribi/mcp-server"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.claribi%2Fmcp-server.svg)](https://glimind.com/server/mcp-registry%2Fcom.claribi%2Fmcp-server?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.claribi%2Fmcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.claribi%2Fmcp-server.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.claribi%2Fmcp-server.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.claribi%2Fmcp-server?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9181aead28fd12b1…, first seen 2026-10-17, included at leaf 11180 of 17,477. Version history · verify what your client received.

Working alternatives

Tools (26)

Compare: most reliable other servers · most reliable payments servers · most reliable ml servers · most reliable productivity servers · most reliable billing servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Claribi MCP server down right now?

As of 2026-10-15 12:24 UTC, the Claribi MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Claribi MCP server provide?

Claribi MCP server advertises 26 tools, including check_integration_status, check_pricing, create_checkout_session, create_forecast, generate_report.

How do I install Claribi MCP server?

Point your MCP client at this streamable-http endpoint: https://claribi.com/mcp/v1/

Is the Claribi MCP server safe to connect to an AI agent?

Glimind scanned all 26 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Claribi MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.