modelcontextprotocol / modelcontextprotocol/registry

Server published but not appearing in registry (2+ days delay)

Open
#1,395 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Summary

I published io.github.Dusheh/myclaw-toolkit v1.0.8 to the registry via CI/CD (mcp-publisher), which returned success:

After 2+ days, the server still does not appear in:

  • GET /v0.1/servers listing (30 total servers)
  • GET /v0/servers/io.github.Dusheh/myclaw-toolkit (404)

server.json

{
  "name": "io.github.Dusheh/myclaw-toolkit",
  "description": "23-in-1 developer utility toolkit",
  "repository": { "url": "https://github.com/Dusheh/myclaw-toolkit", "source": "github" },
  "version": "1.0.8",
  "packages": [
    { "identifier": "myclaw-toolkit", "registryType": "npm", "version": "1.0.8", "transport": { "type": "stdio" } }
  ]
}

Related

  • Issue #960: same symptoms, later resolved after time

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 CI/CD run linked in the issue with the published server.json, then query GET /v0.1/servers and GET /v0/servers/io.github.Dusheh/myclaw-toolkit. Review issue #960 for the previously reported behavior. Done means determining why the successful publication is not visible and confirming that both registry endpoints return the server.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, go
Domain
api, backend, ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.