Resource-scan receipts

supabase/mcp

Canonical URL: https://github.com/supabase/mcp · Fetched from: https://raw.githubusercontent.com/supabase/mcp/HEAD/README.md · Machine form: /v1/resource-scans/github-com-supabase-mcp-d6af4d2d99 · Markdown

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: b546179b15f8d2170ecbb0c91eb5e3ed9be04ba604d36eb82205c4676d9c13a3 · 8965 bytes · scanned 2026-10-27T12:21:12.515Z · scanner resource-scan-v1 · ledger entry 1542.

Analysis is static only: the bytes were read as text and were never executed, installed or run. Nothing was fetched from behind a login.

Checks (latest receipt)

• Outbound network references — flag

  The scanned bytes reference outbound network activity to these domains: ai-sdk.dev, github.com, img.shields.io, mcp.supabase.com, modelcontextprotocol.io, registry.modelcontextprotocol.io, supabase.com. Any resource that reaches the network can send data out as well as bring data in; the findings name what the bytes reference, and the reader decides whether that fits the resource's stated purpose.

  Evidence: domain: ai-sdk.dev; domain: github.com; domain: img.shields.io; domain: mcp.supabase.com; domain: modelcontextprotocol.io; domain: registry.modelcontextprotocol.io; domain: supabase.com

• Credential and environment access — pass

  No credential or environment access patterns were found in the scanned bytes.

• Install and postinstall hooks — pass

  No install or postinstall hooks were found in the scanned bytes.

• Obfuscation and encoded payloads — pass

  No obfuscation or encoded-payload signs were found in the scanned bytes.

• Shell-outs and download-and-execute — pass

  No shell-out or download-and-execute patterns were found in the scanned bytes.

• Permission declarations vs behavior — flag

  The bytes show network behavior, and no permissions declaration was found in the scanned bytes to compare it against.

  Evidence: behavior: network

• Known-bad indicators — pass

  None of the scanner's published known-bad indicator patterns matched the scanned bytes.

• Provenance facts (weak signals) — pass

  Provenance facts, labeled weak signals — they say where the bytes sit, not what the bytes do: source host: github.com; repository: supabase/mcp; bytes scanned: 8965; fetched from: https://raw.githubusercontent.com/supabase/mcp/HEAD/README.md.

  Evidence: source host: github.com; repository: supabase/mcp; bytes scanned: 8965; fetched from: https://raw.githubusercontent.com/supabase/mcp/HEAD/README.md

History

Every receipt for this artifact so far names the same SHA-256: the bytes have not changed between scans.

• 2026-10-27 — 2 of 8 checks flagged · SHA-256 b546179b15f8d217… · 8965 bytes · scanner resource-scan-v1 · ledger entry 1542