{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-11T21:09:20.344Z",
  "record_id": "VXI-EXT-TOOL-TRUST-SUPABASE-01-v1",
  "record_kind": "external_reference",
  "title": "Supabase MCP: Database access and developer authority",
  "system": "Supabase MCP",
  "evidence_family": "agent_tool_trust_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "What should an agent check before connecting a database project to Supabase MCP?",
  "near_questions": [
    "Can read-only database tools still disclose sensitive rows?",
    "How should an agent scope a Supabase MCP project?",
    "Does Supabase MCP use developer or end-user permissions?",
    "Can Supabase MCP apply database migrations?",
    "Does project scoping disable Supabase account management tools?",
    "Do SQL confirmations prove a person approved every operation?",
    "Can stored database content inject agent instructions?",
    "What authentication can unattended Supabase MCP use?",
    "Which database logs will reach the connected AI client?",
    "What should be checked before connecting a production database tool?",
    "What is retained in a Supabase trust snapshot?",
    "Does this profile validate our database access controls?"
  ],
  "supported_claims": [
    {
      "claim": "Supabase documents project scoping, read-only mode and feature-group restrictions. Its guidance identifies developer permissions and warns about untrusted database content. Review those controls and the actual data requested before connecting a sensitive project. A confirmation prompt or read-only query does not establish that returned data is suitable for the client or model receiving it.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent tool execution or security testing",
    "Vendor certification, guaranteed safety or no-training assurance"
  ],
  "public_summary": "Supabase documents project scoping, read-only mode and feature-group restrictions. Its guidance identifies developer permissions and warns about untrusted database content. Review those controls and the actual data requested before connecting a sensitive project. A confirmation prompt or read-only query does not establish that returned data is suitable for the client or model receiving it.",
  "related_record_ids": [
    "VXI-EXT-TOOL-TRUST-SENTRY-01-v1",
    "VXI-EXT-TOOL-TRUST-STRIPE-01-v1",
    "VXI-EXT-TOOL-TRUST-CLOUDFLARE-01-v1"
  ],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Supabase MCP scope and security",
    "source_url": "https://supabase.com/docs/guides/ai-tools/mcp",
    "checked_on": "2026-10-11",
    "candidate_record_id": "VXI-EXT-TOOL-TRUST-SUPABASE-01-v1",
    "candidate_record_sha256": "8d884a2d972206cb7558df08311a665e6df9d9ad192fdd4145f3a8a961e3d508",
    "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": "Supabase documents project scoping, read-only mode and feature-group restrictions. Its guidance identifies developer permissions and warns about untrusted database content. Review those controls and the actual data requested before connecting a sensitive project. A confirmation prompt or read-only query does not establish that returned data is suitable for the client or model receiving it.",
    "required_buyer_context": "Supabase-hosted MCP for developer use; project, enabled features and authentication method must be specified. Resolved grants, data sensitivity, effective feature restrictions, client retention and buyer-specific isolation.",
    "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.",
  "trust_profile": {
    "schema": "varexis-agent-tool-trust/1",
    "identity": {
      "tool": "Supabase MCP",
      "variant": "Supabase-hosted MCP for developer use; project, enabled features and authentication method must be specified."
    },
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-11",
    "version_scope": "Dated rolling documentation snapshot; no installed or hosted runtime version independently verified.",
    "plan_scope": "Buyer plan, feature entitlement and effective configuration are not verified.",
    "findings": [
      {
        "field": "operator",
        "label": "Publisher and operator",
        "status": "documented",
        "statement": "Supabase publishes the MCP and hosted connection guidance.",
        "source_ids": [
          "supabase-main",
          "supabase-repo"
        ]
      },
      {
        "field": "purpose",
        "label": "Purpose",
        "status": "documented",
        "statement": "Inspect database projects and perform permitted development operations.",
        "source_ids": [
          "supabase-main",
          "supabase-repo"
        ]
      },
      {
        "field": "reads",
        "label": "Read capability",
        "status": "documented",
        "statement": "Schema, query results and project logs through enabled features.",
        "source_ids": [
          "supabase-main",
          "supabase-repo"
        ]
      },
      {
        "field": "writes",
        "label": "Write capability",
        "status": "documented",
        "statement": "SQL, migrations and deployment tools exist outside applicable restrictions.",
        "source_ids": [
          "supabase-main",
          "supabase-repo"
        ]
      },
      {
        "field": "auth",
        "label": "Authentication",
        "status": "documented",
        "statement": "Hosted OAuth registration is documented; scoped PATs support unattended use. Manual OAuth setup has separately documented scope requirements.",
        "source_ids": [
          "supabase-main",
          "supabase-repo"
        ]
      },
      {
        "field": "permissions",
        "label": "Permission surface",
        "status": "documented",
        "statement": "Project scope disables account management tools; read-only queries and selected feature groups reduce the exposed surface.",
        "source_ids": [
          "supabase-main",
          "supabase-repo"
        ]
      },
      {
        "field": "egress",
        "label": "Data leaving the environment",
        "status": "review_inference",
        "statement": "Query results and logs reach the connected client. A read-only connection can still disclose sensitive rows.",
        "source_ids": [
          "supabase-main",
          "supabase-repo"
        ]
      },
      {
        "field": "failures",
        "label": "Failure modes to consider",
        "status": "review_inference",
        "statement": "Developer authority mistaken for end-user row permissions; instructions in stored content; assuming every SQL operation requires a human confirmation.",
        "source_ids": [
          "supabase-main",
          "supabase-repo"
        ]
      },
      {
        "field": "unknown",
        "label": "Unknowns and applicability",
        "status": "unknown",
        "statement": "Resolved grants, data sensitivity, effective feature restrictions, client retention and buyer-specific isolation.",
        "source_ids": []
      },
      {
        "field": "gate",
        "label": "Suggested refusal or clarification condition",
        "status": "varexis_review_policy",
        "statement": "For a diagnostic-only task, withhold writes and minimize returned data; do not give an end user the developer connector.",
        "source_ids": []
      }
    ],
    "evidence_sources": [
      {
        "source_id": "supabase-main",
        "url": "https://supabase.com/docs/guides/ai-tools/mcp",
        "final_url": "https://supabase.com/docs/guides/ai-tools/mcp",
        "title": "Supabase MCP scope and security",
        "checked_on": "2026-10-11",
        "sha256": "fc19683df448b2af80e33f59d7615450f6725028e8601e3744cad12c7df0a501",
        "bytes": 266235
      },
      {
        "source_id": "supabase-repo",
        "url": "https://github.com/supabase/mcp",
        "final_url": "https://github.com/supabase/mcp",
        "title": "Supabase MCP repository",
        "checked_on": "2026-10-11",
        "sha256": "8ae2129d693e18c479543ceaaeed667f0474a5e2b0da68e9db003313b8d92319",
        "bytes": 381263
      },
      {
        "source_id": "mcp-hints",
        "url": "https://blog.modelcontextprotocol.io/posts/2026-03-16-tool-annotations/",
        "final_url": "https://blog.modelcontextprotocol.io/posts/2026-03-16-tool-annotations/",
        "title": "MCP tool annotations and enforcement boundaries",
        "checked_on": "2026-10-11",
        "sha256": "82888044d831c3bd18f03d87a846ce5d27e028bd67a095edc04ba377fc622163",
        "bytes": 52715
      }
    ],
    "observed_tool_execution": false,
    "policy_basis": "Suggested VAREXIS review gates; apply the buyer's authorized task and policy. These conditions do not execute or enforce controls.",
    "commercial_reliance_boundary": "A source-linked review aid, not a vendor certification, security clearance or deployment assessment. Unknown does not mean false or unsafe.",
    "paid_value": {
      "decision_context": "Preserve project scoping, read-only and data-disclosure questions behind a database-tool review.",
      "free": "Complete profile, 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": "Recheck when permissions, deployment, authentication, source guidance or intended use changes; a purchase does not trigger revalidation.",
      "specific_watch": "Review the effective tool inventory and client data policy before a new integration decision."
    },
    "change_history": [
      {
        "version": 1,
        "date": "2026-10-11",
        "change": "Initial documentation review; no earlier vendor assessment claimed."
      }
    ]
  },
  "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#supabase-mcp-database-access-trust",
  "machine_readable_record": "/varexis-index/records/supabase-mcp-database-access-trust.json"
}