mcpField
M
MCP Schema Audit

MCP Schema Audit

Remote
github.com/tylerscomic-labDeveloper Tools0Updated 14w ago
Repository

About MCP Schema Audit

MCP Schema Audit is an MCP server for developers who build MCP tools and marketplace listings. It scores tool definitions and reports concrete fixes for schema patterns that can lead models to choose or fill tools incorrectly.

Key features

  1. 01Score a single tool definition from 0 to 100
  2. 02Batch-audit tools with cross-tool checks
  3. 03Flag vague descriptions and missing parameter docs
  4. 04Check naming, enum size, and schema depth
  5. 05Validate marketplace description limits

Use cases

  1. 01Review a new tool before release
  2. 02Find inconsistent names across a server's tools
  3. 03Catch description limits before marketplace deployment

MCP support

Exposes auditing tools to MCP clients for single definitions, batches, and marketplace descriptions.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp-schema-audit-mcp.mcpize.run/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-schema-audit-mcp

License: MIT Live on MCPize

An MCP server that audits other MCP tool definitions and marketplace listings for the specific patterns that make models call tools wrong, never call them, or mis-fill their parameters — vague descriptions, missing parameter docs, non-verb-first naming, oversized enums, deeply nested schemas — plus MCPize's own 500-character description limit, which fails at deploy time with no warning until you hit it.

Most tool-definition bugs don't throw errors. They just make a model call the wrong tool, or call the right tool with the wrong arguments, silently and intermittently. This scores every tool 0-100 and tells you exactly which line to fix.

Why this exists

Verb-first naming, parameter descriptions, and schema depth aren't cosmetic — they measurably change how reliably a model picks and fills a tool. This project encodes those patterns as an actual auditor instead of a blog post you have to remember to re-read every time you write a new tool.

Tools

audit_tool_definition

Audit a single tool (name, description, inputSchema). Returns a 0-100 friendliness score and a list of concrete issues, each with severity, why it matters, and the fix.

audit_tool_batch

Same checks across an entire server's tool list, plus cross-tool checks: duplicate names, inconsistent naming convention (snake_case vs camelCase mixed in one server), and a worst-offenders summary.

check_marketplace_description

Validates a marketplace-facing short/long description against known platform limits — specifically catches MCPize's 500-character short-description cap before you burn a deploy attempt finding out the hard way.

Use it

Hosted (recommended, no setup): subscribe on MCPize — free tier included, $7/mo for higher limits.

Self-host:

npm install
node server.js

Exposes a Streamable HTTP MCP endpoint on :8080 (/mcp), health check at /health.

Part of a small suite

Built alongside three sibling correctness-audit tools for Claude Code / MCP builders: cron-schedule-audit-mcp (DST-correct cron validation), regex-safety-audit-mcp (ReDoS detection), and claude-cost-audit-mcp (exact Claude API cost + cache-economics calculator).

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.