What to prepare
- A public GitHub repository whose README documents tested MCP installation and configuration.
- One concise sentence; the service writes it as “MCP server: …” as the list requires.
- A choice of Development & Workflow or Tools & Integrations, and no existing entry for the repository.
Alphabetical, MCP-prefixed entry
The service inserts one bullet in alphabetical order within the section you choose and starts the description with “MCP server: ”. Scanning, trust scores and merging remain with the maintainer.
Submission workflow
- Read the current contribution guide and sections.
- Inspect the exact bullet and its alphabetical position in free preflight.
- Authorize the checked contribution and follow the independently verified PR.
- Track the list’s required source scan, maintainer review and the merged entry separately.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- A failed or unavailable centralized source scan (normalized score below 75).
- A duplicate, dead link, unmaintained project or a description that does not start with “MCP server: ”.
Primary sources
Checked 2026-11-04. Follow the destination’s current instructions if its requirements change.