Resource-scan receipts

modelcontextprotocol/typescript-sdk

Canonical URL: https://github.com/modelcontextprotocol/typescript-sdk · Fetched from: https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/HEAD/README.md · Machine form: /v1/resource-scans/github-com-modelcontextprotocol-typescript-sdk-f7fb7d70e0 · Markdown

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: d776beb7f1d0194da22e7d82cc84d869bd4ae805ba5d8283b69f57dec5b64dd6 · 8317 bytes · scanned 2026-10-27T12:18:28.051Z · scanner resource-scan-v1 · ledger entry 1494.

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: github.com, img.shields.io, modelcontextprotocol.io, standardschema.dev, ts.sdk.modelcontextprotocol.io, www.npmjs.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: github.com; domain: img.shields.io; domain: modelcontextprotocol.io; domain: standardschema.dev; domain: ts.sdk.modelcontextprotocol.io; domain: www.npmjs.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: modelcontextprotocol/typescript-sdk; bytes scanned: 8317; fetched from: https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/HEAD/README.md.

  Evidence: source host: github.com; repository: modelcontextprotocol/typescript-sdk; bytes scanned: 8317; fetched from: https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/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 d776beb7f1d0194d… · 8317 bytes · scanner resource-scan-v1 · ledger entry 1494