Score your MCP server before registry and directory submission.

Check the package metadata, install path, tool safety notes, and release proof that reviewers and users look for before trusting a new MCP server.

Best for

Open-source MCP servers published through npm, GitHub, the official MCP Registry, MCP directories, or coding-agent setup guides.

Package or server name Repo, npm, or package URL Target registry or directory

Package identity Package metadata is complete and points to the real repo. MCP server identity is stable across package, repo, and docs. Registry package mapping or server.json is present and version-aware. Release tag matches the published package version.

Install and client config Published install command works from a clean environment. README has a copyable MCP client config block. Transport, arguments, and environment variables are documented. Package entrypoint and bin/export path are verified.

Tool safety and UX Tool names and descriptions are specific. Tool permissions and side effects are documented. Tool errors are actionable for users and agents. Risky inputs and write operations have guardrails.

Release proof Smoke test proof is visible in docs or release notes. CI checks build, package contents, or server startup. Directory submission assets are ready and consistent. Security and trust notes are clear before install.

0 /100

MCP launch check not started

Mark the checks that are already true. Missing items become the prioritized MCP launch-risk list.

Email result

Priority risks

Fill out the check to generate a prioritized MCP launch-risk list.

This is a self-check, not a registry guarantee. A manual MCP launch check is $99.

Pay $99 launch check View sample report

MCP launch self-check lymantate2@gmail.com Shipcheck MCP launch check Sample report Payments