Modelcontextprotocol
GET /v0/servers/{id}/versions changes: takes the server name instead of the server ID
Stopped workingSubscribe to ModelcontextprotocolShare
On September 29, 2025, the GET /v0/servers/{id}/versions endpoint changed how it identifies servers. The path parameter was updated so that requests take the server name instead of the server ID. Requests that continue sending the server ID to GET /v0/servers/{server_id}/versions fail after this date.
Calls it hits
GET /v0/servers/{id}/versions
What to use instead of these calls
Pass the URL-encoded server name instead of the server ID in GET /v0/servers/{serverName}/versions requests.
In Modelcontextprotocol's words
`GET /v0/servers/{server_id}/versions` → `GET /v0/servers/{serverName}/versions`
Facts
- API
- Modelcontextprotocol
registry.modelcontextprotocol.io - Kind
- Behaviour change
- Takes effect
- September 29, 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}/versions on Modelcontextprotocol stopped working on September 29, 2025.
What happens to calls after September 29, 2025?
They have failed since September 29, 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}Endpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.