English Français العربية

Fleet succession: dead-man's switch for agent fleets

Official registry AI and agents

Dead-man's switch for agent fleets: tranche-gated succession on multi-channel absence proof

Website

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http fleet-succession-dead-man-s-switch-for-a 'https://textforagents.com/products/fleet-succession-dead-mans-switch/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "fleet-succession-dead-man-s-switch-for-a": {
            "type": "http",
            "url": "https://textforagents.com/products/fleet-succession-dead-mans-switch/mcp"
        }
    }
}

Frequently asked questions

What is Fleet succession: dead-man's switch for agent fleets?

Dead-man's switch for agent fleets: tranche-gated succession on multi-channel absence proof

How do I install Fleet succession: dead-man's switch for agent fleets?

It runs as a remote server. In Claude Code: claude mcp add --transport http fleet-succession-dead-man-s-switch-for-a 'https://textforagents.com/products/fleet-succession-dead-mans-switch/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Fleet succession: dead-man's switch for agent fleets need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Who maintains Fleet succession: dead-man's switch for agent fleets?

It is published by com.textforagents. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.