MCP Server List

MCPBundles listing requirements

An open MCP server directory where any signed-in account can publish a remote MCP URL; the maintainer can then claim the listing.

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.

Owner-submitted website publish (no publish API)Sources checked

What to prepare

  • A public HTTPS remote MCP URL that answers tools/list; local and private addresses are rejected.
  • A name and short description; a logo, website and contact email are optional.
  • An MCPBundles account and the ownership check: a work email on the server domain, or a 6-digit code emailed to a contact in /.well-known/mcpbundles.json or security.txt.

Publish, then optionally claim

Publishing creates the listing; claiming proves you control the server and lets you edit it. An unclaimed listing stays visible. The claim file contains only your contact email and is optional.

Submission workflow

  1. Sign in, paste the URL into the analyze box and run it.
  2. Continue to publish and fill the prepared name and description.
  3. Pass the ownership check; the listing goes live at /skills/<slug>.
  4. Optional (about 2 minutes): publish the prepared /.well-known/mcpbundles.json, open the listing, click Claim this listing and enter the emailed code to edit it later.

Blockers to resolve before review

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

  • A URL that is not public HTTPS or does not answer tools/list.
  • A duplicate: a listing for the same URL already exists and should be claimed instead.

Primary sources

Checked 2026-11-04. Follow the destination’s current instructions if its requirements change.

← Compare all destinations