AIS Agent Flight Recorder

A dead-man switch for AI agents and cron jobs.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only

What it can do

  • 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 moni
  • 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 th
  • Fetch Capsule: Agent Flight Recorder (Gateway key) — get the last state capsule a monitored agent sent, to resume from where it died.

What data it sees

Do you need an account

No: the server works without sign-in

A dead-man switch for AI agents and cron jobs. Your agent calls heartbeat on a schedule (optionally with a JSON state capsule); if it goes silent past its grace period, your Discord/webhook/email gets the alert with the last capsule and a resume link — so you (or a fresh agent) can continue from the step it died on.

register_monitor + heartbeat are free (1 monitor per alert target, alerts only). A Gateway key (scope recorder or a campus pass — https://aislabs.ai/gateway) unlocks 20 monitors, stored capsules, fetch_capsule, and fleet_status. HTTP twins at https://api.aislabs.ai/v1/recorder (one-line curl heartbeats for cron).

Part of the AIS campus: the front desk server aislabs/ais-gateway lists every building.

How to connect

How to connect AIS Agent Flight Recorder to Claude

The server address to paste into Claude settings:

https://ais-recorder--aislabs.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect AIS Agent Flight Recorder to ChatGPT

The server address to paste into ChatGPT settings:

https://ais-recorder--aislabs.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect AIS Agent Flight Recorder to Cursor

The server address to paste into Cursor settings:

https://ais-recorder--aislabs.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (5)

Raw names from tools/list. Only developers need these.

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 alert target (Discord/HTTPS webhook and/or email) is notified with the last state capsule and a resume link.
heartbeatAgent 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).