mcp_servers
Operations for discovering, retrieving, and publishing MCP servers
List MCP servers (v0.1)
Returns a list of all registered MCP servers within the selected registry
Query Parameters
Pagination cursor for retrieving next set of results.
Cursors are opaque strings returned in the metadata.nextCursor field of paginated responses. Always use the exact cursor value returned by the API.
Maximum number of items to return
Search servers by name (substring match)
Example:filesystem
Filter servers updated since timestamp (RFC3339 datetime)
Example:2025-08-07T13:15:04.280Z
Filter by version (‘latest’ for latest version, or an exact version like ‘1.2.3’)
Example:1.2.3
Path Parameters
Registry name or UUID
Example:my-registry
Response
application/json
Response
A list of MCP servers
ServerList
API response format with separated server data and registry metadata
Show Child Parameters
Show Child Parameters
Authentication
Path Parameters
Query Parameters
List all versions of an MCP server (v0.1)
Returns all available versions for a specific MCP server within the selected registry, ordered by publication date (newest first)
Path Parameters
URL-encoded server name (e.g., “com.example%2Fmy-server”)
Example:com.example%2Fmy-server
Registry name or UUID
Example:my-registry
Response
application/json
Response
A list of all versions for the server
ServerList
API response format with separated server data and registry metadata
Show Child Parameters
Show Child Parameters
Authentication
Path Parameters
Get specific MCP server version (v0.1)
Returns detailed information about a specific version of an MCP server within the selected registry. Use the special version latest to get the latest version.
Path Parameters
URL-encoded server name (e.g., “com.example%2Fmy-server”)
Example:com.example%2Fmy-server
URL-encoded version to retrieve (e.g., “1.0.0” or “1.0.0%2B20130313144700” for versions with build metadata)
Example:1.0.0
Registry name or UUID
Example:my-registry
Response
application/json
Response
Detailed server information
ServerResponse
API response format with separated server data and registry metadata
Schema for a static representation of an MCP server. Used in various contexts related to discovery, installation, and configuration.
Show Child Parameters
Registry-managed metadata
Show Child Parameters
Authentication
Path Parameters
Update specific MCP server version
Update a specific version of an MCP server in the registry within the selected 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.
Path Parameters
URL-encoded server name (e.g., “com.example%2Fmy-server”)
Example:com.example%2Fmy-server
URL-encoded version to update (e.g., “1.0.0” or “1.0.0%2B20130313144700” for versions with build metadata)
Example:1.0.0
Registry name or UUID
Example:my-registry
Body
application/json
Body
ServerDetail
Schema for a static representation of an MCP server. Used in various contexts related to discovery, installation, and configuration.
Server name in reverse-DNS format. Must contain exactly one forward slash separating namespace from server name.
Match pattern:^[a-zA-Z0-9.-]+/[a-zA-Z0-9._-]+$
>= 3 characters<= 200 characters
Example:io.github.user/weather
Clear human-readable explanation of server functionality. Should focus on capabilities, not implementation details.
>= 1 characters<= 100 characters
Example:MCP server providing weather data and forecasts via OpenWeatherMap API
Optional human-readable title or display name for the MCP server. MCP subregistries or clients MAY choose to use this for display purposes.
>= 1 characters<= 100 characters
Example:Weather API
Optional repository metadata for the MCP server source code. Recommended for transparency and security inspection.
Show Child Parameters
Version string for this server. SHOULD follow semantic versioning (e.g., ‘1.0.2’, ‘2.1.0-alpha’). Equivalent of Implementation.version in MCP specification. Non-semantic versions are allowed but may not sort predictably. Version ranges are rejected (e.g., ‘^1.2.3’, ‘~1.2.3’, ‘>=1.2.3’, ‘1.x’, ‘1.*’).
<= 255 characters
Example:1.0.2
Optional URL to the server’s homepage, documentation, or project website. This provides a central link for users to learn more about the server. Particularly useful when the server has custom installation instructions or setup requirements.
Example:https://modelcontextprotocol.io/examples
An optionally-sized icon that can be displayed in a user interface.
Show Child Parameters
JSON Schema URI for this server.json format
Example:https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json
Show Child Parameters
Any OfTransport protocol configuration for remote context - extends StreamableHttpTransport or SseTransport with variables
Show Child Parameters
Extension metadata using reverse DNS namespacing for vendor-specific data
Show Child Parameters
Response
application/json
Response
Successfully updated server version
ServerResponse
API response format with separated server data and registry metadata
Schema for a static representation of an MCP server. Used in various contexts related to discovery, installation, and configuration.
Show Child Parameters
Registry-managed metadata