Get a fix plan for your MCP server

The directory and the free playground tell you what is wrong. This is the part where somebody works out what to do about it, in what order, and what each change is worth.

What you get

• A ranked change list. Every finding turned into a concrete edit, ordered by token saving and selection-accuracy impact rather than by rule severity.
• A consolidation proposal. Which tools should merge behind one intent-shaped tool, with the parameter shape written out, and which should simply be removed.
• Rewritten descriptions and schemas for the tools that carry the most selection ambiguity — as a diff you can apply, not as advice.
• A before/after token budget so the saving is a number you can put in a pull request description.

How it works

Send the server: a public endpoint, an npm package, or a tools/list snapshot if the surface is private. Nothing is invoked, and nothing is published without your say-so — private surfaces stay private, and a directory page only ever covers a public server.

Before you pay for anything

Run the audit yourself first — it is free, it takes a minute, and it may be all you need. Paste a tools/list dump into the playground, run npx mcp-surface-lint against your server, or read how the scoring works and fix the obvious things directly.

See what other servers score · Read the rule catalogue