Resource-scan receipts

motherduckdb/mcp-server-motherduck

Canonical URL: https://github.com/motherduckdb/mcp-server-motherduck · Fetched from: https://raw.githubusercontent.com/motherduckdb/mcp-server-motherduck/HEAD/README.md · Machine form: /v1/resource-scans/github-com-motherduckdb-mcp-server-motherduck-5472bbd225 · Markdown

Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 0dddca489475ff00d1ee498f1754b2cdf7fdf97b6c66b6e608690b2f5d9d5393 · 13075 bytes · scanned 2026-10-27T12:23:03.438Z · scanner resource-scan-v1 · ledger entry 1593.

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: cursor.com, docs.aws.amazon.com, duckdb.org, github.com, img.shields.io, insiders.vscode.dev, kiro.dev, motherduck.com, www.youtube.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: cursor.com; domain: docs.aws.amazon.com; domain: duckdb.org; domain: github.com; domain: img.shields.io; domain: insiders.vscode.dev; domain: kiro.dev; domain: motherduck.com; domain: www.youtube.com

• Credential and environment access — flag

  The scanned bytes contain credential or environment access patterns: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names). The receipt names the pattern kinds only; no credential value is reproduced here.

  Evidence: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names)

• Install and postinstall hooks — pass

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

• Obfuscation and encoded payloads — flag

  The scanned bytes carry obfuscation or encoding signs: 1 long base64-shaped run (120+ characters). Encoded content cannot be read from the bytes alone, so what it does cannot be checked from the bytes alone either.

  Evidence: 1 long base64-shaped run (120+ characters)

• 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, credentials behavior, and no permissions declaration was found in the scanned bytes to compare it against.

  Evidence: behavior: network; behavior: credentials

• 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: motherduckdb/mcp-server-motherduck; bytes scanned: 13075; fetched from: https://raw.githubusercontent.com/motherduckdb/mcp-server-motherduck/HEAD/README.md.

  Evidence: source host: github.com; repository: motherduckdb/mcp-server-motherduck; bytes scanned: 13075; fetched from: https://raw.githubusercontent.com/motherduckdb/mcp-server-motherduck/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 — 4 of 8 checks flagged · SHA-256 0dddca489475ff00… · 13075 bytes · scanner resource-scan-v1 · ledger entry 1593