Resource-scan receipts

modelcontextprotocol/servers — fetch (README)

Canonical URL: https://raw.githubusercontent.com/modelcontextprotocol/servers/main/src/fetch/README.md · Fetched from: https://raw.githubusercontent.com/modelcontextprotocol/servers/main/src/fetch/README.md · Machine form: /v1/resource-scans/raw-githubusercontent-com-modelcontextprotocol-servers-m-060d8d97ca · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 770433653dce6c5806ed827723b832243cac03bfa72a152c7028de9f91e1e199 · 12272 bytes · scanned 2026-10-27T12:17:58.285Z · scanner resource-scan-v1 · ledger entry 1488.

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: docs.astral.sh, github.com, img.shields.io, insiders.vscode.dev. 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: docs.astral.sh; domain: github.com; domain: img.shields.io; domain: insiders.vscode.dev; fetch / XMLHttpRequest / WebSocket calls

• 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 — flag

  The scanned bytes contain shell-out or download patterns: download-and-execute pattern (fetched content passed to an executor in the same file). Code that runs shell commands acts with the full permissions of whoever runs it.

  Evidence: download-and-execute pattern (fetched content passed to an executor in the same file)

• 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; bytes scanned: 12272.

  Evidence: source host: raw.githubusercontent.com; repository: modelcontextprotocol/servers; bytes scanned: 12272

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 770433653dce6c58… · 12272 bytes · scanner resource-scan-v1 · ledger entry 1488