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

What it can reach

From its install config and its own description; a sandbox run will confirm this later.

Checks on v0.1.0

1. Real tool

   passrules 2026-09-29.1 · 3 hours ago

2. Static scan

   passrules 2026-09-29.1 · 3 hours ago

3. Claims check

   skippedrules 2026-09-29.1 · 3 hours ago
   • infoLLM claims check is not configured on this deploy.

Install

Each app still asks you to confirm. Everything is pinned to the version checked above.

{
  "servers": {
    "recorder": {
      "type": "http",
      "url": "https://api.aislabs.ai/recorder/mcp"
    }
  }
}

Tools it offers

As the server describes them. This text comes from the publisher and is shown as-is.

• 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.

• 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.

• fetch_capsule

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

• fleet_status

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

• delete_monitor

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