Resource-scan receipts

cloudflare/mcp-server-cloudflare

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

Latest receipt: 1 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 6e79c8c11bd111e95917c001e756d1458854099caf0655b46cfeb16243a7dd3d · 9379 bytes · scanned 2026-10-27T12:21:14.263Z · scanner resource-scan-v1 · ledger entry 1543.

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: ai-gateway.mcp.cloudflare.com, auditlogs.mcp.cloudflare.com, autorag.mcp.cloudflare.com, bindings.mcp.cloudflare.com, blog.mcp.cloudflare.com, browser.mcp.cloudflare.com, builds.mcp.cloudflare.com, casb.mcp.cloudflare.com, containers.mcp.cloudflare.com, dash.cloudflare.com, demo-day.mcp.cloudflare.com, dex.mcp.cloudflare.com, dns-analytics.mcp.cloudflare.com, docs.mcp.cloudflare.com, github.com, graphql.mcp.cloudflare.com, logs.mcp.cloudflare.com, mcp.cloudflare.com, modelcontextprotocol.io, observability.mcp.cloudflare.com, openai.com, playground.ai.cloudflare.com, radar.mcp.cloudflare.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: ai-gateway.mcp.cloudflare.com; domain: auditlogs.mcp.cloudflare.com; domain: autorag.mcp.cloudflare.com; domain: bindings.mcp.cloudflare.com; domain: blog.mcp.cloudflare.com; domain: browser.mcp.cloudflare.com; domain: builds.mcp.cloudflare.com; domain: casb.mcp.cloudflare.com; domain: containers.mcp.cloudflare.com; domain: dash.cloudflare.com; domain: demo-day.mcp.cloudflare.com; domain: dex.mcp.cloudflare.com; domain: dns-analytics.mcp.cloudflare.com; domain: docs.mcp.cloudflare.com; domain: github.com; domain: graphql.mcp.cloudflare.com; domain: logs.mcp.cloudflare.com; domain: mcp.cloudflare.com; domain: modelcontextprotocol.io; domain: observability.mcp.cloudflare.com; domain: openai.com; domain: playground.ai.cloudflare.com; domain: radar.mcp.cloudflare.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 — pass

  The bytes show network behavior, and a permissions declaration is present in the bytes: <img width="937" alt="Screenshot 2025-05-21 at 10 38 02 AM" src="https://github.com/user-attachments/assets/872e253f-23ce-43b3-983c-45f9d0f66100" />

  Evidence: behavior: network; declared: <img width="937" alt="Screenshot 2025-05-21 at 10 38 02 AM" src="https://github.com/user-attachments/assets/872e253f-23ce-43b3-983c-45f9d0f66100" />

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

  Evidence: source host: github.com; repository: cloudflare/mcp-server-cloudflare; bytes scanned: 9379; fetched from: https://raw.githubusercontent.com/cloudflare/mcp-server-cloudflare/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 — 1 of 8 checks flagged · SHA-256 6e79c8c11bd111e9… · 9379 bytes · scanner resource-scan-v1 · ledger entry 1543