Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Agent Flight Recorder — remove a monitor (needs its secret or the owning key).
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Agent Flight Recorder — remove a monitor (needs its secret or the owning key).
| Argument | Type | Description |
|---|---|---|
| secret | string | |
| monitor_id* | string |
{
"type": "object",
"required": [
"monitor_id"
],
"properties": {
"secret": {
"type": "string"
},
"monitor_id": {
"type": "string"
}
},
"additionalProperties": false
}Agent Flight Recorder (Gateway key) — get the last state capsule a monitored agent sent, to resume from where it died.
| Argument | Type | Description |
|---|---|---|
| secret | string | |
| monitor_id* | string |
{
"type": "object",
"required": [
"monitor_id"
],
"properties": {
"secret": {
"type": "string"
},
"monitor_id": {
"type": "string"
}
},
"additionalProperties": false
}Agent Flight Recorder (Gateway key) — every monitor you own: alive / late / dead, last heartbeat, capsule preview.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| secret | string | Monitor secret from register_monitor (not needed when calling with the owning Gateway key) |
| status | string | |
| capsule | object | Resume state: { step, done: [...], next, ids: {...} } — anything JSON |
| monitor_id* | string |
{
"type": "object",
"required": [
"monitor_id"
],
"properties": {
"secret": {
"type": "string",
"description": "Monitor secret from register_monitor (not needed when calling with the owning Gateway key)"
},
"status": {
"enum": [
"ok",
"fail"
],
"type": "string"
},
"capsule": {
"type": "object",
"description": "Resume state: { step, done: [...], next, ids: {...} } — anything JSON"
},
"monitor_id": {
"type": "string"
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| name* | string | What is being watched, e.g. "nightly ETL loop" |
| alert_email | string | Email address to alert (Gateway key tier only; capped at 10 emails/monitor/day) |
| alert_webhook | string | Discord webhook URL or any HTTPS webhook (receives JSON) |
| grace_minutes | number | How late a heartbeat may be before alerting (default 5) |
| period_minutes | number | Expected heartbeat interval in minutes (default 10) |
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "What is being watched, e.g. \"nightly ETL loop\""
},
"alert_email": {
"type": "string",
"description": "Email address to alert (Gateway key tier only; capped at 10 emails/monitor/day)"
},
"alert_webhook": {
"type": "string",
"description": "Discord webhook URL or any HTTPS webhook (receives JSON)"
},
"grace_minutes": {
"type": "number",
"description": "How late a heartbeat may be before alerting (default 5)"
},
"period_minutes": {
"type": "number",
"description": "Expected heartbeat interval in minutes (default 10)"
}
},
"additionalProperties": false
}