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

- Registry name: `ai.aislabs/recorder` · version 0.1.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security, Travel & booking, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=ai.aislabs%2Frecorder
- Server page: https://mcpstation.net/s/ai.aislabs--recorder.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://api.aislabs.ai/recorder/mcp`

## Tools (as reported by the server, not verified)

- `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
- `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\).

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html