MCP Schema Audit

io.github.tylerscomic-labPublished by GitHub account tylerscomic-labv1.0.0Updated Oct 25, 2026

Audits MCP tool definitions for patterns that make models call tools wrong or mis-fill args.

The publisher's own server: audit.domains - Domain Valuation

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Audits MCP tool definitions and marketplace descriptions, scoring each tool 0-100 and pointing to the exact lines that make models call tools wrong.

What you can do
Audit a single tool definition (name, description, inputSchema) for a 0-100 friendliness score and concrete issues with severity and fixes. Audit a whole server's tool list with cross-tool checks for duplicate names, mixed naming conventions and a worst-offenders summary. Validate marketplace-facing short and long descriptions against platform limits, including a 500-character short-description cap.
When to use it
Useful when building or reviewing MCP servers and tool schemas, to catch vague descriptions, missing parameter docs, non-verb-first naming, oversized enums or deep nesting before shipping. Also handy for checking marketplace listing text against length limits before a deploy attempt.
Requirements
A remote Streamable HTTP endpoint with OAuth authentication required. The README mentions a hosted MCPize subscription (free tier, paid tier for higher limits) or self-hosting via npm install and node server.js on port 8080.
Before you install
OAuth sign-in is required to connect. The hosted option involves a paid subscription for higher limits. The audit tools only read the definitions you supply, but the definitions are sent to the remote service.

Installation

In SourceWeft

  1. Open MCP Schema Audit in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.tylerscomic-lab%2Fmcp-schema-audit-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "schema-audit": {
      "type": "http",
      "url": "https://mcp-schema-audit-mcp.mcpize.run/mcp"
    }
  }
}

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:

bash
npm installnode 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

Source: README.md at commit e83dfd0

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Audit integrations