220 pages for reported.
Titles and paths first, then pages whose text carries it. Each row opens that page as this site last read it.
SEP-1303: Input Validation Errors as Tool Execution Errors
Model Context Protocol · in the page
seps/1303-input-validation-errors-as-tool-execution-errors
…- Unknown tools - Server errors 2. **Tool Execution Errors**: Reported in tool results with `isError: true`: - API failures - Input validation errors - Business logic errors ``` ## I…
SEP-1686: Tasks
Model Context Protocol · in the page
seps/1686-tasks
…*Task Execution Errors**: Errors in the underlying request execution, reported through task status #### 7.1. Protocol Errors Receivers **MUST** return standard JSON-RPC errors for the following prot…
SEP-1730: SDKs Tiering System
Model Context Protocol · in the page
seps/1730-sdks-tiering-system
…pport stats** | 10 days | 100 days | 5 days | | **Documentation (self reported)** | Good | Minimal | Good | | **Tier (computed from above)** | Tier 2 | Tier 3 | Tier 1 | ## Rationale ### Why Three T…
SEP-2207: OIDC-Flavored Refresh Token Guidance
Model Context Protocol · in the page
seps/2207-oidc-refresh-token-guidance
…nt metadata may not be sufficient**: Since client metadata is self-reported, a malicious actor could register a client claiming `refresh_token` grant support to obtain long-lived tokens. Authori…
SEP-2640: Skills Extension
Model Context Protocol · in the page
seps/2640-skills-extension
…MUST identify servers by a host-assigned label, not the server's self-reported `serverInfo.name`. Any cross-origin read MUST be gated behind explicit per-call user approval naming both servers. * **Na…
SEP-2663: Tasks Extension
Model Context Protocol · in the page
seps/2663-tasks-extension
…*Task Execution Errors**: Errors in the underlying request execution, reported through task status #### Protocol Errors Servers **MUST** return standard JSON-RPC errors for the following protocol er…
Tools
Model Context Protocol · in the page
specification/2024-11-05/server/tools
…* Invalid arguments * Server errors 2. **Tool Execution Errors**: Reported in tool results with `isError: true`: * API failures * Invalid input data * Business logic errors Example proto…
Tools
Model Context Protocol · in the page
specification/2025-03-26/server/tools
…* Invalid arguments * Server errors 2. **Tool Execution Errors**: Reported in tool results with `isError: true`: * API failures * Invalid input data * Business logic errors Example proto…
Schema Reference
Model Context Protocol · in the page
specification/2025-06-18/schema
…successful).</p> <p>Any errors that originate from the tool SHOULD be reported inside the result object, with <code>isError</code> set to true, <em>not</em> as an MCP protocol-level error response…
Tools
Model Context Protocol · in the page
specification/2025-06-18/server/tools
…* Invalid arguments * Server errors 2. **Tool Execution Errors**: Reported in tool results with `isError: true`: * API failures * Invalid input data * Business logic errors Example proto…
Tasks
Model Context Protocol · in the page
specification/2025-11-25/basic/utilities/tasks
…*Task Execution Errors**: Errors in the underlying request execution, reported through task status ### Protocol Errors Receivers **MUST** return standard JSON-RPC errors for the following protocol e…
Tools
Model Context Protocol · in the page
specification/2025-11-25/server/tools
…a#calltoolrequest)) * Server errors 2. **Tool Execution Errors**: Reported in tool results with `isError: true`: * API failures * Input validation errors (e.g., date in wrong format, value o…
Overview
Model Context Protocol · in the page
specification/2026-07-28/basic/index
…tocol/clientInfo` and `io.modelcontextprotocol/serverInfo` > are self-reported by the sender and are not verified by the protocol. They are > intended for display, logging, and debugging. Implementati…
Schema Reference
Model Context Protocol · in the page
specification/2026-07-28/schema
…version</code>; other fields are optional.</p> <p>The value is self-reported by the client and is not verified by the protocol. It is intended for display, logging, and debugging. Servers SHOULD…
Discovery
Model Context Protocol · in the page
specification/2026-07-28/server/discover
…to use this server effectively > [!NOTE] > > `serverInfo` is self-reported by the server and is not verified by the > protocol. It is intended for display, logging, and debugging. Clients **SHOULD…
Tools
Model Context Protocol · in the page
specification/2026-07-28/server/tools
…g format, value out of range) * Business logic errors They are reported in tool results with `isError: true`: ```json theme={null} { "jsonrpc": "2.0", "id": 4, "result": {…
Overview
Model Context Protocol · in the page
specification/draft/basic/index
…tocol/clientInfo` and `io.modelcontextprotocol/serverInfo` > are self-reported by the sender and are not verified by the protocol. They are > intended for display, logging, and debugging. Implementati…
Schema Reference
Model Context Protocol · in the page
specification/draft/schema
…version</code>; other fields are optional.</p> <p>The value is self-reported by the client and is not verified by the protocol. It is intended for display, logging, and debugging. Servers SHOULD…
Discovery
Model Context Protocol · in the page
specification/draft/server/discover
…to use this server effectively > [!NOTE] > > `serverInfo` is self-reported by the server and is not verified by the > protocol. It is intended for display, logging, and debugging. Clients **SHOULD…
Tools
Model Context Protocol · in the page
specification/draft/server/tools
…g format, value out of range) * Business logic errors They are reported in tool results with `isError: true`: ```json theme={null} { "jsonrpc": "2.0", "id": 4, "result": {…