No user-submitted related servers found.
Scored across 75 tools
The tool set has a clear spec-prefix convention (e.g., clinical_ai_validate, tutor_card_inspect), so many tools are distinguishable. However, 75 tools repeat the same validate/inspect/fetch/check actions across a dozen similar document schemas, so an agent can easily select the wrong spec's validator or inspector without careful reading.
Names are overwhelmingly snake_case with a consistent subject-prefix + action pattern (ai_evidence_validate, tutor_card_coppa_check, audit_chain_verify). Minor deviations exist, such as aeo_get_claim using 'get' instead of fetch/inspect, audit_events_query using a plural subject, and defensetech_* tools adding an extra domain prefix, but the overall convention is readable and stable.
At 75 tools, this server is far beyond the 3-15 range appropriate for a single MCP server, and exceeds the 50+ threshold for extreme mismatch. The functionality spans many independent specs and services that would be better split into separate servers.
The surface covers validation, inspection, fetching, hashing, and compliance checks for many Suite specs, but coverage is uneven: AEO lacks a validate tool, several specs lack fetch tools, and signing/hashing support is inconsistent (e.g., claims_card_sign exists but no equivalent sign tool for most other cards). There are also no update/delete operations, though immutability may justify that for attestation documents.
