modelcontextprotocol / modelcontextprotocol/registry
Support `ETag` and `If-Match` in creation endpoints
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
Is your feature request related to a problem? Please describe.
The behavior of POST /v0/publish is unclear in the case of two conflicting posts updating in slightly different ways the same MCP server.
Describe the solution you'd like
It would be great to support ETag and If-Match headers when getting and updating MCP servers, respectively, allowing the server to detect conflicting changes.
Describe alternatives you've considered
None
Additional context
Usually a hash of the original resource is used to populate the ETag header, which introduces the question of how to calculate hashes consistently, which I'm not describing to leave the discussion open.
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 with the POST /v0/publish endpoint and the MCP server GET and update endpoints described in the issue. Determine how ETag values should be calculated consistently and how If-Match should detect conflicting changes; done means concurrent updates are rejected when the original resource has changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100