No user-submitted related servers found.
Scored across 18 tools
Each tool targets a distinct lifecycle step (create, verify, revoke, log, token, attestation, proof, contest), and the lengthy descriptions explicitly cross-reference siblings to prevent misselection. A few pairs could still be confused at a glance: verify_mandate vs check_action_token vs issue_mandate_attestation, and prepare_mandate_signature vs prepare_mandate_pdf, which differ only by output artifact.
Every name is snake_case verb_noun (create_mandate, revoke_mandate, issue_action_token, prepare_contest_signature, list_action_contests, report_issue), with the resource always named explicitly. The prepare_* family and the get_/list_ read tools follow a single, predictable convention throughout.
18 tools is at the upper edge but each maps to a real capability (mandate lifecycle, three prepare-for-signature helpers, token issue/check, attestation, dossier export, contest reminder, issue reporting). The count is justified by the domain's depth, though the prepare_* triples and separate PDF helper add surface an agent must learn.
The surface covers the full lifecycle: create, verify, revoke, action logging, token issuance/verification, offline attestation, proof packs, contests, and key registration, with immutable mandates by design. Gaps are minor: there is no tool to list or search mandates by principal/agent, and no direct read of a single mandate short of generating a full proof pack or dossier.