Developer · Remote MCP server
AIS Agent Flight Recorder - dead-man alerts & resume for AI agents
Dead-man switch for AI agents & cron jobs: heartbeat with state capsule, alerts + resume links.
Visit AIS Agent Flight Recorder - dead-man alerts & resume for AI agents's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.aislabs/recorder- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-31
- Updated
- 2026-08-31
- Publisher
- ai.aislabs · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain aislabs.ai · how
- Listed under
- Flights MCP servers
- Website
- aislabs.ai/gateway
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.aislabs.ai/recorder/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- ais-recorder 0.1.0 · protocol 2025-06-18
- Tools discovered
- 5:
register_monitor,heartbeat,fetch_capsule,fleet_status,delete_monitor - Checked on
- 2026-10-05
How to connect AIS Agent Flight Recorder - dead-man alerts & resume for AI agents
AIS Agent Flight Recorder - dead-man alerts & resume for AI agents is a remote MCP server: there is nothing to install. Its endpoint is https://api.aislabs.ai/recorder/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, aislabs.ai, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More from ai.aislabs
| Server | Runs |
|---|---|
| AIS CVE Priorities - daily exploit-ranked patch list for AI agentsDaily CVE priorities ranked by real exploitation (KEV+EPSS) for AI agents; free teaser, paid full. | Remote · HTTPLive check: ✓ handshake |
| AIS Gateway - the campus front desk for AIS MCP buildingsFront desk for the AIS MCP campus: lists our buildings (CVE, Flight Recorder), prices, how to pay. | Remote · HTTPLive check: ✓ handshake |
More developer servers
| Server | Runs |
|---|---|
| Air Blackbox MCPEU AI Act compliance scanner for Python AI agents. 14 tools across 6 articles. | Local · stdio |
| Air PipeBuild, validate, deploy - HTTP APIs, cron jobs, webhooks and MCP tools - from your AI client. | Remote · HTTPLive check: ✓ handshake |
| AIR SDKCollective intelligence for browser automation agents. Site capabilities, selectors, and extraction. | Local · stdio |
| AirtableRead and write access to Airtable database schemas, tables, and records. | Local · stdio |
| AIShield Security ScannerScans MCP servers for tool poisoning, prompt injection and supply chain risks. | Local · stdio |
| AISIX AI GatewaySelf-hosted AI gateway that governs MCP servers, LLM traffic, and A2A agents behind one endpoint. | Local · HTTP |