No user-submitted related servers found.
Scored across 11 tools
The three non-report tools (create_constitution, build_constitution_audit, verify_manifest) are clearly distinct, and each build_* report tool names its target framework explicitly. However, eight tools share the identical shape 'build a Markdown compliance report from a receipt set,' so selection depends entirely on the agent knowing which regulatory framework applies—an easy source of misselection.
Every tool is snake_case with a leading verb (build_, create_, verify_) followed by a noun describing the target artifact or standard. The build_* family is uniform, and the two non-build tools still follow verb_noun convention.
Eleven tools sits comfortably in the well-scoped 3–15 range. The count is driven by distinct regulatory frameworks rather than redundant variants, and each report tool targets a genuinely different standard.
Framework reporting coverage is broad (EU AI Act, ISO 42001, NIST, SOC 2, GDPR, HIPAA, ISO 23894, CRA), but the receipt and constitution lifecycle is thin: no tool to list/fetch receipts, retrieve or list constitutions, or verify an individual receipt (only a whole manifest, and only the Ed25519 half of v3 signatures). Agents can work around this if receipts are supplied externally, but the surface has notable dead ends.