mcpbeat Sign in

Killcord MCP Server

not responding

Killcord is listed as active in the registry but did not answer our last check. It exposes 1 tools.

Dead-man's switch for Anthropic API spend: kills the key the instant it crosses a limit you set.

Uptime history 50 days of history · worst day 0%
50 days agonow
0.0%
Uptime 24h
0 of 91 checks
1
Tools
read from the server
103 ms
Response time
average over 24h
open, no key
Access
streamable-http

Killcord does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 6 min ago.

run in your terminal
claude mcp add killcord --transport http https://www.edgethirteen.com/api/mcp/killcord
Settings → Connectors → Add custom connector, then paste this address
https://www.edgethirteen.com/api/mcp/killcord
~/.codex/config.toml
[mcp_servers.killcord]
url = "https://www.edgethirteen.com/api/mcp/killcord"
.cursor/mcp.json
{
  "mcpServers": {
    "killcord": {
      "url": "https://www.edgethirteen.com/api/mcp/killcord"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "killcord": {
      "type": "http",
      "url": "https://www.edgethirteen.com/api/mcp/killcord"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

killcord
get_killcord
Get the killcord script: a dead-man's switch for Anthropic API spend. Self-hosted, dependency-free Node script that polls Anthropic's real Admin Usage & Cost API and deactivates the API key the instant spend crosses a limit -- for stopping a runaway agent loop, not just alerting on it. Returns the full script source plus a ready-to-run setup snippet, optionally pre-filled with the workspace/limit/keys you provide, so it can be written straight into the project being worked on.

Endpoints

URLTransportStateLatencyChecked
https://www.edgethirteen.com/api/mcp/killcord streamable-http answering 103 ms 6 min ago

Alternatives to Killcord

same job, measured the same way
Hookpulse
by hookpulse

Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.

30 tools answering
AgentiSend
by fortuneflick

Email API for apps and AI agents: budgets per key, a kill switch, refusals that name the fix.

45 installs/wk answering
Netcafe Memory
by ainetcafe

Cross-session, cross-device memory for your agent: remember and recall notes. No key to start.

4 tools answering
Pastaclean
by pastaclean

Search and order at pastaclean.tv for your human. Limits set by the customer, customer pays.

116 installs/wk answering
K
Kit Lite
by workers-randall-75d-kit-lite

Instant x402 spend-cap pack for agents. get_quote then buy_intel_pack 5 USDC Base. No human.

6 tools answering
Fleet MCP
by simplyminimal

An MCP server that provides tools for managing and monitoring your Fleet Device Management instance.

245 installs/wk local only
API Key Case
by melavern

Local MCP tools for secret status and guarded deployment. Values never reach the agent.

58 installs/wk local only
Scandit
by scandit

Create a Scandit account, get trial license keys and set up the Scandit SDK in your app.

answering

Killcord — questions

Answers built from our own checks of this server.

What can Killcord do?
It exposes 1 tools, read directly from the server on our last check. Among them: get_killcord. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Killcord working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 103 ms. The bar chart above shows every period we have measured.
The registry lists Killcord as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Killcord?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Killcord need an API key?
No. Killcord completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.