ServerDetail
objectSchema 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
ServerResponse
objectAPI 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
UuidFieldFilter
objectFilter using one of the following operators: eq, oeq, neq
The field exactly matches the provided value.
Example:?filter[field_name_here][eq]=foo
The field matches any of the provided values.
Example:?filter[field_name_here][oeq]=foo,bar
The field does not match the provided value.
Example:?filter[field_name_here][neq]=bar
StringFieldFilter
One OfThe field exactly matches the provided value.
Example:?filter[field_name_here][eq]=foo
The field contains the provided value.
Example:?filter[field_name_here][contains]=foo
The field contains any of the provided values.
Example:?filter[field_name_here][ocontains]=foo,bar
The field matches any of the provided values.
Example:?filter[field_name_here][oeq]=foo,bar
The field does not match the provided value.
Example:?filter[field_name_here][neq]=bar
SortQuery
stringThe asc suffix is optional as the default sort order is ascending.
The desc suffix is used to specify a descending order.
Multiple sort attributes may be provided via a comma separated list.
JSONPath notation may be used to specify a sub-attribute (eg: ‘foo.bar desc’).