MCP Server List

Submit to Awesome Remote MCP Servers

A curated list for shared public remote MCP endpoints, with explicit access, authentication, Glama health and contribution requirements.

Open a reviewed shared remote service contribution PR. Eligibility is checked before purchase.

Checked public remote contribution PRSources checked

What to prepare

  • A shared public HTTPS Streamable HTTP endpoint usable by anyone or through public signup; explicitly attest remote_access accurately.
  • A product homepage or documentation URL, exact existing category, and accurate none/API-key/OAuth marker.
  • An existing evaluated matching Glama connector with inspected tools and a recent healthy test.
  • The operator contribution account must meet upstream requirements, including its existing repository star; no endpoint or entry duplicate.

List the endpoint someone can actually use

This list introduces a service operated by its publisher. The endpoint is shared and publicly reachable; users may have to sign up, but a private invitation or unique per-user MCP URL is outside the list’s scope. Installation instructions for a local process belong in the local-server list instead.

State access accurately in your profile. A public landing page is not proof that an MCP endpoint is usable by the advertised audience. The free preflight requires the owner’s explicit public or public-signup attestation alongside actual protocol and connector evidence.

Match the entry to the connector evidence

The entry combines a product or documentation link, the exact MCP endpoint, a Glama connector badge and an authentication marker. The description should explain the tools’ task in one short sentence. Keep the category and alphabetical placement aligned with the current README.

A badge must resolve to the same endpoint and authentication method. MCP Server List checks an evaluated discovered connector with inspected tools and a recent healthy test. An unknown health state or a syntactically valid badge pointing elsewhere cannot pass as readiness.

A contribution still goes through review

The operator account must meet the repository’s contribution prerequisites before the target can be sold. The service prepares a focused change, records the actual PR URL, and follows the review outcome. It does not purchase acceptance or bypass required checks.

A rejected or unresolved PR remains visible in the launch. Only matching accepted content can support the listed state. If the upstream rules change between preflight and execution, the worker stops for attention instead of quietly substituting a different public submission.

Submission workflow

  1. Confirm the remote service belongs in this list rather than the installable local-server list.
  2. Run free preflight to check access, exact endpoint, Glama evaluation and health, auth marker, category, ordering and operator prerequisites.
  3. Review the precise three-line contribution and authorize the checked launch before payment starts the PR job.
  4. Follow the real PR and maintainer decision; verify merged content before reporting a list entry.

Blockers to resolve before review

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

  • A private, invite-only, single-tenant or per-user endpoint is submitted as a public shared service.
  • The endpoint cannot initialize for upstream checks, or the declared authentication marker disagrees with connector evidence.
  • The required Glama connector, description, category, ordering, operator star or duplicate checks fail.

Primary sources

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

← Compare all destinations