Official MCP RegistryListed
AIS Agent Flight Recorder — dead-man alerts & resume for AI agents
Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links
First seen 2 Oct 2026. Evidence as of 3 Oct 2026.
5
Tools
From an anonymous probe
1
Source listings
Each with its own history
0
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| delete_monitor | Agent Flight Recorder — remove a monitor (needs its secret or the owning key). | Not declared |
| fetch_capsule | Agent Flight Recorder (Gateway key) — get the last state capsule a monitored agent sent, to resume from where it died. | Not declared |
| fleet_status | Agent Flight Recorder (Gateway key) — every monitor you own: alive / late / dead, last heartbeat, capsule preview. | Not declared |
| 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. | Not declared |
| 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. | Not declared |
Change history
No changes since the first observation. The first snapshot is the baseline.
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | ai.aislabs/recorder | 2 Oct 2026 | 3 Oct 2026 | 1 |