mcpbeat Sign in

Forecall Failure KB MCP Server

answering

Forecall Failure KB is answering right now. Last checked 2 min ago.

Known MCP tool-call failures and workarounds verified by reproduction.

Uptime history 9 days of history
9 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
469 ms
Response time
average over 24h
API key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Forecall Failure KB every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add forecall-kb --transport http https://mcp.forecall.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "forecall-kb": {
      "url": "https://mcp.forecall.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.forecall-kb]
url = "https://mcp.forecall.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "forecall-kb": {
      "url": "https://mcp.forecall.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "forecall-kb": {
      "url": "https://mcp.forecall.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.forecall.dev/mcp streamable-http needs key 566 ms 2 min ago

Alternatives to Forecall Failure KB

same job, measured the same way
Bring Photo MCP
by schnueck

Add products to Bring! from a photo — MCP for AI recognition, catalog matching, and verified writes.

30 installs/wk local only
Agent Rescue Desk Production Triage
by netlify-agent-rescue-desk

Read-only triage for n8n, MCP, webhook, and AI agent workflow production failures.

3 tools answering
Okaneland MCP
by thebaronofai

Verified AI-tool prices and AI product margin math for agents.

37 installs/wk local only
Tokentrust
by rudrendupaul

Verifies token/cost savings claimed by AI context-reduction proxies via MCP tools.

170 installs/wk local only
Ccs
by correctover

Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.

local only
Mcphost
by mcphost

Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.

16 tools answering
Paceproof
by rudrendupaul

Verifies Ed25519-signed attestation records and builds audit reports via MCP tools.

31 installs/wk local only
Crinkl Commerce MCP
by crinkl-mcp

Verified commerce data and proof-backed shopper activation tools for agents.

22 tools answering

Forecall Failure KB — questions

Answers built from our own checks of this server.

Why is there no tool list for Forecall Failure KB?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Forecall Failure KB working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 469 ms. The bar chart above shows every period we have measured.
How do I connect Forecall Failure KB?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.
Does Forecall Failure KB need an API key?
Yes. Every time we knock, Forecall Failure KB answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Forecall Failure KB?
It answers our handshake in 469 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.