Skip to content
{mcpdesc}

Overview

The document’s mcpdesc value remains 0.9.0; its exact schema identity is 0.9.0-rc.3. For validators and projection tools, the bare 0.9.0 selector advances with release candidates until final 0.9.0 is released. Select an exact RC supported by your tool when you need to pin a snapshot. Publishing this specification snapshot does not itself add RC.3 support to downstream packages.

Format version: 0.9.0 | Snapshot: rc.3 | Date: November 7, 2026

These versioned sections, examples, validation rules, and companion guides mirror the immutable RC.3 snapshot. Earlier draft and RC snapshots remain available from the canonical specification repository.

RC.3 extends RC.2’s discriminator-driven validation with union-aware, source-located diagnostics. Disjoint unions with approved selectors use portable guarded conditionals; only the inclusive oauthFlows union retains anyOf. Findings identify the applicable failing rule rather than irrelevant alternatives.

For diagnostic consumers:

  • Missing-member paths identify the enclosing object; detail.member names the absent member.
  • Unexpected-member paths identify the member that exists in the source.
  • Findings reached through $componentRef identify the reference use site and provide a component-definition entry in relatedLocations.
  • Render recognized detail.kind values and their factual fields; fall back to message for unknown kinds or diagnostics without detail.
  • Do not depend on raw diagnostic counts or validation-engine schema paths.

Validation result format advances to 1.4.0. Rule format remains 1.3.0, with 85 rules (46 MCP, 1 JSON Schema, and 38 mcpdesc), updated ownership locations and fixture citations, and an expanded unchecked-requirement inventory.

Read the 0.8.0-to-0.9.0 migration guide, including RC.3 diagnostic migration, for compatibility details. The cumulative candidate also retains protocol-version-scoped validation, Effective Protocol Views, merge and conversion profiles, and the non-semantic document ordering profile. The proposals implemented by this candidate remain under review.

  1. Introduction
  2. Terminology
  3. Document Structure
  4. Versioning
  5. Info Object
  6. Transports
  7. Security
  8. Capabilities
  9. Tools
  10. Resources and Resource Templates
  11. Prompts
  12. Elicitation Declarations
  13. Tags
  14. Specification Extensions
  15. Serialization
  16. Conformance
  17. Reusable Components and Local References
  18. Document-oriented Serialization Ordering

See also the appendix and examples.