Found during 2026-08-14 portability audit of packages/mcp-server and packages/cli.
The gap: normative discovery is only GET /v1/streams (+ per-stream). What an agent actually needs to query well — valid fields, filter operators, sort/count support, extension capabilities, connection identities — is only available from the non-normative /v1/schema. Result: the MCP server's mandated discovery entry point depends on an implementation-internal route, and no conformant third-party deployment can serve agents equally well.
Precedent: OIDC solves this with a discovery document; LSP with capability negotiation. A protocol designed for agent access needs machine-readable queryability metadata in its normative surface.
Proposed path (deliberate, not rushed): draft as an extension profile first (spec-ext-discovery), gather implementation experience, then promote to Core per the multiple-independent-implementations bar. Should be a consultation agenda item.
Related: #147 (normative contract split).
Assisted-by: AI
Found during 2026-08-14 portability audit of packages/mcp-server and packages/cli.
The gap: normative discovery is only
GET /v1/streams(+ per-stream). What an agent actually needs to query well — valid fields, filter operators, sort/count support, extension capabilities, connection identities — is only available from the non-normative/v1/schema. Result: the MCP server's mandated discovery entry point depends on an implementation-internal route, and no conformant third-party deployment can serve agents equally well.Precedent: OIDC solves this with a discovery document; LSP with capability negotiation. A protocol designed for agent access needs machine-readable queryability metadata in its normative surface.
Proposed path (deliberate, not rushed): draft as an extension profile first (
spec-ext-discovery), gather implementation experience, then promote to Core per the multiple-independent-implementations bar. Should be a consultation agenda item.Related: #147 (normative contract split).
Assisted-by: AI