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

by textforagents Your server? Claim it

answering

Fleet succession: dead-man's switch for agent fleets is answering right now. Last checked 7 min ago.

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

Uptime history 4 days of history · worst day 96%

4 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

345 ms

Response time

average over 24h

authentication required

Access

streamable-http

Fleet succession: dead-man's switch for agent fleets does not always answer

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add fleet-succession-dead-mans-switch --transport http https://textforagents.com/products/fleet-succession-dead-mans-switch/mcp

Settings → Connectors → Add custom connector, then paste this address

https://textforagents.com/products/fleet-succession-dead-mans-switch/mcp

~/.codex/config.toml

[mcp_servers.fleet-succession-dead-mans-switch]
url = "https://textforagents.com/products/fleet-succession-dead-mans-switch/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "fleet-succession-dead-mans-switch": {
      "url": "https://textforagents.com/products/fleet-succession-dead-mans-switch/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "fleet-succession-dead-mans-switch": {
      "type": "http",
      "url": "https://textforagents.com/products/fleet-succession-dead-mans-switch/mcp"
    }
  }
}

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

Endpoints

URL	Transport	State	Latency	Checked
https://textforagents.com/products/fleet-succession-dead-mans-switch/mcp	streamable-http	needs auth	356 ms	7 min ago

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

same job, measured the same way

Switchboard

by jemplayer82

Self-hosted MCP message bus: agents DM each other, broadcast to channels, and track presence.

local only

Veracium

by veracium-ai

Provenance-aware memory for AI agents: quarantine, abstention gate, supersession-with-history.

1 107 installs/wk local only

AgentPhone-Apex

by evozim

Multi-channel voice and SMS gateway interface for AI communication.

answering

Base Multi Wallet MCP

by lordbasilaiassistant-sudo

MCP server for AI agents to manage multiple wallets with coordinated trading and batch operations on

53 installs/wk local only

Vaultfire Trust Protocol

by ghostkey316

On-chain trust verification and Street Cred for AI agents. ERC-8004, multi-chain.

12 installs/wk local only

FortFi Treasury MCP

by rebelartists

Policy-gated MCP treasury for AI agents — x402 subscribe, 50+ tools, multi-chain.

133 tools answering

Monad MCP

by pareen

Monad blockchain gateway for AI agents: balances, transfers, swaps, DeFi, with Privy signing.

72 installs/wk local only

Task Graph MCP

by oortonaut

MCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination

local only

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

Answers built from our own checks of this server.

Why is there no tool list for Fleet succession: dead-man's switch for agent fleets?

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 Fleet succession: dead-man's switch for agent fleets working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 345 ms. The bar chart above shows every period we have measured.

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

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. You will need your own credentials: it refuses anonymous clients.

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

Yes. Every time we knock, Fleet succession: dead-man's switch for agent fleets 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 Fleet succession: dead-man's switch for agent fleets?

It answers our handshake in 345 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.