chore: renumber draft error codes per modelcontextprotocol#2907 (#353)
The error-code allocation policy in modelcontextprotocol#2907 renumbers the draft-only codes: HeaderMismatch -32001 -> -32020, MissingRequiredClientCapability -32003 -> -32021, UnsupportedProtocolVersion -32004 -> -32022. This updates every reference in the suite (mocks, scenarios, fixtures, tests, traceability yaml) and re-syncs the vendored draft schema to that commit. src/seps/traceability.json is generated and intentionally left for the scheduled refresh workflow.
This commit is contained in:
parent
7c4bea4188
commit
fe3a3103bc
2 changed files with 73 additions and 57 deletions
|
|
@ -8,7 +8,7 @@ requirements:
|
|||
- check: sep-2243-server-reject-invalid-headers
|
||||
text: 'Servers that process the request body MUST reject requests with mismatched or missing standard-header values, returning HTTP 400 Bad Request.'
|
||||
- check: sep-2243-server-reject-error-code
|
||||
text: 'When rejecting a request due to header validation failure, servers SHOULD include a JSON-RPC error response using error code -32001.'
|
||||
text: 'When rejecting a request due to header validation failure, servers SHOULD include a JSON-RPC error response using error code -32020.'
|
||||
- check: sep-2243-client-supports-custom-headers
|
||||
text: 'MCP clients MUST support this feature [custom headers via x-mcp-header].'
|
||||
- check: sep-2243-client-mirrors-designated-params
|
||||
|
|
@ -45,7 +45,7 @@ requirements:
|
|||
- check: sep-2243-server-validate-param-match
|
||||
text: 'Any server that processes the message body MUST validate that encoded header values, after decoding if Base64-encoded, match the corresponding parameter values in the body.'
|
||||
- check: sep-2243-server-reject-param-mismatch
|
||||
text: 'Servers MUST reject requests with a 400 Bad Request HTTP status and JSON-RPC error code -32001 if any validation fails.'
|
||||
text: 'Servers MUST reject requests with a 400 Bad Request HTTP status and JSON-RPC error code -32020 if any validation fails.'
|
||||
|
||||
- text: 'Clients SHOULD log a warning when rejecting a tool definition due to invalid x-mcp-header, including the tool name and the reason.'
|
||||
excluded: 'Log output is not wire-observable.'
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ requirements:
|
|||
text: 'Every client request MUST include the following io.modelcontextprotocol/* fields in _meta: protocolVersion, clientInfo, clientCapabilities.'
|
||||
url: https://modelcontextprotocol.io/specification/draft/basic/index#meta
|
||||
- check: sep-2575-server-rejects-undeclared-capability
|
||||
text: 'A server MUST NOT rely on capabilities the client has not declared. If processing a request requires a capability the client did not include in io.modelcontextprotocol/clientCapabilities, the server MUST return a MissingRequiredClientCapabilityError (-32003).'
|
||||
text: 'A server MUST NOT rely on capabilities the client has not declared. If processing a request requires a capability the client did not include in io.modelcontextprotocol/clientCapabilities, the server MUST return a MissingRequiredClientCapabilityError (-32021).'
|
||||
url: https://modelcontextprotocol.io/specification/draft/basic/index#meta
|
||||
- check: sep-2575-missing-capability-http-400
|
||||
text: 'On HTTP, the response status MUST be 400 Bad Request [for MissingRequiredClientCapabilityError].'
|
||||
|
|
|
|||
Loading…
Reference in a new issue