publish
Update specific MCP server version (Optional)
Changed onUpdate a specific version of an MCP server in the registry.
Note: This endpoint is optional for registry implementations and is not implemented by the official MCP registry. It is included in the specification to standardize the update mechanism for registry implementations that choose to support it.
Authentication mechanism is registry-specific and may vary between implementations.
put/v0.1/servers/{serverName}/versions/{version}
Request
- The document declares no server URL.
- Auth: HTTP bearer
Path parameters
serverNamestring required
Example:com.example%2Fmy-server
URL-encoded server name (e.g., "com.example%2Fmy-server")
versionstring required
Example:1.0.0
URL-encoded version to update (e.g., "1.0.0" or "1.0.0%2B20130313144700" for versions with build metadata)
Request body
Server Detail required(unresolved $ref)
Response
Successfully updated server version
Changes
- warning
the
//request property's maxLength was set to255
- warning
- info
added the optional property
///to the response with the status
- info