MCP.Market

MCP Schema Audit MCP server

not responding
by tylerscomic-lab·io.github.tylerscomic-lab/mcp-schema-audit-mcp·v1.0.0
No reviews yet

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

F32/100grade F
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
F32/100

full report

Adoption
New

0 stars

Blocked at the gateway.Blocked at the gateway. A critical finding or a dead endpoint.

Reviews

Write one

Nobody has reviewed MCP Schema Audit yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

MCP Schema Audit tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote unreachable: HTTP 5000/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityno auth information5/15
  • Maintenancelast push 95 days ago8/15
  • Maintainer identityregistry namespace matches repository owner6/10

Findings (1)

  • highRemote endpoint did not respondreliability.unreachable

    HTTP 500

Overall 32/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How MCP Schema Audit compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
32/100
higher than 6% of 48,255 servers
Uptime
18%
of our recent checks; the typical remote server answers 100%
Response time
1,840 ms
faster than 5% of 30,031 servers

Install MCP Schema Audit in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp-schema-audit-mcp https://mcp-schema-audit-mcp.mcpize.run/mcp
Add to Cursor

What the publisher says

From the MCP Schema Audit repository's README, as published. We do not edit it. Read it on GitHub

mcp-schema-audit-mcp

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

audittooldefinition

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.

audittoolbatch

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.

checkmarketplacedescription

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

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-28revokeA → Fscore 32: Remote endpoint did not respond

MCP Schema Audit: common questions

Is MCP Schema Audit MCP server safe?
No: it is graded F and blocked at the gateway (32/100). Read the MCP Schema Audit safety report
How do I install MCP Schema Audit?
It runs remotely at mcp-schema-audit-mcp.mcpize.run. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does MCP Schema Audit need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is MCP Schema Audit maintained?
The last commit was 102 days ago (2026-07-25). The latest release is v1.0.0.
Is MCP Schema Audit up?
18% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of MCP Schema Audit?
Servers from other publishers that do the same job: QVeris MCP server.
How does MCP Schema Audit compare with other MCP servers?
safety score 32/100 (higher than 6% of 48,255 servers); uptime 18% (of our recent checks; the typical remote server answers 100%); response time 1,840 ms (faster than 5% of 30,031 servers). Full comparison.

Alternatives to MCP Schema Audit

Same job from other publishers: the closest match first, then the best rated.

  • QVeris
    Professional data and tools for AI: find services, review scope, call them, and audit usage.
    A

More from tylerscomic-lab →