Request: delete io.github.Norcalnappy/atlasofplantbased-pct (1 version), orphaned after GitHub rename Norcalnappy -> AtlasDigitalDesign, holding the remote URL
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
- 10/100
Línea de trabajo
The orphaned record is stored in the registry backend; an admin must delete it via the management API or database. Confirm the repo 301 redirect and server.json on main as evidence. Done means io.github.Norcalnappy/atlasofplantbased-pct is removed and the remote URL is released for the new namespace.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hi,
My GitHub account was renamed from Norcalnappy to AtlasDigitalDesign on October 23, 2026. The one server I had published, io.github.Norcalnappy/atlasofplantbased-pct (version 1.0.0, published October 14), is now orphaned: GitHub OIDC resolves to io.github.AtlasDigitalDesign, so no credential I hold can deprecate or update the old record.
Republishing under the new namespace with the same remote failed on the remote URL rule:
Publishing io.github.AtlasDigitalDesign/[email protected] to https://registry.modelcontextprotocol.io...
Error: publish failed: server returned status 400: {"title":"Bad Request","status":400,"detail":"Failed to publish server","errors":[{"message":"remote URL https://atlasofplantbased.com/mcp is already used by server io.github.Norcalnappy/atlasofplantbased-pct"}]}
As a bridge, io.github.AtlasDigitalDesign/[email protected] is now published against https://atlasofplantbased.com/mcp/ (trailing slash; the same Pages Function answers there). I would like to move it back to the canonical https://atlasofplantbased.com/mcp once the old record is gone, and stop the orphaned record from being served as latest.
Ask: please mark all versions of io.github.Norcalnappy/atlasofplantbased-pct as deleted so the remote URL reservation is released. There is only the one version.
Evidence the two are the same publisher and server:
- The repository field on the old record, https://github.com/Norcalnappy/atlasofplantbased-mcp, 301-redirects to https://github.com/AtlasDigitalDesign/atlasofplantbased-mcp.
- The repo's
server.jsononmaincarries the new name and was published by the samepublish-mcp.ymlworkflow that published the original (run #1 on October 13, run #3 today). - The remote is a Cloudflare Pages Function on a domain I control, with the server card at https://atlasofplantbased.com/.well-known/mcp/server-card.json. Happy to add a DNS TXT record or anything else that helps.
Same situation as #1662, #1682 and #1688. Thanks for your time.
- Lenguaje dominante
- Go
- Estrellas
- 7.4k
- Forks
- 1k
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 29
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de modelcontextprotocol/registry
-
3 registry records that cannot resolve for any client, and a caution about single-pass dead countsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
modelcontextprotocol/registry#1692 ·
Los mantenedores suelen responder en 1 día
-
IsValidRemoteURL only blocks literal localhost/127.0.0.1 — misses [::1], 127.0.0.0/8, 0.0.0.0, and private/link-local addressesPosiblemente ocupada @amitvijapur la tomó hace 97 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
modelcontextprotocol/registry#1465 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 56/100
modelcontextprotocol/registry#1719 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 28/100
modelcontextprotocol/registry#1715 · 14 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 8/100
modelcontextprotocol/registry#1708 ·
Los mantenedores suelen responder en 1 día
Todos los issues de modelcontextprotocol/registry
Issues similares
-
[flaky test] TestValidatorCommitterDropsEmptyStatusBatch: submits to the mock VC before its stream is registeredPosiblemente ocupada @liran-funaro la tomó hoy. Abiertocoordinator flaky-test race-condition testing
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
hyperledger/fabric-x-committer#876 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
garethgeorge/backrest#1426 ·
Los mantenedores suelen responder en 1 día
-
enhancement nav-pilot
Dificultad 2/5 Medio día Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
valkey-io/valkey-operator#549 · 1 comentario ·
Los mantenedores suelen responder en 3 días
-
kind/features
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
TencentBlueKing/bk-nodemgr#3804 ·
Los mantenedores suelen responder en 1 día