static

The definitions were not properly referenced. There are several definitions but not properly exported to root. Below is corrected option that keeps in line with original merging of several previous vendor standards and allows for easy addition of new client specific schemas. { "$comment": "Corrected root schema. Original schema was invalid because it referenced ServerDetail directly without exporting it as the root. This version wraps the intended root types in a oneOf union, preserving compatibility with all MCP contexts.", "$id": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json", "$schema": "http://json-schema.org/draft-07/schema#", "oneOf": [ { "$ref": "#/definitions/ServerDetail" }, { "$ref": "#/definitions/Package" }, { "$ref": "#/definitions/RemoteTransport" } ], "definitions": { / KEEP ALL ORIGINAL DEFINITIONS EXACTLY AS PUBLISHED / } }

In the description it already mentions that this is an URL Template. The regexp is more restrictive than this. Our actual problem is: MCP Servers might not know their full absolute URL, this is often defined later, e.g. by the Gateway. So for some MCP servers, they can only provide a relative URL or a templated URI. Is this correct or are there reasons why the current regexp insists on an absolute URL? I understand we want absolute URLs at the very end (in the registry), but when you self-describe yourself you might not yet have it.

As part of MCP joining the Linux Foundation, this PR updates licensing to Apache 2.0 for new contributions while grandfathering existing MIT code. See modelcontextprotocol/modelcontextprotocol#1994