{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-07T02:45:27.401Z",
  "record_id": "VXI-EXT-MCP-20260728-02-v1",
  "record_kind": "external_reference",
  "title": "MCP July 2026: Core and application state",
  "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 July 2026 stateless core mean an application cannot keep state?",
  "near_questions": [
    "What does the MCP July 2026 stateless core mean?",
    "Can an MCP application still retain state?",
    "Does protocol statelessness imply data is never stored?",
    "Which layer owns application conversation state?",
    "Can an agent infer retention policy from the protocol model?",
    "Does a stateless core establish recovery behaviour?",
    "What application state should an MCP review identify?",
    "Can explicit application state cross tenant boundaries?",
    "Does a protocol release prove deployment migration is complete?",
    "Which MCP release does the state claim refer to?",
    "What remains unknown about application persistence?",
    "What should a state-boundary receipt preserve?"
  ],
  "supported_claims": [
    {
      "claim": "The MCP July 2026 release describes a stateless protocol core. Applications may still maintain their own state explicitly; the protocol model alone does not establish application retention, isolation or recovery behaviour.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "stateless application storage",
    "configured retention policy",
    "tested recovery or isolation"
  ],
  "public_summary": "The MCP July 2026 release describes a stateless protocol core. Applications may still maintain their own state explicitly; the protocol model alone does not establish application retention, isolation or recovery 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-03-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-02-v1",
    "candidate_record_sha256": "c6d0b95de1ace9e292054fd6169331efee0919f65a7483fd6dcc8f04ffe9a4a9",
    "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 describes a stateless protocol core. Applications may still maintain their own state explicitly; the protocol model alone does not establish application retention, isolation or recovery behaviour.",
    "required_buyer_context": "The protocol release, application state model, storage scope, retention policy and recovery 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-stateless-core-application-state",
  "machine_readable_record": "/varexis-index/records/mcp-stateless-core-application-state.json"
}
