Manufact

How good is your MCP?

Get a quality score and concrete improvements for your MCP tools.

Reviews all discovered tools. Your score, tool metadata, and feedback will appear in this public catalog.

MCP leaderboard

826 curated MCP servers, ranked by quality score.

FAQ

How Manufact reviews MCP quality and helps you improve it.

What does the MCP quality score measure?

Manufact adds points from tool documentation (40%), tool definitions (30%), protocol compatibility (20%), and server metadata (10%). Unavailable required sections earn zero points. For servers that provide MCP Apps, Apps contributes 20% and the required sections share the remaining 80% in the same proportions. Servers without Apps are not penalized. The report includes checks and concrete improvements for each section. It does not certify runtime reliability or marketplace approval.

How do I get a score for my MCP server?

Paste your MCP HTTPS URL and select Score my MCP. Your report opens while the review runs, and tool scores and feedback appear as they become available. For OAuth servers, complete the authentication prompt when required. No Manufact account is required. The server's tool metadata, documentation feedback, and score appear in the public catalog.

Does the score cover every tool?

New reviews score every tool returned by the server. Completed tool reviews contribute to the documentation score even if some tools could not be reviewed. Each report shows the number reviewed and the total discovered. Run a new review to retry missing tools.

Does the review execute my tools?

The review connects to your MCP server and checks its protocol, tool definitions, and app resources. It evaluates tool metadata without calling tools or changing your server. Use Manufact Cloud to test live tool behavior.

How do I improve my MCP quality score?

Open a report section to see failed checks and improvements. Tool documentation reviews include feedback on titles, descriptions, inputs, annotations, and output schemas. Preview and copy a fix prompt into your coding agent, verify the suggestions against your implementation, then rerun the review. No edits are applied automatically.

What is an MCP publishing checklist?

An MCP publishing checklist is a pre-submission audit of a live Model Context Protocol server against the protocol, tool, metadata, and MCP Apps rules used by the ChatGPT Apps Store and Claude Cloud Connectors. Manufact's free MCP checklist connects to a public or OAuth HTTPS MCP URL and reports pass, fail, and warning results before reviewers see the server.

How do I validate an MCP server?

You validate an MCP server by pointing an MCP validator at its Streamable HTTP endpoint: complete the handshake, list tools and resources, and check names, JSON Schema, annotations, and MCP Apps UI metadata. Paste the MCP URL into this checklist to run that scan.

How do I publish an MCP app to the ChatGPT Apps Store?

A ChatGPT MCP app is a public MCP endpoint ChatGPT can call as tools, with optional widgets, submitted through the ChatGPT Apps Store. Run an MCP checklist first so the handshake, tool descriptions, behavior annotations, and MCP Apps resources match what ChatGPT review expects. This page is that pre-submit scan.

What are Claude Cloud Connector requirements for MCP?

Claude Cloud Connectors expect a reachable MCP server, a negotiated protocol version, unique tool names within Claude's 64-character limit, human-readable titles, descriptions that fit Claude Code's metadata size limit, and capability declarations that match discovery. The Manufact MCP checklist flags those Claude-specific limits on any public or OAuth MCP URL.

How do I check an OAuth-protected MCP server?

An OAuth MCP server is validated after the MCP OAuth handshake, the same publishing checks as a public URL. If the checklist shows Authenticate, complete that handshake to continue the review. No Manufact account is required.

What is an MCP app?

An MCP app is an MCP server that a host such as ChatGPT or Claude can call as tools, optionally rendering an MCP Apps widget from a ui:// resource. A publishing checklist checks the tool surface and the widget envelope: MIME type, widget description, and whether linked UI resources can be read.

What MCP tool metadata do ChatGPT and Claude require?

ChatGPT and Claude expect each MCP tool to have a unique name, a description, a human-readable title, structurally valid JSON Schema, and boolean behavior annotations for read-only, destructive, and open-world. Hidden or control characters in that metadata fail review. The MCP checklist reports each of those fields.

How do I test MCP Apps widgets before submitting?

MCP Apps widgets should be linked from tools to ui:// resources, return supported HTML MIME types, and include a widget description. The free MCP checklist reads those UI resources without invoking tools, so envelope and metadata issues show up before ChatGPT or Claude review.

How do I know if an MCP server is ready to publish?

An MCP server is closer to publish-ready when it completes the MCP handshake over Streamable HTTP, advertises matching capabilities, and passes the tool, resource, and applicable MCP Apps checks used in ChatGPT and Claude listings. Manufact's MCP Quality Score adds weighted section points on a 0 to 100 scale. Unavailable required sections earn no points; MCP Apps is optional. A score is feedback on these checks, not a guarantee of marketplace approval.

What is the difference between an MCP Inspector and an MCP checklist?

An MCP Inspector is a debugger for calling tools, browsing resources, and watching JSON-RPC. An MCP checklist or MCP validator is a publishing-readiness audit against ChatGPT Apps Store and Claude Connector rules. Use Inspector while you build; use this Manufact checklist to score the same server before you submit.