published · S-005

Model Context Protocol

Connect hosts and clients to server-provided tools, resources, prompts, and related primitives.

Markdown · JSON · Canonical source

Revision
2026-07-28
Maturity
published
Authority
MCP project / AAIF ecosystem
Structure
JSON-RPC, normative prose, and a TypeScript schema
Roles
host, client, server

MCP is not one boolean capability. Tools, resources, prompts, sampling, elicitation, roots, tasks, transports, and authorization are independent questions with direction-specific roles.

Catalog assertions should pin this revision (or another named revision), identify the exact harness surface, and retain transport, authorization, plan, policy, and runtime conditions as qualifiers. A broad product statement that it “supports MCP” is discovery evidence, not proof of every primitive.

Catalog mapping

Atomic capability rows

Absence here means the feature tree has not yet been published, not that the specification lacks the capability.

Conformance boundary

Proposed tests

Definitions only. No fixture has been executed against a harness.