Killcord

com.edgethirteen.wwwPublished by www.edgethirteen.comOfficial publisherv1.0.0Updated Oct 24, 2026

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

The publisher's own server: Accessproof

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint that acts as a dead-man's switch for Anthropic API spend, revoking the API key as soon as it crosses a limit you set.

What you can do
  • The listing names no tools, so capabilities come from the short description only.
  • It is described as a dead-man's switch for Anthropic API spend.
  • It kills the API key the instant spending crosses a limit you configure.
  • It runs as a remote endpoint rather than a local package.
When to use it
Worth considering if you give assistants or automated agents access to an Anthropic API key and want a hard spending cap that revokes the key automatically instead of relying on billing alerts.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's site; no packages, environment variables or headers are declared. The description implies you must set a spend limit and connect it to an Anthropic API key, but the listing does not document how.
Before you install
It is designed to revoke (kill) an Anthropic API key, so a misconfigured limit could disable your key and break running workloads. It necessarily deals with API credentials and spend data, and the listing gives no details on authentication, storage or what is sent to third parties; verify these before connecting a production key.

Installation

In SourceWeft

  1. Open Killcord in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.edgethirteen.www%2Fkillcord/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "killcord": {
      "type": "http",
      "url": "https://www.edgethirteen.com/api/mcp/killcord"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Edgethirteen integrations