Registry

The MCP Tool Shop Registry is the canonical metadata catalog for tools in the ecosystem. It provides verified names, descriptions, install contracts, and capability tags for each listed tool.

What "Registry listed" means

When a tool shows the Registry badge, it means:

  • The tool has been reviewed and added to registry.json
  • Its name, description, and tags have been curated
  • It has a stable install contract (how to get the tool)
  • Clients like mcpt can discover and install it automatically

Org-only repos

Tools showing Org-only exist in the mcp-tool-shop-org organization but haven't been formally listed in the registry yet. They may be experimental, in-progress, or simply awaiting review.

How to add a tool

  1. Push your repo to mcp-tool-shop-org
  2. Open a PR to the mcp-tool-registry adding your tool to registry.json
  3. Include: id, name, description, repo URL, install object, and tags
  4. Once merged, the tool appears on this site after the next sync

Registry health

8 Registry tools
8 Active projects
70 Org-only repos
0 Archived/missing

Active aliases (2)

Temporary workarounds for registry ID / repo name mismatches. These are band-aids — fix the upstream registry.json to retire them. Goal: zero aliases.

  • claim-ledger → ClaimLedger case-mismatch or rename
  • creator-ledger → CreatorLedger case-mismatch or rename

Data sources

Each tool page combines data from three sources, in merge order:

  1. Registry — canonical names, descriptions, tags, install contracts
  2. GitHub API — live signals (stars, language, last updated)
  3. Overrides — editorial polish (taglines, good-for/not-for, screenshots)

This means registry data is the foundation, GitHub keeps it fresh, and human editors add the finishing touches.