# Resource-scan receipt: neondatabase-labs/mcp-server-neon

A resource-scan receipt is the record of one static check run over one public AI resource — a repository, a gist, a skill file, a script, an MCP server package or a config — at the public URL named on the receipt. The receipt binds to the exact bytes scanned, named by their SHA-256 hash, and is sealed into the public ledger like every other record here. Each receipt carries the published check list with the outcome of every check and the findings in plain language. The analysis is static only: the bytes are read as text and are never executed, installed or run, and nothing is fetched from behind a login. A receipt publishes evidence, never a judgment: the summary line counts how many of the checks flagged, and the reader draws their own conclusion from the findings. Re-scanning the same URL creates a new receipt; the artifact page shows the latest receipt and the history, and when the bytes at a URL change the new receipt is a new version — no receipt is ever edited or overwritten.

Artifact: 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
SHA-256 of the exact bytes scanned: a91200d102a25c3ea3e43a181310df4c10163471541b17a13badb1b50a2d5510
Bytes scanned: 33795 · Scanned: 2026-10-27T12:21:22.369Z · Scanner: resource-scan-v1
Summary: 5 of 8 checks flagged (evidence only — the findings below are the record)
Analysis: static only — the bytes were read as text and were never executed, installed or run.
Ledger entry: 1547

## 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 (1 receipt, 1 version)

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

Machine form: https://www.rightshold.com/v1/resource-scans/github-com-neondatabase-labs-mcp-server-neon-f638e23562