Publish checks
Validate protocol compliance before distributing your MCP server.
Before you distribute a server, to your users, the MCP registry, or an app directory, the Checklist tab in the Publish section helps you verify it's ready. It works for Manufact-hosted and external (URL-connected) servers.
Checklist
The Checklist tab runs an automated audit of your server for protocol compliance and platform readiness: initialization behavior, tool schemas, error handling, metadata quality, and more. The basic checklist is available on every plan and is billed at $0.10 per run.
- Open your server, go to Publish → Checklist, and click Run checklist.
- Each check reports as passed, a warning, an error, or skipped, with an explanation. The summary card shows your score and counts by status.
While a run is in progress, use Stop to cancel it. Partial results streamed so far are kept.
End-to-end checks (ChatGPT & Claude)
On Hobby and above, the checklist also includes end-to-end checks that exercise your server live in ChatGPT and Claude. These verify tool calls and widget rendering in real clients, not just protocol compliance. E2E checks are billed at $2 per run.
Free plans run the basic checklist only. Upgrade to Hobby to unlock E2E checks.
- Expand a category with issues to read How to fix guidance for each failed check.
- For fixable issues you can copy a fix prompt into your own coding agent, or run the built-in autofix flow (requires a connected GitHub repository). In-flight autofix jobs can be stopped from the dashboard.
Run it again after deploying fixes; runs are kept so you can track progress over time.
Recommended publish flow
- Pass the Checklist with no failures.
- Validate behavior with test suites across clients and models.
- Try it end to end via Public Chat or your own client setup.
- Generate a submission pack and submit to the app directory.