N17Q pinned server identity, tool schemas, descriptions, mappings, and the exact offered subset so replay and approval referred to the capabilities a run actually saw.
#mcp
A valid MCP tool request proved that arguments had the expected shape; V0M3 still had to establish identity, authority, resource scope, current state, approval, and recoverable effect semantics.
Porting V0M3’s source and tool boundary to the newly released MCP validated its capability adapters while exposing the identity, schema, permission, content-trust, and recovery work a protocol could not own.
On MCP’s launch, V0M3 treated interoperable discovery and invocation as an adapter opportunity while keeping identity, authorization, content trust, review, and effects under product policy.