Resource-scan receipts

modelcontextprotocol/servers-archived — redis (package.json)

Canonical URL: https://raw.githubusercontent.com/modelcontextprotocol/servers-archived/main/src/redis/package.json · Fetched from: https://raw.githubusercontent.com/modelcontextprotocol/servers-archived/main/src/redis/package.json · Machine form: /v1/resource-scans/raw-githubusercontent-com-modelcontextprotocol-servers-a-2edb5a9912 · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 993d67d9f3a4bb7831e192bee998dc09539ba775358ca6d20db4898b864cb639 · 769 bytes · scanned 2026-10-27T12:28:04.558Z · scanner resource-scan-v1 · ledger entry 1713.

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: anthropic.com, github.com, modelcontextprotocol.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: anthropic.com; domain: github.com; domain: modelcontextprotocol.io

• Credential and environment access — pass

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

• Install and postinstall hooks — flag

  Install-time hooks are present: package.json script "prepare": npm run build. A hook runs code at install time, before the resource itself is ever invoked.

  Evidence: package.json script "prepare": npm run build

• 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: raw.githubusercontent.com; repository: modelcontextprotocol/servers-archived; bytes scanned: 769.

  Evidence: source host: raw.githubusercontent.com; repository: modelcontextprotocol/servers-archived; bytes scanned: 769

History

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

• 2026-10-27 — 3 of 8 checks flagged · SHA-256 993d67d9f3a4bb78… · 769 bytes · scanner resource-scan-v1 · ledger entry 1713