Resource-scan receipts

neondatabase-labs/mcp-server-neon

Canonical URL: https://github.com/neondatabase-labs/mcp-server-neon · Fetched from: https://raw.githubusercontent.com/neondatabase-labs/mcp-server-neon/HEAD/README.md · Machine form: /v1/resource-scans/github-com-neondatabase-labs-mcp-server-neon-f638e23562 · Markdown

Latest receipt: 5 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: a91200d102a25c3ea3e43a181310df4c10163471541b17a13badb1b50a2d5510 · 33795 bytes · scanned 2026-10-27T12:21:22.369Z · scanner resource-scan-v1 · ledger entry 1547.

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: console.neon.tech, cursor.com, github.com, img.shields.io, kiro.dev, mcp.neon.tech, modelcontextprotocol.io, neon.com, nodejs.org, opensource.org, pnpm.io. 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: console.neon.tech; domain: cursor.com; domain: github.com; domain: img.shields.io; domain: kiro.dev; domain: mcp.neon.tech; domain: modelcontextprotocol.io; domain: neon.com; domain: nodejs.org; domain: opensource.org; domain: pnpm.io

• 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); authorization headers and bearer values. 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); authorization headers and bearer values

• 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 — flag

  The scanned bytes contain shell-out or download patterns: shell command tools named in the bytes (curl, wget, powershell). Code that runs shell commands acts with the full permissions of whoever runs it.

  Evidence: shell command tools named in the bytes (curl, wget, powershell)

• 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: neondatabase-labs/mcp-server-neon; bytes scanned: 33795; fetched from: https://raw.githubusercontent.com/neondatabase-labs/mcp-server-neon/HEAD/README.md.

  Evidence: source host: github.com; repository: neondatabase-labs/mcp-server-neon; bytes scanned: 33795; fetched from: https://raw.githubusercontent.com/neondatabase-labs/mcp-server-neon/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 — 5 of 8 checks flagged · SHA-256 a91200d102a25c3e… · 33795 bytes · scanner resource-scan-v1 · ledger entry 1547