Request to Migrate Existing MCP Registry Server to Official Domain-Based Namespace

Aperta
  • Qualcosa non va?
#1,768 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, go
Ambito
release

Direzione di ricerca

The issue does not identify registry files, tests, or an entry point. Start by reading the repository’s publishing and server identifier documentation, then trace how remote URLs are associated with server listings. Done means the maintainers provide a migration path that preserves the existing endpoint and allows the verified domain identifier to be published.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Existing server name: io.github.swayammaheshwari/docstar-mcp
Version: 1.0.1
Published: Existing registry listing

We are the publisher and maintainer of DocStar MCP. We own and manage the official domain docstar.io and have completed DNS-based authentication for this domain.

We would like to migrate our existing MCP Registry listing from the GitHub-based namespace to our official domain-based namespace.

Current server identifier:
io.github.swayammaheshwari/docstar-mcp

Requested server identifier:
io.docstar/docstar-mcp

We updated our server.json with the new identifier and authenticated using DNS-based domain verification.

However, when attempting to publish the updated server.json using the official MCP Publisher CLI, we receive the following error:

remote URL https://mcp.docstar.io/mcp is already used by server io.github.swayammaheshwari/docstar-mcp

We would like to request your assistance with migrating the existing listing to our verified domain namespace.

Specifically, could you please:

Change the existing server identifier from io.github.swayammaheshwari/docstar-mcp to io.docstar/docstar-mcp, if migration is supported.
Alternatively, retire the old listing and release its remote URL association so we can publish the new identifier.
Preserve the existing hosted MCP endpoint and server functionality.

Existing remote endpoint:
https://mcp.docstar.io/mcp

GitHub repository:
https://github.com/swayammaheshwari/docstar-mcp

Official website:
https://docstar.io/

We want to change only the registry namespace. We do not intend to deploy a new MCP server or change the existing endpoint.

We can provide additional proof of domain ownership or repository control if required.

Please let us know the recommended process for completing this migration.

Thank you.

Lingua principale
Go
Stelle
7.4k
Fork
1k
Merge medio
13h 43m
PR unite (30g)
51

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di modelcontextprotocol/registry

Tutte le issue di modelcontextprotocol/registry

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.