Home / MCP registry index / com.mcpscores/agent-continuity
MCPFax Agent Continuity
com.mcpscores/agent-continuity in the official MCP registry.
Endpoint https://mcpfax-continuity.bowling-anthony.workers.dev/mcp.
The registry describes it as: Resume the work, not the conversation. A checkpoint by one model is resumable by another.
We read its 33 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
register whoami claim complete lease lease_renew lease_release resume_packet checkpoint_put checkpoint_get watermark_set watermark_get seen_add seen_check retry_state send inbox_schedule inbox_poll inbox_ack inbox_nack heartbeat budget_record budget_check barrier_create barrier_signal barrier_status work_push work_take work_done work_fail work_status job_cancel should_continue
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-mcpscores-agent-continuity)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.