Status 2026-09-12
What is left, the earlier body kept below for context:
SEP-2127: publish the /.well-known/ai-catalog.json catalog entry, or record that the deployment rather than the binary owns it, and confirm the extension's merge status against the card shipped in PR 692. SEP-2792: still a watch; once it merges, decide the translated set (titles, elicitation prompts, progress messages) and how the Spanish site terminology is reused.
Two upstream proposals this server deliberately waits for, moved out of the 2.8.0 conformance issue (#511) so that issue can close with its four batches. Nothing here is implemented before the proposal merges; each entry states its trigger.
SEP-2127, server card successor
Our card at /.well-known/mcp/server-card.json is SEP-1649-shaped and SEP-1649 is dead. SEP-2127 lives at GET <url>/server-card via /.well-known/ai-catalog.json and rejects .well-known/mcp paths; its v1 has no capabilities or primitives.
Trigger: SEP-2127 merges into the specification. Then: publish a conformant card plus the catalog entry, and keep the vendor card, documented as vendor, until SEP-2127 v2 covers primitives, because it has a real consumer.
SEP-2792, per-request user language
_meta io.modelcontextprotocol/acceptLanguage per request with a contentLanguage reply; SHOULD-translate covers titles, elicitation and progress only, descriptions stay English.
Trigger: SEP-2792 merges. Then: decide what is translated (titles, elicitation prompts, progress messages) and how the Spanish site's terminology is reused.
How to watch
Both live in https://github.com/modelcontextprotocol/modelcontextprotocol (search the SEP number). Check on every specification revision bump this repository makes, and whenever the go-sdk release notes mention either.
Status 2026-09-12
What is left, the earlier body kept below for context:
SEP-2127: publish the /.well-known/ai-catalog.json catalog entry, or record that the deployment rather than the binary owns it, and confirm the extension's merge status against the card shipped in PR 692. SEP-2792: still a watch; once it merges, decide the translated set (titles, elicitation prompts, progress messages) and how the Spanish site terminology is reused.
Two upstream proposals this server deliberately waits for, moved out of the 2.8.0 conformance issue (#511) so that issue can close with its four batches. Nothing here is implemented before the proposal merges; each entry states its trigger.
SEP-2127, server card successor
Our card at
/.well-known/mcp/server-card.jsonis SEP-1649-shaped and SEP-1649 is dead. SEP-2127 lives atGET <url>/server-cardvia/.well-known/ai-catalog.jsonand rejects.well-known/mcppaths; its v1 has no capabilities or primitives.Trigger: SEP-2127 merges into the specification. Then: publish a conformant card plus the catalog entry, and keep the vendor card, documented as vendor, until SEP-2127 v2 covers primitives, because it has a real consumer.
SEP-2792, per-request user language
_metaio.modelcontextprotocol/acceptLanguageper request with acontentLanguagereply; SHOULD-translate covers titles, elicitation and progress only, descriptions stay English.Trigger: SEP-2792 merges. Then: decide what is translated (titles, elicitation prompts, progress messages) and how the Spanish site's terminology is reused.
How to watch
Both live in https://github.com/modelcontextprotocol/modelcontextprotocol (search the SEP number). Check on every specification revision bump this repository makes, and whenever the go-sdk release notes mention either.