Resource-scan receipts

hangwin/mcp-chrome

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

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 949370768e87221359abaaf50e72a667ee0db77d80cb636cc2655ba7eb7247d3 · 13102 bytes · scanned 2026-10-27T12:21:56.123Z · scanner resource-scan-v1 · ledger entry 1565.

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: developer.chrome.com, github.com, img.shields.io, opensource.org, www.typescriptlang.org, www.youtube.com, youtu.be. 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: developer.chrome.com; domain: github.com; domain: img.shields.io; domain: opensource.org; domain: www.typescriptlang.org; domain: www.youtube.com; domain: youtu.be

• 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: hangwin/mcp-chrome; bytes scanned: 13102; fetched from: https://raw.githubusercontent.com/hangwin/mcp-chrome/HEAD/README.md.

  Evidence: source host: github.com; repository: hangwin/mcp-chrome; bytes scanned: 13102; fetched from: https://raw.githubusercontent.com/hangwin/mcp-chrome/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 949370768e872213… · 13102 bytes · scanner resource-scan-v1 · ledger entry 1565