mcp-spec-compliance-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_server_jsonB | Full conformity audit of an MCP server.json. Args: server_json: The contents of an MCP server.json file. spec_version: Target spec revision. Defaults to latest. Returns: {pass, score_0_100, errors, warnings, recommendations, spec_version} |
| check_required_fieldsB | Fast gate: only check required fields. Args: server_json: server.json contents. spec_version: target spec version. Returns: {pass, missing} |
| check_naming_conventionsB | Lint the slug, version, and tool names. Args: server_json: server.json contents. tool_names: Optional list of tool names to validate against snake_case convention. Returns: {pass, issues} |
| list_spec_versionsA | Return the supported MCP spec revisions + which fields are required for each. |
| generate_passing_templateB | Generate a minimal-but-passing server.json template. Args: org: GitHub org slug. slug: Package slug (must end in -mcp by convention). Returns: {template} |
| sign_conformity_reportA | HMAC-sign a conformity report so authors can publish it as evidence. Args: audit_result: Output of audit_server_json(). Returns: {signed, signature, sealed_at, cert_id} |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
audit_server_json substantially overlaps with check_required_fields and check_naming_conventions, since the former is effectively a superset of the two fast gates. However, descriptions clearly frame the latter as lightweight gates, so an agent can reasonably choose between them.
Every tool follows a consistent snake_case verb_noun pattern (audit_server_json, check_required_fields, list_spec_versions, generate_passing_template, sign_conformity_report). No deviations in style or casing.
Six tools is well-scoped for a compliance/linting server, covering audit, fast checks, version lookup, template generation, and signing. Each tool earns its place without redundancy.
The surface covers the full audit-to-evidence lifecycle (check, audit, template, sign) and is largely self-contained. Minor gaps exist, such as no explicit schema-field-level validator or fix/repair operation, but agents can work around these.