Resource-scan receipts

apollographql/apollo-mcp-server

Canonical URL: https://github.com/apollographql/apollo-mcp-server · Fetched from: https://raw.githubusercontent.com/apollographql/apollo-mcp-server/HEAD/README.md · Machine form: /v1/resource-scans/github-com-apollographql-apollo-mcp-server-b7f114c00e · Markdown

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: a4024c9582ba0fa71ac15dbbaa511298c36138f2466a0d7cff0b9d313ccbf7fb · 3863 bytes · scanned 2026-10-27T12:19:20.712Z · scanner resource-scan-v1 · ledger entry 1521.

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: codecov.io, crates.io, github.com, img.shields.io, mcptoplist.com, modelcontextprotocol.io, raw.githubusercontent.com, www.apollographql.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: codecov.io; domain: crates.io; domain: github.com; domain: img.shields.io; domain: mcptoplist.com; domain: modelcontextprotocol.io; domain: raw.githubusercontent.com; domain: www.apollographql.com

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

  Evidence: source host: github.com; repository: apollographql/apollo-mcp-server; bytes scanned: 3863; fetched from: https://raw.githubusercontent.com/apollographql/apollo-mcp-server/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 a4024c9582ba0fa7… · 3863 bytes · scanner resource-scan-v1 · ledger entry 1521