{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T13:45:35.999Z",
  "record_id": "VXI-EXT-PROCUREMENT-MCPB-REGISTRY-HASH-01-v1",
  "record_kind": "external_reference",
  "title": "MCPB: Registry hash metadata still needs client verification",
  "system": "Official MCP Registry",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an MCPB fileSha256 in the Registry prove the downloaded bundle was verified?",
  "near_questions": [
    "Who validates the MCPB bundle hash before installation?",
    "Does the official MCP Registry check fileSha256?",
    "What should happen if a downloaded MCPB digest differs?",
    "Can a published checksum prove this bundle was downloaded intact?",
    "Which artifact does the Registry fileSha256 refer to?",
    "Does a matching MCPB hash certify its permissions?",
    "Where is the client integrity-verification evidence?",
    "Can a downstream registry validate an MCPB artifact itself?",
    "How do we bind the installed bundle to the reviewed version?",
    "Is the bundle URL alone sufficient for integrity review?",
    "Does an MCPB metadata entry establish safe execution?",
    "What separates an expected hash from a verified download?"
  ],
  "supported_claims": [
    {
      "claim": "The MCP Registry package guide requires MCPB metadata to include a fileSha256 value, but states that the Registry does not validate that hash. Clients validate the hash before installation; downstream registries may also validate it. A published hash is therefore a reference to check, not evidence that a particular download was checked or is safe to execute.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration, actual data erasure, effective access or completed business actions",
    "Legal advice, compliance determination, vendor certification or safety assurance",
    "Runtime enforcement, permission to act or expanded licensed-checker coverage"
  ],
  "public_summary": "The MCP Registry package guide requires MCPB metadata to include a fileSha256 value, but states that the Registry does not validate that hash. Clients validate the hash before installation; downstream registries may also validate it. A published hash is therefore a reference to check, not evidence that a particular download was checked or is safe to execute.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "MCP Registry: Supported package types",
    "source_url": "https://modelcontextprotocol.io/registry/package-types",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-MCPB-REGISTRY-HASH-01-v1",
    "candidate_record_sha256": "6fd27eacb22ac6ca157cea033d13241e88a575c6b06edf18c52ef34d42ec9ca5",
    "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 Registry package guide requires MCPB metadata to include a fileSha256 value, but states that the Registry does not validate that hash. Clients validate the hash before installation; downstream registries may also validate it. A published hash is therefore a reference to check, not evidence that a particular download was checked or is safe to execute.",
    "required_buyer_context": "The exact MCPB URL, registry version and declared fileSha256. The downloaded bundle digest and the client verification result. The expected publisher and separately reviewed execution permissions. 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-18",
    "claim_to_check": "Does an MCPB fileSha256 in the Registry prove the downloaded bundle was verified?",
    "documented_statement": {
      "status": "documented",
      "statement": "The MCP Registry package guide requires MCPB metadata to include a fileSha256 value, but states that the Registry does not validate that hash. Clients validate the hash before installation; downstream registries may also validate it. A published hash is therefore a reference to check, not evidence that a particular download was checked or is safe to execute.",
      "source_ids": [
        "mcp-package"
      ]
    },
    "buyer_evidence_required": [
      "The exact MCPB URL, registry version and declared fileSha256.",
      "The downloaded bundle digest and the client verification result.",
      "The expected publisher and separately reviewed execution permissions."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not mark bundle integrity verified from metadata alone or infer safe behavior merely from a matching digest."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "mcp-package",
        "url": "https://modelcontextprotocol.io/registry/package-types",
        "final_url": "https://modelcontextprotocol.io/registry/package-types",
        "title": "MCP Registry: Supported package types",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T13:33:51.472Z",
        "version_context": "Rolling official Registry preview documentation; MCPB fileSha256 verification",
        "sha256": "9f7d5b79e40c308422f1e6025b997f63eac67d41b8994565214a35ad6641c6e2",
        "bytes": 465722,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does an MCPB fileSha256 in the Registry prove the downloaded bundle was verified?"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "An installer operator must bind the reviewed MCPB package metadata to the actual bundle before granting local tool authority.",
      "free": "Complete review, practical questions, sources 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": "The exact MCPB URL, registry version and declared fileSha256. The downloaded bundle digest and the client verification result. The expected publisher and separately reviewed execution permissions."
    },
    "buyer_relevance": "An installer operator must bind the reviewed MCPB package metadata to the actual bundle before granting local tool authority.",
    "refusal_conditions": [
      "Do not mark bundle integrity verified from metadata alone or infer safe behavior merely from a matching digest."
    ]
  },
  "niche": {
    "label": "Agent Authority & Action Evidence",
    "niche_id": "agent-authority-action-evidence",
    "topic_id": "tool-authority-integrity",
    "buyer_intent": "An installer operator must bind the reviewed MCPB package metadata to the actual bundle before granting local tool authority."
  },
  "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#mcpb-registry-hash-client-verification",
  "machine_readable_record": "/varexis-index/records/mcpb-registry-hash-client-verification.json"
}
