A
licenseNot graded
qualityB
maintenanceEnables agents to persist and resume long-horizon tasks using cryptographic event-sourced checkpoints, idempotency deduplication, scheduled heartbeats, pause/resume tokens, and fail-safe recovery.
7
MIT
universal-agent-recovery
by nbhson
Related Servers
Alternatives to universal-agent-recovery
No user-submitted related servers found.
Related Servers
genpark-long-horizonofficial
AlicenseNot gradedqualityBmaintenanceEnables long-horizon autonomous task checkpointing and resumption through cryptographic event-sourced state persistence, idempotency key deduplication, timeout heartbeats, human-in-the-loop pause/resume tokens, and fail-safe recovery.7MIT- AlicenseAqualityBmaintenanceEnables agents to monitor token/usage limits and persist work checkpoints, allowing them to pause, resume, and track progress across sessions.5MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Code and Codex to delegate background Pi Coding Agent tasks, inspect and steer running work, and recover saved checkpoints after server restarts.377 npm16MIT
- AlicenseNot gradedqualityDmaintenanceProvides operational continuity for AI coding agents, preserving task state, decisions, checkpoints, and project context across sessions and model switches via MCP.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to open and update session work, report goals, tasks, blockers, outcomes, and subagent contributions, and resume compact context after interruptions. A local dashboard then visualizes multiple sessions and live updates without requiring additional model calls.MIT
TDQS
A3.5/5.0
Scored across 7 tools
Disambiguation4/5
Each tool maps to a distinct lifecycle action, but report_progress (heartbeat) and save_checkpoint (durable state) are close enough that an agent could misuse one for the other; the descriptions do clarify the difference. register_task vs report_interruption vs mark_completed are clearly separated by intent.
Naming Consistency5/5
All seven tools follow a strict snake_case verb_noun pattern (register_task, report_progress, save_checkpoint, report_interruption, get_task_status, mark_completed, cancel_task). No deviations or mixed conventions.
Tool Count5/5
Seven tools cleanly covers the register→progress→checkpoint→recover→complete/cancel lifecycle without redundancy. Each tool earns its place in the watchdog workflow.
Completeness4/5
Core task lifecycle is fully covered, including recovery and terminal states. Minor gap: no way to enumerate or query multiple tasks (no list_tasks) and no explicit manual recovery trigger, though the watchdog handles recovery automatically.
Maintenance
ActivityMaintained
ResponsivenessNo issues