MCP server checklist
Last reviewed October 23, 2026
Run through this before you post the link anywhere. Each item is something people check, or something that bites later, and each points back to the step that explains it.
Can people find it?
- It is in the official MCP Registry, under your namespace (publish).
- The README has an install snippet for each client people use, VS Code's own form included (publish).
- The repository's name and description say what it connects to, in the words someone would search for.
This site lists only skills, plugins, plugin marketplaces and MCP servers, and decides from the repository itself. An MCP server has no manifest file of its own, so it shows up here when one of these is true:
- it is in the official MCP Registry;
- its root has a
smithery.yamlor aglama.json; - it has the GitHub topic
mcp-serverormcp-servers. The broadermodel-context-protocolcounts only when the README also has an install command, because clients and SDKs use that topic too; - its name says MCP (
linear-mcp), or its description says "MCP server" or "Model Context Protocol".
A name or description that calls the repository a demo, an example, an SDK, a framework or an awesome list cancels the last of those, since most such repositories are something else. If your server started from a template, make it yours before you publish it.
Will people trust it?
- The README lists every tool, what each can read or change, and which credentials the server needs and why (secure).
- Tools that change things are separate from tools that read, and say so in their descriptions (secure).
- The README says which tools return outside content, such as web pages or emails, that reaches the model (secure).
- Ownership checks out: the registry entry is under your namespace, and an npm package carries provenance (publish).
- Nothing in the README or tool descriptions reads as an attempt to steer the agent, and no key appears anywhere in the repository. This site's safety scan looks for both.
Can you keep it working?
- It runs on the current SDK and answers both protocol versions (build).
- CI runs the Inspector's
tools/listcheck in both protocol eras on every change (test). - One CI job publishes the package and the registry entry together, with the same version (publish).
- A
CHANGELOG.mdsays when a tool's name or inputs change. Agents and the people who configured them depend on both, and a silent rename breaks them in ways that are hard to trace.
Building something else? See the guides to a skill and a plugin or marketplace.