{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T18:06:09.388Z",
  "record_id": "VXI-EXT-PROCUREMENT-MCP-LEGACY-INITIALIZATION-CAPABILITY-SEQUENCE-01-v1",
  "record_kind": "external_reference",
  "title": "MCP legacy initialization and capability boundaries",
  "system": "Model Context Protocol",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "For MCP 2025-11-25, does successful initialization permit calls to every client-advertised capability?",
  "near_questions": [
    "Does MCP initialization enable all advertised client features?",
    "When may a 2025-11-25 MCP client begin normal operations?",
    "Do all MCP protocol editions use the same initialization handshake?",
    "What evidence establishes negotiated MCP capability support?"
  ],
  "supported_claims": [
    {
      "claim": "MCP 2025-11-25 requires initialize first, negotiation of version and capabilities, and a subsequent initialized notification before normal operation. Successful initialization does not mean every capability advertised by one participant is supported by the other. The reviewed 2026-07-28 protocol instead documents per-request version compatibility without that initialization handshake.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "A change to the existing INDEX MCP contract",
    "Actual consumer compatibility and operation support remain untested.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "MCP 2025-11-25 requires initialize first, negotiation of version and capabilities, and a subsequent initialized notification before normal operation. Successful initialization does not mean every capability advertised by one participant is supported by the other. The reviewed 2026-07-28 protocol instead documents per-request version compatibility without that initialization handshake.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Lifecycle - Model Context Protocol",
    "source_url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-MCP-LEGACY-INITIALIZATION-CAPABILITY-SEQUENCE-01-v1",
    "candidate_record_sha256": "4a85b646ba092640bd3eb4e38199968b5068d5ea7d41c6aca84efcb022924b1d",
    "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": "MCP 2025-11-25 requires initialize first, negotiation of version and capabilities, and a subsequent initialized notification before normal operation. Successful initialization does not mean every capability advertised by one participant is supported by the other. The reviewed 2026-07-28 protocol instead documents per-request version compatibility without that initialization handshake.",
    "required_buyer_context": "Client/server protocol versions; Initialization exchange for the legacy edition; Capability declarations and intended operation. Buyer deployment not inspected.",
    "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.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-24",
    "claim_to_check": "For MCP 2025-11-25, does successful initialization permit calls to every client-advertised capability?",
    "documented_statement": {
      "status": "documented",
      "statement": "MCP 2025-11-25 requires initialize first, negotiation of version and capabilities, and a subsequent initialized notification before normal operation. Successful initialization does not mean every capability advertised by one participant is supported by the other. The reviewed 2026-07-28 protocol instead documents per-request version compatibility without that initialization handshake.",
      "source_ids": [
        "mcp-lifecycle-legacy",
        "mcp-lifecycle"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Apply the lifecycle rules for the negotiated protocol edition and verify the specific capability before use.",
      "source_ids": [
        "mcp-lifecycle-legacy",
        "mcp-lifecycle"
      ]
    },
    "buyer_evidence_required": [
      "Client/server protocol versions",
      "Initialization exchange for the legacy edition",
      "Capability declarations and intended operation"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse capability assumptions from handshake success or from applying another edition’s lifecycle."
    },
    "unknowns": "Actual consumer compatibility and operation support remain untested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual consumer compatibility and operation support remain untested."
    },
    "evidence_sources": [
      {
        "source_id": "mcp-lifecycle-legacy",
        "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle",
        "final_url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle",
        "status": 200,
        "captured_at_utc": "2026-10-24T17:46:54.326Z",
        "sha256": "c78611638a3fd1fac75de8468441b1c400ab9ad930e9108a7f8ab21433d13ed0",
        "bytes": 429668,
        "title": "Lifecycle - Model Context Protocol",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Initialization",
          "Capability Negotiation",
          "Initialized notification"
        ],
        "version_context": "MCP 2025-11-25 pinned lifecycle: legacy initialization handshake."
      },
      {
        "source_id": "mcp-lifecycle",
        "url": "https://modelcontextprotocol.io/specification/2026-07-28/basic/lifecycle",
        "final_url": "https://modelcontextprotocol.io/specification/2026-07-28/basic/versioning",
        "status": 200,
        "captured_at_utc": "2026-10-24T17:45:36.589Z",
        "sha256": "5a769311df93a4348873a0ecec6d816fd04045bd78e0dd04cec6cceee08f15a7",
        "bytes": 362426,
        "title": "Versioning and Compatibility - Model Context Protocol",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Versioning and Compatibility",
          "Per-request protocol version",
          "No initialization handshake"
        ],
        "version_context": "MCP 2026-07-28 pinned edition; per-request version compatibility and subscription-specific notifications must not be applied to legacy editions."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Prevent version-mismatched integration assumptions at handover.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Prevent version-mismatched integration assumptions at handover.",
    "refusal_conditions": [
      "Refuse capability assumptions from handshake success or from applying another edition’s lifecycle."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Prevent version-mismatched integration assumptions at handover.",
    "comparison_role": "supplementary_discovery"
  },
  "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": "single_request",
    "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-legacy-initialization-capability-sequence",
  "machine_readable_record": "/varexis-index/records/mcp-legacy-initialization-capability-sequence.json"
}
