MCP Server List

MCP.Directory listing requirements

A repository submission form with metadata ingestion and review, plus discovery from the official registry.

Prefilled — you submit: copy our checked values into the free form yourself; not part of the paid direct submissions. This action is separate from the qualifying submission minimum.

Guarded browser submission without paymentSources checked

What to prepare

  • A public GitHub repository URL and accurate optional public fields.
  • An enabled dedicated browser connection and the current no-payment form.
  • Complete duplicate search and exact source-link evidence checks.

A guarded form and an independent public record

The current form takes a repository and optional package, description and email details. MCP Server List checks that the flow contains no billing fields or paid placement choice, records matching request/acceptance evidence, and verifies a public detail page linking to the exact source. Provider timing remains outside our control.

Submission workflow

  1. Check existing discovery for the exact source repository.
  2. Review the public form payload and no-payment route.
  3. Authorize the launch; the isolated browser submits only those fields.
  4. Retain confirmed acceptance and verify a matching public detail page.

Blockers to resolve before review

Use these as preparation checks. The destination makes its own acceptance decision.

  • Unusable repository metadata.
  • An existing listing that needs a claim or correction instead of a new submission.

Primary sources

Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.

← Compare all destinations