{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T12:05:03.000Z",
  "record_id": "VXI-EXT-PROCUREMENT-MCP-STATE-HANDLE-NOT-AUTHENTICATION-CREDENTIAL-01-v1",
  "record_kind": "external_reference",
  "title": "MCP state handles and authentication",
  "system": "Model Context Protocol",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an MCP application state handle or legacy session ID replace authentication?",
  "near_questions": [
    "Is an MCP session identifier an authentication credential?",
    "Should an MCP state handle be bound to the authenticated user?",
    "What changed between legacy MCP session IDs and current application state handles?",
    "Does possession of a resumed MCP state handle authorise the next tool call?"
  ],
  "supported_claims": [
    {
      "claim": "MCP security guidance for revision 2026-07-28 requires verification of inbound requests and prohibits using application state handles for authentication. It recommends unpredictable handles bound to the authenticated principal. The 2025-11-25 guidance applies the same authentication warning to that revision's session IDs. These are version-specific state mechanisms, not bearer authority to act.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Authentication or authorisation from a state identifier or an INDEX protocol upgrade",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "MCP security guidance for revision 2026-07-28 requires verification of inbound requests and prohibits using application state handles for authentication. It recommends unpredictable handles bound to the authenticated principal. The 2025-11-25 guidance applies the same authentication warning to that revision's session IDs. These are version-specific state mechanisms, not bearer authority to act.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Security Best Practices - Model Context Protocol",
    "source_url": "https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-MCP-STATE-HANDLE-NOT-AUTHENTICATION-CREDENTIAL-01-v1",
    "candidate_record_sha256": "5895f17bb03e93db40eb76dbcb01828fa8311bbf75800a74e654190cd17e0325",
    "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 security guidance for revision 2026-07-28 requires verification of inbound requests and prohibits using application state handles for authentication. It recommends unpredictable handles bound to the authenticated principal. The 2025-11-25 guidance applies the same authentication warning to that revision's session IDs. These are version-specific state mechanisms, not bearer authority to act.",
    "required_buyer_context": "Implemented MCP revision and state mechanism; Request authentication and principal-to-state binding; State lifecycle and access checks for the resumed 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": "Can an MCP application state handle or legacy session ID replace authentication?",
    "documented_statement": {
      "status": "documented",
      "statement": "MCP security guidance for revision 2026-07-28 requires verification of inbound requests and prohibits using application state handles for authentication. It recommends unpredictable handles bound to the authenticated principal. The 2025-11-25 guidance applies the same authentication warning to that revision's session IDs. These are version-specific state mechanisms, not bearer authority to act.",
      "source_ids": [
        "mcp-security",
        "mcp-legacy-security"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Verify identity and state ownership separately when resuming an interaction; possession of a handle alone is insufficient.",
      "source_ids": [
        "mcp-security",
        "mcp-legacy-security"
      ]
    },
    "buyer_evidence_required": [
      "Implemented MCP revision and state mechanism",
      "Request authentication and principal-to-state binding",
      "State lifecycle and access checks for the resumed operation"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not accept a resumed action using a state handle or legacy session ID as its only authentication evidence."
    },
    "unknowns": "The deployed version, authentication checks and state isolation were not tested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The deployed version, authentication checks and state isolation were not tested."
    },
    "evidence_sources": [
      {
        "source_id": "mcp-security",
        "url": "https://modelcontextprotocol.io/specification/2026-07-28/basic/security_best_practices",
        "final_url": "https://modelcontextprotocol.io/docs/2026-07-28/tutorials/security/security_best_practices",
        "status": 200,
        "captured_at_utc": "2026-10-24T11:34:51.369Z",
        "sha256": "9b22cd5f333079bfeee18ea2eb3a95caac06c75efb464b79a1c5e476c359d844",
        "bytes": 546307,
        "title": "Security Best Practices - Model Context Protocol",
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "version_context": "MCP revision 2026-07-28",
        "reviewed_sections": [
          "Application state handle hijacking mitigations"
        ],
        "claim_review_completed": true
      },
      {
        "source_id": "mcp-legacy-security",
        "url": "https://modelcontextprotocol.io/docs/2025-11-25/tutorials/security/security_best_practices",
        "final_url": "https://modelcontextprotocol.io/docs/2025-11-25/tutorials/security/security_best_practices",
        "status": 200,
        "captured_at_utc": "2026-10-24T11:37:57.584Z",
        "sha256": "bc95ccd602dced1f3dbdc09011e5260af8b4c082bac13a8c6612de7d5c7a2c60",
        "bytes": 508854,
        "title": "Security Best Practices - Model Context Protocol",
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "version_context": "MCP revision 2025-11-25",
        "reviewed_sections": [
          "Session hijacking mitigations"
        ],
        "claim_review_completed": true
      }
    ],
    "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": "Check identity continuity when an agent resumes stateful work across requests.",
      "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": "Check identity continuity when an agent resumes stateful work across requests.",
    "refusal_conditions": [
      "Do not accept a resumed action using a state handle or legacy session ID as its only authentication evidence."
    ]
  },
  "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": "Check identity continuity when an agent resumes stateful work across requests.",
    "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-state-handle-not-authentication-credential",
  "machine_readable_record": "/varexis-index/records/mcp-state-handle-not-authentication-credential.json"
}
