{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-07T02:45:27.401Z",
  "record_id": "VXI-EXT-MCP-20260728-03-v1",
  "record_kind": "external_reference",
  "title": "MCP July 2026: Extension support boundary",
  "system": "Model Context Protocol",
  "evidence_family": "agent_protocol",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does MCP's extension framework establish support for every optional capability?",
  "near_questions": [
    "Does the MCP extension framework enable every extension automatically?",
    "How should MCP client and server capabilities be compared?",
    "Can two implementations support different MCP extensions?",
    "Does an extension declaration prove correct behaviour?",
    "What authorisation assumptions need review after an MCP update?",
    "Can an agent rely on an unsupported optional capability?",
    "Which extension versions should a receipt identify?",
    "Does a release announcement test my integration?",
    "How are missing optional features handled by a client?",
    "Can extension support alone establish permission enforcement?",
    "What evidence supports an MCP extension compatibility claim?",
    "Does formal extensibility imply universal interoperability?"
  ],
  "supported_claims": [
    {
      "claim": "The MCP July 2026 release introduces a formal extension framework and authorisation changes. An extension mechanism does not establish that a client and server implement the same optional capabilities or enforce them correctly; review their declared versions and behaviour.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "universal optional-feature support",
    "tested extension interoperability",
    "correct authorisation enforcement"
  ],
  "public_summary": "The MCP July 2026 release introduces a formal extension framework and authorisation changes. An extension mechanism does not establish that a client and server implement the same optional capabilities or enforce them correctly; review their declared versions and behaviour.",
  "related_record_ids": [
    "VXI-EXT-AGENT-PROTOCOL-01-v1",
    "VXI-EXT-AGENT-PROTOCOL-02-v1",
    "VXI-EXT-LANGGRAPH-01-v1",
    "VXI-EXT-LANGGRAPH-02-v1",
    "VXI-EXT-MCP-20260728-02-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "MCP July 2026 release",
    "source_url": "https://blog.modelcontextprotocol.io/posts/2026-07-28/",
    "checked_on": "2026-10-07",
    "candidate_record_id": "VXI-EXT-MCP-20260728-03-v1",
    "candidate_record_sha256": "47cbcd6ea192c33fc87c9b5a5b70626c70e74b74c96b01ed1e015d5ed55bb571",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "The MCP July 2026 release introduces a formal extension framework and authorisation changes. An extension mechanism does not establish that a client and server implement the same optional capabilities or enforce them correctly; review their declared versions and behaviour.",
    "required_buyer_context": "The core release, extension identifiers and versions, client and server support and observed authorisation behaviour.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "evidence_receipt",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#mcp-extension-support-boundary",
  "machine_readable_record": "/varexis-index/records/mcp-extension-support-boundary.json"
}
