mcpbeat Sign in

Klisten FailBox MCP Server

answering

Klisten FailBox is answering right now. Last checked 4 min ago.

Persist failure simulations. No external fault injection or transfers. Customer key required.

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
927 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Klisten FailBox 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 4 min ago.

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

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://api.klisten.co.kr/mcp/failbox streamable-http needs auth 817 ms 4 min ago

Alternatives to Klisten FailBox

same job, measured the same way
K
Klisten MeterMCP
by co-klisten-api

Read your organization usage records. No payments or transfers. Customer API key required.

answering
K
Klisten AgentScore
by co-klisten-api

Read private agent activity, not identity or reputation scores. Customer key required.

answering
K
Klisten DeadlineEngine
by co-klisten-api

Compute explicit durations. No reminders or legal guarantees. Customer key required.

answering
K
Klisten ActionCheck
by co-klisten-api

Check proposed actions against existing policies. Never executes actions. Customer key required.

answering
K
Klisten SchemaShield
by co-klisten-api

Store and compare organization JSON snapshots. No database crawling. Customer key required.

answering
K
Klisten ClearGate
by co-klisten-api

Check existing content grants and expiry. No content fetching. Customer key required.

answering
Firefox Addons MCP
by mrfentmen

Search Firefox browser extensions on AMO. No key required.

86 installs/wk local only
K
Klisten AgentEscrow
by co-klisten-api

Read unfunded contract drafts. No deposits, payouts or settlement. Customer key required.

answering

Klisten FailBox — questions

Answers built from our own checks of this server.

Why is there no tool list for Klisten FailBox?
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 Klisten FailBox 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 927 ms. The bar chart above shows every period we have measured.
How do I connect Klisten FailBox?
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 credentials: it refuses anonymous clients.
Does Klisten FailBox need an API key?
Yes. Every time we knock, Klisten FailBox 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 Klisten FailBox?
It answers our handshake in 927 ms on average, which is faster than 8% 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.