Tag
Registry tools
4 reviewed tools: 3 free or open source, 1 hosted with a real free tier.
Order: free and open source first, then hosted products with a real free tier, then paid-led; catalog order inside each group, with quiet or archived repos last. Not a score, and no tool pays for its place.
4 tools
- MCP RegistryCanonical protocol-org community MCP server registry
Free / OSS · Apache-2.0 · 7.4k GitHub stars
VerdictCanonical community MCP registry when you want protocol-org discovery; treat the license transition and preview API as real compliance and product risk.
CatchVs Smithery: this is the protocol-org community registry, not a hosted freemium marketplace/CLI product. LICENSE is mid MIT→Apache-2.0 transition (Apache body + MIT-holdout preamble); GitHub SPDX often shows NOASSERTION — redistribution diligence required during the mixed-license era. Still in preview / API-freeze posture; pin expectations before building a business on the API shape.
- ObservalApache self-host registry for coding-agent extensions + insight
Free / OSS · Apache-2.0 · 4.5k GitHub stars
VerdictApache self-host agent-extension registry when internal catalog + insight matter — not skills.sh installer alone and not a single skills library.
Catch★3979 in about 27 weeks (~147 a week): judge it on the registry substance, not the star count. Vs skillbox / mcp-gateway-registry-class catalogs / vercel-skills: Skillbox is a skills library; skills.sh is an installer ecosystem — Observal’s catch is self-hosted registry + insight for internal agent extensions as system of record. Self-host ops and what “extension” means in your org still need a mapping; pin CLI/GHCR versions.
- ToolHiveApache-2.0 MCP server runner + gateway — each server in its own container
Free / OSS · Apache-2.0 · 2.3k GitHub stars
VerdictApache-2.0 container-isolated MCP runner when you want every server sandboxed and auditable — bring Docker/Podman and an IdP for real policy.
CatchEvery MCP server runs in its own container, so you need Docker or Podman even on a laptop. Identity and access policies only apply once you connect an OIDC/OAuth provider — out of the box it is isolation, not authorization. Stacklok sells an enterprise tier on top. Vs metamcp (aggregator/proxy that merges servers into one endpoint) and contextforge (gateway/federation): ToolHive’s lane is per-server container isolation plus a registry.
- SmitheryFreemium MCP registry, gateway, and hosting marketplace
Free tier · Freemium · 843 GitHub stars
VerdictFreemium MCP registry/host. Discover fast; treat hosted builds as trust boundary.
CatchVs FastMCP (build servers) and mcp-inspector (debug): Smithery is distribution/hosting, not an SDK. Hosted registry is proprietary SaaS — supply-chain risk is real (past hosting incidents in the ecosystem). Prefer BYO HTTPS publish if you distrust hosted builds. Free discovery ≠ free infinite hosting.
FAQ
- What is the top free pick among Registry tools?
- MCP Registry leads the Stack Gems list for Registry tools. Verdict: Canonical community MCP registry when you want protocol-org discovery; treat the license transition and preview API as real compliance and product risk.
- How many Registry tools does Stack Gems review?
- 4: 3 free or open source, 1 hosted with a real free tier. Each review has a verdict and an honest Catch; no tool pays for its spot.
- Which Registry tools can I self-host for free?
- MCP Registry, Observal and ToolHive.
- Which Registry tools have the most GitHub stars?
- MCP Registry (7.4k), Observal (4.5k), ToolHive (2.3k), per GitHub on 2026-10-19. Stars measure attention, not fit; read the Catch.
- What is the catch with MCP Registry?
- Vs Smithery: this is the protocol-org community registry, not a hosted freemium marketplace/CLI product.