No user-submitted related servers found.
Scored across 5 tools
check_draft, list_claims, check_policy_only and about each target a clearly different need, and the descriptions explicitly delimit what each does and does not decide. The one soft spot is check_draft vs check_draft_json, which perform the identical check and differ only in output format, plus check_policy_only which is a partial subset of check_draft; both overlaps are well-explained, so confusion is unlikely but not impossible.
Four of five names follow a verb_noun snake_case pattern (check_draft, check_draft_json, list_claims, check_policy_only) with a readable _json suffix convention. The lone outlier is 'about', a bare noun, which is a minor deviation rather than a convention clash.
Five tools is well-scoped for a claim-verification server: a human-readable check, a machine-gated variant, a pre-pass claim lister, an evidence-free policy check, and a trust/scope note. Nothing feels padded, and no essential verb is crowded out by the count.
The core lifecycle (list claims, check against evidence, check against policy, gate on structured output, read scope) is fully covered for a read-only verification domain. Minor gaps remain: no rewrite/suggestion tool to fix flagged claims, no tool to build or validate an evidence set or policy (init-policy is CLI-only), and no batch/multi-draft entry point, but agents can work around these.