Resource-scan receipts

apify/apify-mcp-server

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

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: f2b25de13d0c47de5f3d1cc38fe6b6f8e6604881f3c924778b26688afd42e8f4 · 38076 bytes · scanned 2026-10-27T12:19:07.533Z · scanner resource-scan-v1 · ledger entry 1514.

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: agi.apify.com, api.apify.com, api.skyfire.xyz, apify.com, base.org, blog.apify.com, claude.ai, code.visualstudio.com, docs.apify.com, github.com, hub.docker.com, img.shields.io, img.youtube.com, json-schema.org, kiro.dev, mcp.apify.com, modelcontextprotocol.org, nodejs.org, pkg.pr.new, raw.githubusercontent.com, sentry.io, smithery.ai, www.npmjs.com, www.skyfire.xyz, www.x402.org, www.youtube.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: agi.apify.com; domain: api.apify.com; domain: api.skyfire.xyz; domain: apify.com; domain: base.org; domain: blog.apify.com; domain: claude.ai; domain: code.visualstudio.com; domain: docs.apify.com; domain: github.com; domain: hub.docker.com; domain: img.shields.io; domain: img.youtube.com; domain: json-schema.org; domain: kiro.dev; domain: mcp.apify.com; domain: modelcontextprotocol.org; domain: nodejs.org; domain: pkg.pr.new; domain: raw.githubusercontent.com; domain: sentry.io; domain: smithery.ai; domain: www.npmjs.com; domain: www.skyfire.xyz; domain: www.x402.org; domain: www.youtube.com

• 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); credential file paths (.env, .ssh, credential stores); 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); credential file paths (.env, .ssh, credential stores); 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 — 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, 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: apify/apify-mcp-server; bytes scanned: 38076; fetched from: https://raw.githubusercontent.com/apify/apify-mcp-server/HEAD/README.md.

  Evidence: source host: github.com; repository: apify/apify-mcp-server; bytes scanned: 38076; fetched from: https://raw.githubusercontent.com/apify/apify-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 — 3 of 8 checks flagged · SHA-256 f2b25de13d0c47de… · 38076 bytes · scanner resource-scan-v1 · ledger entry 1514