This matrix describes OzMcp 0.9.0 against the Model Context Protocol specification, revision 2025-11-25. It is the only revision that the server supports.
Legend: โ implemented ยท ๐ก partially implemented ยท โ not implemented
Checked by
The CI checks the server from the outside on each build:
- The official conformance tool,
@modelcontextprotocol/conformance0.1.16 (serverscenarios). One scenario is expected to fail:server-sse-multiple-streams. It sends the headerMCP-Protocol-Version: 2025-03-26and the server answers400, as the transport specification requires for a version that the server does not support. The list of expected failures is intest/conformance/expected_failures.yml. - The official TypeScript SDK client,
@modelcontextprotocol/sdk1.32.2, over HTTP and stdio (mix test.sdk).
Base protocol
- โ JSON-RPC 2.0 requests, notifications and responses, with a check of the envelope
- โ
Request ids: strings and integers of any size;
null, float, boolean and object ids are refused with-32600 - โ
A request id is unique while its request runs; a duplicate gets
-32600 - โ
Batches refused (
-32600 "batching is not supported"), on HTTP and stdio - โ
Parse errors: text that is not JSON, invalid UTF-8, a lone surrogate, text after the object, a number over 100 characters,
1e400all give-32700 - โ
paramsmust be an object;nullcounts as absent - โ
A method that exists only as a notification is refused as a request (
-32601); an unknown notification is ignored - ๐ก
_meta: the type is checked on a message of the client (an object, a string or integerprogressToken); the key format and the reserved prefixes are checked on what the server declares, not on what the client sends - โ
Standard error codes, plus
-32002(resource not found) and-32042(URL elicitation required) - โ
Every response carries its
id, also when the callback raises or returns a wrong shape (-32603) - โ
Icons,
title,descriptionandwebsiteUrlwhere the specification puts them - โ JSON Schema 2020-12 by default
Lifecycle
See Declare a server and Runtime options.
- โ
initialize: version negotiation (an unknown version gets2025-11-25),clientInfoandcapabilitieschecked,instructions - โ
A second
initializeis refused on both transports - โ
notifications/initialized; a second one is accepted and ignored - โ
Requests before the initialization are refused;
pingis allowed - โ
Initialization timeout,
DELETE - โ
Idle timeout with one rule: a stream, a request, a request to the client or a tracked task holds the session; it expires
session_timeout_msafter the last one ends - โ
Capability gating: a method of a capability that the server does not declare gives
-32601 - โ
pingin both directions - โ
A request of the server role sent by the client gives
-32601 - โ Protocol revisions other than 2025-11-25 (by design)
Transport: stdio
See stdio transport.
- โ Newline-delimited JSON, logs on stderr only
- โ Concurrent requests, drain at the end of stdin, bounded output queue
- โ The same outcome as HTTP for every message, except a malformed answer of the client, which gets no line on stdio
- โ Every request gets one line, also on a crash
- โ An answer of the client gets no line, valid or malformed, with an id or with none
Transport: Streamable HTTP
See HTTP transport.
- โ
POST,GET,DELETE,OPTIONSon one endpoint,405withAllow - โ
AcceptandContent-Typechecks - โ JSON and SSE answers, lazy upgrade to SSE, priming event
- โ
202for notifications and for answers of the client - โ
Mcp-Session-Id: visible ASCII,400when missing,404when unknown or foreign - โ
MCP-Protocol-Version:400for an unsupported value - โ
Origin check (
403), Host allow-list (DNS rebinding protection) - โ Limits: sessions, streams, subscriptions, body, numbers, tokens
- โ
Session limit with reclaim of the oldest idle session;
429only when no session is idle - โ
GETSSE:retry:, heartbeats, poll close, several streams per session - โ
Resumability with
Last-Event-ID - ๐ก The resume of an unknown or ended
POSTstream gets204(on purpose, to stop reconnect loops) - โ
Server-initiated close of a
POSTstream withretry:(SEP-1699); the callback goes on - โ A disconnect is not a cancel, on Bandit and on Cowboy
Authorization (resource server)
See Authorization.
- โ
Protected Resource Metadata (RFC 9728),
WWW-Authenticatewithresource_metadataandscope - โ Bearer token in the header only, strict parsing, size limit, checked before the body is read
- โ Audience check (RFC 8707), fails closed
- โ
Step-up with
insufficient_scope - โ
Pluggable
authenticate/2andauthorize/3, both fail closed - โ
required_scopesper entity, filtered lists - โ
Session bound to
{issuer, subject}; a foreign session gets404 - โ Local revocation, token expiry during a stream
- โ No authorization on stdio, as the specification expects
- โ Authorization server, dynamic client registration (out of scope)
Tools
See Tools.
- โ
tools/listwith pagination; a cursor of a wrong type, an unknown cursor and an empty cursor give-32602 - โ
tools/call; an unknown tool gives-32602; input errors are tool errors (isError: true) - โ
inputSchemacheck with defaults;outputSchemaandstructuredContentchecked - โ
title,annotations,icons,_meta,execution.taskSupport - โ
notifications/tools/list_changed(by design: the list is fixed at boot) - โ All content types, resource links, embedded resources
- โ Tool name format (SEP-986)
Resources
- โ
resources/list,resources/templates/list,resources/read; an unknown URI gives-32002 - โ
resources/subscribe(an unknown resource gives-32002),resources/unsubscribe,notifications/resources/updated - โ
notifications/resources/list_changed(by design: the lists are fixed at boot) - โ URI templates, RFC 6570 levels 1 to 3
- ๐ก RFC 6570 level 4 modifiers: refused at compile time (by design: never implemented)
- โ
Annotations,
size, text and binary contents
Prompts
See Prompts.
- โ
prompts/list,prompts/get - โ
notifications/prompts/list_changed(by design: the list is fixed at boot) - โ
Argument checks: a missing required argument, a value that is not a string and an unknown argument give
-32602 - โ All content types in messages
Utilities
See Completions and Notifications.
- โ
completion/completewith prompt and resource references andcontext.arguments - โ
logging/setLevel(an unknown level gives-32602),notifications/message, level filter, log rate limit per session - โ Pagination with opaque cursors
- โ
Incoming
notifications/cancelledwith a two-step stop; an unknown id is ignored - โ
notifications/progress, increasing values only
Client features (requests of the server)
See Client requests.
- โ
sampling/createMessagewithtools,toolChoice,includeContext - โ
elicitation/createin form mode and in URL mode, withnotifications/elicitation/complete - โ
roots/list,notifications/roots/list_changed - โ Capability check before sending; timeouts per method; cancel on timeout
- โ An answer of the client with a result and an error, a result that is not an object, or a malformed error is refused
- ๐ก A request of the server tied to a client request that has no open stream falls back to the
GETstream (kept on purpose)
Tasks (experimental)
See Tasks.
- โ
taskscapability andtaskSupportgating - โ
Task metadata check:
ttltype and ceiling - โ
tasks/get,tasks/list,tasks/result,tasks/cancel; an unknowntaskIdgives-32602 - โ
A running task holds its session with
tasks_follow_session - โ
A task process that dies with no
untrack_taskfrees its session - โ Owner isolation and scope checks
- โ
notifications/tasks/status,ttl,pollInterval, timestamps,statusMessage - โ
input_requiredwith held requests; related-task_meta - โ Limits per owner
- โ
Server as requestor (option
client_tasks, off by default)
Many nodes (outside the specification)
See Cluster.
- โ
Broadcast across nodes with
OzMcp.PubSub.PG, at most once - โ Sticky routing and failover guide
- โ A request that arrives right after a session crash restores the session from the snapshot
- ๐ก Failover through a snapshot store: the event log and the open requests to the client are lost (documented)
- โ Limits, revocation and the task store across the cluster (out of scope)