modelcontextprotocol / modelcontextprotocol/registry
Automatically remove server.json entries referencing invalid packages
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
Some discussion here: https://github.com/modelcontextprotocol/registry/discussions/50
In the case where npm, pypi, etc. take down a package (e.g. in the case it is found to be malicious), we don't want to maintain a reference to that package.
Because server.json is meant to be immutable, what we should probably do in this case is delete the version of the server.json altogether.
We'll want to run this kind of check (for broken package references) at least ~daily.
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.
Research direction
Start by reading discussion #50 and tracing how server.json versions are stored and validated; the issue names no implementation files or tests. Done means detecting removed package references, deleting the affected server.json version rather than mutating it, and scheduling the check at least daily.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100