Modelcontextprotocol
GET /v0/servers/{id} endpoint removal
Stopped workingSubscribe to ModelcontextprotocolShare
Calls to GET /v0/servers/{id} on Modelcontextprotocol stopped working on October 17, 2025.
Calls it hits
GET /v0/servers/{id}
What to use instead of these calls
Call GET /v0/servers/{serverName}/versions/latest instead.
In Modelcontextprotocol's words
`GET /v0/servers/{serverName}` - Use `GET /v0/servers/{serverName}/versions/latest` instead
Facts
- API
- Modelcontextprotocol
registry.modelcontextprotocol.io - Kind
- Endpoint removal
- Takes effect
- October 17, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Modelcontextprotocol's own pages
Questions
When does this change take effect?
Calls to GET /v0/servers/{id} on Modelcontextprotocol stopped working on October 17, 2025.
What happens to calls after October 17, 2025?
They have failed since October 17, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Modelcontextprotocol 1
-
GET /v0/servers/{id}/versionsBehaviour change Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.