submissionPublish an authorized versioned registry record
Publish versioned server metadata with a verified namespace. The registry describes packages and remote endpoints; it does not host your application.
Limits and required steps
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- Published metadata and capability descriptions are accurate.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Encrypted source-owner GitHub connection; registry namespace grant.
Checked for eligibility before you pay
Requirements →submissionPublish a public unauthenticated remote release and follow its scan
Publish an eligible public remote MCP endpoint through Smithery’s release API, then verify its scan and current server connection.
Limits and required steps
- Only public unauthenticated Streamable HTTP is supported; stdio/MCPB and authenticated scanning are excluded.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- Public endpoint has no required configuration.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Owner-authorized Smithery publishing credential.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed npm/stdio list contribution PR
Contribute an installable public GitHub server to punkpeye’s curated Markdown list through a reviewed pull request.
Limits and required steps
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- Installation instructions and capabilities describe the actual release.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Contributor access and Glama evaluator.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed shared remote service contribution PR
A curated list for shared public remote MCP endpoints, with explicit access, authentication, Glama health and contribution requirements.
Limits and required steps
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- Public signup/access declaration is accurate; no private or per-user endpoint.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Contributor access and Glama evaluator.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed marketplace entry PR
A client marketplace entry with an explicit install configuration, submitted through the maintained Cline marketplace repository.
Limits and required steps
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- Declared environment names/requirements are complete; never provide secret values.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Verified service GitHub contributor and source-owner authorization
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed marketplace entry PR
Distribute an eligible MCP configuration through Kilo’s reviewed marketplace contribution process.
Limits and required steps
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- Declared environment names/requirements are complete; never provide secret values.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Verified service GitHub contributor and source-owner authorization
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed category entry PR
A categorized community list with reviewed README contributions for installable MCP servers.
Limits and required steps
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Verified service GitHub contributor and source-owner authorization
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed project metadata PR
A ranked community list generated from structured project metadata and public repository metrics.
Limits and required steps
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- Do not invent optional package identities or licenses.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Verified service GitHub contributor and source-owner authorization
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed remote server table row PR
A curated table of official remote MCP servers with their URL, authentication method and maintainer.
Limits and required steps
- Open (unauthenticated) servers are not submitted. Maintainers merge infrequently; a PR receipt is not a listing.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server is officially maintained by its publisher and the endpoint is public and stable.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Verified service GitHub contributor and source-owner authorization
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed catalog PR: one data entry plus the regenerated README, llms.txt and llms-full.txt
A curated, link-checked catalog of MCP servers with a searchable website, README and LLM index files, all generated from one data file.
Limits and required steps
- Maintainers review by hand on Sunday, Wednesday and Friday; a merged PR is verified on main but a PR receipt is never a listing. Remote servers (Streamable HTTP) are accepted; no star count or badge is required.
- mcpHQ maintainers review PRs by hand (Sunday, Wednesday and Friday) and may ask for conflict fixes because counts in the generated files change with every merge; a PR receipt is never a listing. Only servers whose maintainer authorizes the entry are submitted; GitHub topics supply the tags and the primary language is read from the source repository.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- You are the maintainer of the server and it is officially yours.
- The source repository has at least two descriptive GitHub topics (they become the tags).
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork with maintainer edits enabled.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed Servers table row PR
A curated table of MCP servers, clients, SDKs and tools grouped by use case, with language, activity and stars recomputed by the list.
Limits and required steps
- Language, activity and stars are recomputed by the list at merge. The maintainer closes PRs where MCP is a bolt-on; a PR receipt is never a listing.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- MCP is the reason the project exists, not a bolt-on to a larger product, and the description is accurate.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Verified service GitHub contributor and source-owner authorization
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed alphabetical README entry PR
A catalog of AI assistant plugins, skills and MCP servers that feeds the HOL Plugin Registry with trust scores.
Limits and required steps
- The list runs its own required source scan (normalized score of at least 75) before merge; this cannot be verified in advance. A PR receipt is never a listing.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The project README documents tested MCP installation and configuration; the description is accurate.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Verified service GitHub contributor and source-owner authorization
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed Chinese table row PR with your own Chinese description
A large Chinese-language list of MCP servers by scenario, with Chinese introductions and implementation tags.
Limits and required steps
- The maintainer may reword or integrate the row directly and rejects paywall wrappers, aggregators, marketing copy and bare-IP endpoints. Listing is confirmed from the public README, not from the PR.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- Your Chinese description is accurate and you accept that it is submitted verbatim.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Verified service GitHub contributor and source-owner authorization
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed data-only registry entry PR against Raycast’s extensions repository
The Model Context Protocol Registry extension in Raycast’s extension store, where official MCP servers are listed by a data-only pull request.
Limits and required steps
- Raycast maintainers review by hand (quoted up to 15 business days) and may request conflict fixes; a merged PR is verified on main but Store release follows Raycast’s own workflow. API-key servers and servers needing environment variables are not submitted.
- Raycast maintainers review PRs by hand (quoted up to 15 business days) and may ask for conflict fixes; a PR receipt is never a listing. Official servers only, with OAuth or no authentication for remote servers, or an environment-free npm package.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- You are the maker of the server: the entry goes in the official list.
- A declared icon URL and website are recommended.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork with maintainer edits enabled.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed server JSON and generated README line PR
A community directory built from one JSON file per server, with a nightly MCP handshake against every hosted endpoint.
Limits and required steps
- Remote servers only in this route. The list probes the endpoint nightly and shows what it observed; a merged PR is verified on main.
- Remote servers only here (one JSON file plus the generated README line). The list probes the endpoint nightly and shows what it observed; listing is verified only when the entry is on main.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server is yours to submit and the description is accurate and not promotional.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed hosted-server table row PR
A curated, CI-checked table list of MCP servers with explicit rules for hosted servers.
Limits and required steps
- Without the contributor star the PR waits for a maintainer. Remote servers only in this route. A merged PR is verified on main.
- The list merges a PR itself only after its author has starred the repository; the service contributor account must have starred it first (an operator action, never automatic). CI sends an MCP initialize to the endpoint. Descriptions are capped at 80 characters.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server is yours to submit; affiliation is disclosed in the PR.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope that has starred the list repository (operator action; the service never stars).
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed numbered table row PR
A large community list of MCP servers, clients and toolkits in numbered tables, with hosted servers welcome.
Limits and required steps
- Remote servers only in this route. The row number is fixed at preflight; if the table gains a row first, a new preflight is required.
- Remote servers only here. The row number is assigned from the current last row at preflight; a moved table needs a new preflight.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server is yours to submit and the description is accurate and not promotional.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed catalog entry PR
A catalog-driven directory of agent tools whose MCP section lists servers with install commands.
Limits and required steps
- Each PR needs one human approval, so review can take days. Remote servers only in this route; the generated README is never edited.
- Maintainers require one human approval per PR, so review can take days. Remote servers only here; the generated README is never edited.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server is yours to submit and the description is accurate and not promotional.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed OSINT section entry PR (only when you opt in)
A curated list of MCP servers for open-source intelligence (people, domains, companies, public records, threat intelligence), with hosted and local servers.
Limits and required steps
- Only OSINT servers. The maintainer verifies the endpoint or package live and may ask for a pricing emoji; none is asserted. A PR receipt is never a listing.
- OSINT servers only. Not offered unless you set directory_categories for it; shown as not applicable otherwise. No pricing emoji is asserted.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server gathers or enriches intelligence from open sources; you opted in with directory_categories.
- The server is yours to submit and the description is accurate and not promotional.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed official-vendor entry PR (only when you opt in)
A curated list of official MCP servers backed by the vendor of each product, with a short description per entry.
Limits and required steps
- Only official vendor servers. The list rejects projects without community usage; the service only checks the repository is at least two months old. A PR receipt is never a listing.
- Official vendor servers only (or widely used open source). Not offered unless you set directory_categories for it; shown as not applicable otherwise. The list rejects brand-new projects.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server is official (backed by its product or company) or a widely used open source project; you opted in with directory_categories.
- The server is yours to submit and the description is accurate and not promotional.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed DevOps table row PR (only when you opt in)
A curated list of MCP servers for DevOps: source control, infrastructure as code, Kubernetes, CI/CD, cloud, observability and security.
Limits and required steps
- Only DevOps servers with commits in the last 12 months. The larger per-server sections are not supported. A PR receipt is never a listing.
- DevOps servers only. Not offered unless you set directory_categories for it; shown as not applicable otherwise. Needs repository activity in the last 12 months.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server is relevant to DevOps (infrastructure, CI/CD, monitoring, security, cloud or containers); you opted in with directory_categories.
- The server is yours to submit and the description is accurate and not promotional.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed China table row PR (only when you opt in)
A bilingual index of MCP servers for Chinese apps and services, with official remote servers marked.
Limits and required steps
- Only China-market servers. A PR receipt is never a listing.
- China-market servers only. Not offered unless you set directory_categories for it; shown as not applicable otherwise.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server connects to a Chinese app or service; the official marker is used only if you are the first-party vendor; you opted in with directory_categories.
- The server is yours to submit and the description is accurate and not promotional.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork.
Checked for eligibility before you pay
Requirements →submissionOpen a reviewed gateway entry PR (only for gateway products you opt in)
A short list of MCP gateway and proxy products, split into open-source and commercial.
Limits and required steps
- Only gateway products. Open-source entries need 200 stars and 2 contributors; commercial entries need a product website. The maintainer merges selectively. A PR receipt is never a listing.
- Gateway and proxy products only. Not offered unless you set directory_categories to open-source or commercial; shown as not applicable otherwise. The maintainer merges selectively.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The server is a gateway or proxy product and not a crypto or finance entry; you opted in with directory_categories (open-source or commercial).
- The server is yours to submit and the description is accurate and not promotional.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Dedicated service GitHub account (mcpserverlister) with public_repo scope; the PR comes from its personal fork.
Checked for eligibility before you pay
Requirements →submissionRegister the domain in Prowl’s free API-readiness directory and follow its public lookup
An agent-readiness directory of web services and APIs (not MCP-only) that benchmarks and scores each entry for AI agents.
Limits and required steps
- Prowl is an API-readiness directory, not MCP-only. The registration write was not exercised live (read-only research only); the agent-key header on /v1/register is documented for agents but unconfirmed.
- Prowl is an API-readiness directory, not an MCP-only list. Registration is free and instant, but entries are scored by Prowl (unclaimed domains are capped at 75) and unauthenticated registrations stay pending review; listing is confirmed only when the public by-domain lookup shows an active record. Claiming the domain (DNS TXT or well-known file, from your own Prowl account) is optional.
- Implemented code has no verified live-provider pilot evidence. Configuration and preflight are required; final provider acceptance remains external.
Owner steps
- The name and description are accurate; Prowl scores the service itself and the score is capped until the domain is claimed.
- Connect the required owner accounts and authorize the exact checked payload and price.
Service configuration
- Service-owned Prowl agent key (PROWL_API_KEY).
Checked for eligibility before you pay
Requirements →