AIS Agent Flight Recorder — dead-man alerts & resume for AI agents
REMOTE · API.AISLABS.AI
Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 447 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 54% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_monitor" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Sept 26 0
- “register_monitor” reworded the description of “alert_email” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 1 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.aislabs.ai/recorder/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aislabs.ai | CN=WE1,O=Google Trust Services,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1da2f6837197aa5b0e7395772a1cfdf9 |
| SANs: aislabs.ai, api.aislabs.ai, *.api.aislabs.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.aislabs.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| aislabs.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.aislabs.ai/recorder/mcp | Verified | 200 | |
| http (plaintext) | http://api.aislabs.ai/recorder/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
delete_monitor ~39
Agent Flight Recorder — remove a monitor (needs its secret or the owning key).
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | string | yes | – |
| secret | string | – | – |
No output schema declared.
No examples provided.
fetch_capsule ~49
Agent Flight Recorder (Gateway key) — get the last state capsule a monitored agent sent, to resume from where it died.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id | string | yes | – |
| secret | string | – | – |
No output schema declared.
No examples provided.
fleet_status ~33
Agent Flight Recorder (Gateway key) — every monitor you own: alive / late / dead, last heartbeat, capsule preview.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
heartbeat ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| capsule | object | – | Resume state: { step, done: [...], next, ids: {...} } — anything JSON |
| monitor_id | string | yes | – |
| secret | string | – | Monitor secret from register_monitor (not needed when calling with the owning Gateway key) |
| status | string | – | – |
No output schema declared.
No examples provided.
register_monitor ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| name | string | yes | What is being watched, e.g. "nightly ETL loop" |
| period_minutes | number | – | Expected heartbeat interval in minutes (default 10) |
No output schema declared.
No examples provided.
How do I install the AIS Agent Flight Recorder — dead-man alerts & resume for… MCP server?
AIS Agent Flight Recorder — dead-man alerts & resume for… is a hosted endpoint at https://api.aislabs.ai/recorder/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.aislabs.ai
claude mcp add --transport http ai-aislabs-recorder 'https://api.aislabs.ai/recorder/mcp'
What is the AIS Agent Flight Recorder — dead-man alerts & resume for… MCP server?
AIS Agent Flight Recorder — dead-man alerts & resume for… is an MCP server listed in the public MCP registry as ai.aislabs/recorder. Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links. This page covers its hosted endpoint (https://api.aislabs.ai/recorder/mcp).
Is the AIS Agent Flight Recorder — dead-man alerts & resume for… MCP server safe to use?
AIS Agent Flight Recorder — dead-man alerts & resume for… scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AIS Agent Flight Recorder — dead-man alerts & resume for… MCP server expose?
AIS Agent Flight Recorder — dead-man alerts & resume for… exposes 5 tools: register_monitor, heartbeat, fetch_capsule, fleet_status, delete_monitor. Their descriptions and schemas cost roughly 447 tokens of context every time the server is loaded.
Does the AIS Agent Flight Recorder — dead-man alerts & resume for… MCP server require authentication?
No. We connected to AIS Agent Flight Recorder — dead-man alerts & resume for… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AIS Agent Flight Recorder — dead-man alerts & resume for… MCP server still maintained?
AIS Agent Flight Recorder — dead-man alerts & resume for… is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.