modelcontextprotocol / modelcontextprotocol/registry
Support `ETag` in listing 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 current API spec does not suggest (or mandate) ways for the server to suggest when updates are available. Note that this is different from returning deltas based on timestamps.
Describe the solution you'd like
Responses of GET /v0/servers SHOULD contain an ETag header that the Client SHOULD use on subsequent requests. The Client can still specify a updated_since query parameter, the two are complementary.
The same reasoning could be applied to /v0/servers/{serverName}/versions endpoint.
Describe alternatives you've considered
None, but ETag was suggested in many MCP SEPs and seemed not too controversial to suggest it here as well.
Additional context
None
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 the API specification and the implementations of GET /v0/servers and GET /v0/servers/{serverName}/versions. Define how responses expose ETag values and how clients use them alongside updated_since; done means both listing endpoints document and support the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100