Portable MCP server for agent handoff state and review tracking.
Until 2026-09-25 this record combined several servers published from one repository. The others now have records of their own: mcp-workstate-orchestrator. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-workstate-handoff","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Workstate Handoff MCP Portable MCP server for agent handoff state, review findings, exports, close checks, and lane-scoped worker/orchestrator coordination. ## Scope This package owns handoff state and related workflow primitives: - task state, decisions, blockers, and next actions - review findings and review runs - generated `CURRENT_TASK.json` snapshots - lane registration, lane activity, worker reports, and lane messages - artifact indexing and derived metrics snapshots It does not include unrelated repo-intel or UI helpers. ## Runtime State By default, runtime state lives under the workspace you point the CLI at: - SQLite DB: `.task-state/handoff.db` - exports: `.task-state/exports/` - generated markdown: `CURRENT_TASK.json` Override these with CLI flags or `WORKSTATE_HANDOFF_*` environment variables. Legacy pre-rebrand names are still read for one release. ### Tuning compaction thresholds The compaction advisory (`get_handoff_state(sections="identity").compaction_advisory`) compares observed token and char totals against thresholds. The single source of truth for the canonical defaults is the `compaction:` block of `docs/workstate/contracts/harness-protocol.yaml` (`threshold_tokens`, `threshold_chars`); see that file for the current values and the rationale comment above them. Per-deployment overrides resolve with precedence **env > overlay > contract**, per knob, every call (no module-level cache): 1. **Environment variables**: - `WORKSTATE_HANDOFF_COMPACTION_THRESHOLD_TOKENS=<int>` - `WORKSTATE_HANDOFF_COMPACTION_THRESHOLD_CHARS=<int>` 2. **`.workstate-overlay.json`** at the workspace root, sibling of `surfaces` (`tokens` and `chars` must be non-negative integers; the values below are illustrative overrides, not required values): ```json { "surfaces": {"contracts": {"local_root": "docs/workstate"}}, "compaction": {"thresholds": {"tokens": 90000, "chars": 360000}} } ``` Either knob may be omitted; missin…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.