AIS Agent Flight Recorder — dead-man alerts & resume for AI agents MCP Server

by aislabs Your server? Claim it

answering

AIS Agent Flight Recorder — dead-man alerts & resume for AI agents is answering right now. Last checked 15 min ago. It exposes 5 tools.

Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links

Uptime history 12 hours of history

12 hours agonow

100.0%

Uptime 24h

41 of 41 checks

Tools

read from the server

287 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check AIS Agent Flight Recorder — dead-man alerts & resume for AI agents every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add recorder --transport http https://api.aislabs.ai/recorder/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "recorder": {
      "url": "https://api.aislabs.ai/recorder/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.recorder]
url = "https://api.aislabs.ai/recorder/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "recorder": {
      "url": "https://api.aislabs.ai/recorder/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "recorder": {
      "url": "https://api.aislabs.ai/recorder/mcp"
    }
  }
}

Available tools 5

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

capsule

fetch_capsule

Agent Flight Recorder (Gateway key) — get the last state capsule a monitored agent sent, to resume from where it died.

fleet

fleet_status

Agent Flight Recorder (Gateway key) — every monitor you own: alive / late / dead, last heartbeat, capsule preview.

heartbeat

heartbeat

Agent Flight Recorder — "still alive" ping for a registered monitor. Include capsule (any JSON ≤32KB: current step, done, next, ids) so a dead-man alert can carry resume state (stored on the key tier). status:"fail" reports a failure immediately.

monitor

delete_monitor

Agent Flight Recorder — remove a monitor (needs its secret or the owning key).

register_monitor

Agent Flight Recorder — FREE (1 monitor per alert target) / Gateway key (20 monitors + stored capsules + fleet view). Register an agent or scheduled job to be watched: you get a monitor_id + secret; the agent then calls heartbeat every period_minutes. If heartbeats stop for period + grace, the alert target (Discord/HTTPS webhook and/or email) is notified with the last state capsule and a resume link.

Endpoints

URL	Transport	State	Latency	Checked
https://api.aislabs.ai/recorder/mcp	streamable-http	answering	318 ms	15 min ago

Alternatives to AIS Agent Flight Recorder — dead-man alerts & resume for AI agents

same job, measured the same way

Heartbeat — dead-man switch for cron jobs & AI agents

by aniripsaretro-max

Dead-man switch monitors for cron & AI agents with dependency-cascade alerts. No account needed.

5 tools answering

Heartbeat Monitor

by workers-cronping-oren-cronping

Dead-man's-switch for cron jobs & AI agents. Import a crontab to arm one silent-miss alert per job.

7 tools answering

Agent Domains

by clize

Domains your AI agent can buy, point and monitor, with four-layer health checks and alerts.

local only

Pulse — heartbeat & status monitor for AI agents

by workers-notdown-app-pulse

Your agent pings once per run; get a public up/late/down status page. Auto-creates checks. One call.

4 tools answering

Watchpup

by workers-watchpup-watchpup

Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts.

12 tools answering

LastPing

by lastping

Monitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.

answering

Remoote Remote Jobs MCP

by remoote

Search remote jobs, compare salaries, create alerts, and request user-confirmed apply links.

6 tools answering

Agentguard47

by bmdhodl

Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.

41 installs/wk local only

AIS Agent Flight Recorder — dead-man alerts & resume for AI agents — questions

Answers built from our own checks of this server.

What can AIS Agent Flight Recorder — dead-man alerts & resume for AI agents do?

It exposes 5 tools, read directly from the server on our last check. Among them: delete_monitor, fetch_capsule, fleet_status, heartbeat, register_monitor. 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 AIS Agent Flight Recorder — dead-man alerts & resume for AI agents working right now?

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

How do I connect AIS Agent Flight Recorder — dead-man alerts & resume for AI agents?

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.

Does AIS Agent Flight Recorder — dead-man alerts & resume for AI agents need an API key?

No. AIS Agent Flight Recorder — dead-man alerts & resume for AI agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is AIS Agent Flight Recorder — dead-man alerts & resume for AI agents?

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