No user-submitted related servers found.
Scored across 8 tools
Each tool maps to a distinct lifecycle action (dispatch/create, poll/claim, fulfill, fail, release, extend, inspect, verify) with explicit 'do NOT use X, use Y' guidance that pre-empts confusion between close pairs like inspect_mesh_state vs verify_contract and extend_ttl vs release_contract. Boundaries are unusually crisp.
All eight names follow a consistent snake_case verb-first pattern (dispatch_contract, poll_next_task, fulfill_contract, fail_contract, release_contract, extend_ttl, inspect_mesh_state, verify_contract). Noun phrases vary slightly in length but the convention is uniform and predictable.
Eight tools cleanly cover one coherent domain (a cross-host contract queue). Every tool earns its place in the lifecycle — no redundant wrappers and no filler.
The lifecycle is nearly fully covered: create, claim, heartbeat, release, fail, deliver, plus read-only state and file-consistency inspection. The notable gap is a requester-side cancel/revoke for a SUBMITTED contract (the only remedy is waiting for queue TTL), which is a minor but real dead end.