All servers · Monitoring & logs · Travel & booking
AIS Agent Flight Recorder — dead-man alerts & resume for AI agents
ai.aislabs/recorder · v0.1.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 5 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links
Connect
streamable-http · https://api.aislabs.ai/recorder/mcp
claude mcp add --transport http recorder https://api.aislabs.ai/recorder/mcp{
"mcpServers": {
"recorder": {
"url": "https://api.aislabs.ai/recorder/mcp"
}
}
}Tools as reported by the server
register_monitorAgent 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 alertheartbeatAgent 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_capsuleAgent Flight Recorder (Gateway key) — get the last state capsule a monitored agent sent, to resume from where it died.fleet_statusAgent Flight Recorder (Gateway key) — every monitor you own: alive / late / dead, last heartbeat, capsule preview.delete_monitorAgent Flight Recorder — remove a monitor (needs its secret or the owning key).
Website · JSON · Text for agents · Registry updated 2026-08-31