No user-submitted related servers found.
Scored across 18 tools
The tools map to distinct lifecycle stages: intents, claims, changesets, verification, acceptance, commit recording, coordination, and conflict handling. Read tools are explicitly differentiated as get-by-id, query/filter, or status overview, and conflict-related operations are separated into check, assess, coordinate, resolve, and discard.
Almost all tools use a predictable snake_case verb_noun pattern, such as publish_intent, claim_work, run_verification, and record_commit. The main deviation is status, which is a bare noun, though the naming remains readable overall.
The 18 tools sit slightly above the typical 3-15 range, but the server implements a multi-step coordination protocol where each tool corresponds to a distinct gate or action. It is somewhat heavy, but not obviously padded.
The coordination lifecycle is largely covered: registration, intent publication, claims, changeset publication, verification, acceptance, commit recording, conflict resolution, and discard are all present. The notable gap is that coordinate_with_agent sends messages but no MCP tool reads them, forcing recipients to use the CLI and leaving the message loop only partly closed over MCP.