Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#1,768 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, go
Área
release

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
7.4k
Forks
1k
Merge medio
14 h 16 min
PR fusionados (30 d)
49

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modelcontextprotocol/registry

Todos los issues de modelcontextprotocol/registry

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.