modelcontextprotocol / modelcontextprotocol/registry
Request: Rename server io.github.amit755/4fetch to com.4fetch/fetch
Open
@pree-dew is already working on this.
Since Apr 23, 2026.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
Summary
I am the publisher of io.github.amit755/4fetch (4fetch MCP – fetch a URL and get clean Markdown; api.4fetch.com). I would like this registry entry to use the domain-based server ID com.4fetch/fetch instead of the current GitHub-based ID io.github.amit755/4fetch.
Reason
- I have set up DNS-based registry authentication for the domain 4fetch.com and want the published server to appear under the domain namespace (
com.4fetch/fetch) rather than my GitHub username. - The remote URL and all other metadata would stay the same; only the server name/ID would change from
io.github.amit755/4fetchtocom.4fetch/fetch.
Request
Please rename the existing server entry:
- Current name:
io.github.amit755/4fetch - Requested name:
com.4fetch/fetch
(If renaming is not supported and the only option is to mark the current entry as deleted so I can publish a new one under com.4fetch/fetch, I'm happy to do that instead – please advise.)
Thank you.
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.
Assessment
This issue has not been assessed yet.