modelcontextprotocol / modelcontextprotocol/registry
My MCP server io.github.meemoprasad/meeba-brain was successfully published to the Official MCP Registry as version 1.0.1 and is returned by the registry API, but it does not appear in GitHub's MCP discovery search for "meeba" or "meeba brain".
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
My MCP server io.github.meemoprasad/meeba-brain was successfully published to the Official MCP Registry as version 1.0.1 and is returned by the registry API, but it does not appear in GitHub's MCP discovery search for "meeba" or "meeba brain". Could you please check whether the GitHub MCP discovery index has synced this server?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the Official MCP Registry API result for io.github.meemoprasad/meeba-brain with GitHub's MCP discovery search results for "meeba" and "meeba brain". Trace the discovery-index synchronization path if it is documented in the repository; done means identifying the sync failure or confirming why the server is not indexed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- backend-api-design, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100