modelcontextprotocol / modelcontextprotocol/registry

Server visible in Official Registry API but not discoverable on github.com/mcp search

Open
#1,107 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
7.3k
Forks
994
Avg merge
4d 12h
Merged PRs (30d)
19

Description

Describe the bug
Our MCP server is published and returned by the Official MCP Registry API, but it does not appear in the GitHub MCP Registry UI search at 'github.com/mcp'.

Server details

Evidence

To reproduce

  1. Open https://github.com/mcp?search=shabaaspay
  2. Observe: no results
  3. Open https://registry.modelcontextprotocol.io/v0.1/servers?search=shabaaspay
  4. Observe: server is returned

Expected behavior
If a server is present and active in the Official MCP Registry, it should be discoverable in 'github.com/mcp' search for relevant terms (e.g. 'shabaaspay' or the server name).

Additional context
We believe this is an indexing/sync issue between the registry backend and the GitHub MCP UI.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the Official MCP Registry API search endpoints with the github.com/mcp search entry point using the supplied server name and terms. Trace where registry results are indexed or synchronized into the GitHub MCP UI; done means the published server appears for relevant searches in both locations.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, go
Domain
search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.