Resource-scan receipts

datalayer/jupyter-mcp-server

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

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

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: assets.datalayer.tech, contrib.rocks, datalayer.ai, discord.gg, docs.astral.sh, github.com, host.docker.internal, hub.docker.com, images.datalayer.io, img.shields.io, jupyter-mcp-server.datalayer.tech, jupyter.org, mcp.datalayer.run, modelcontextprotocol.io, opensource.org, pepy.tech, pypi.org. 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: assets.datalayer.tech; domain: contrib.rocks; domain: datalayer.ai; domain: discord.gg; domain: docs.astral.sh; domain: github.com; domain: host.docker.internal; domain: hub.docker.com; domain: images.datalayer.io; domain: img.shields.io; domain: jupyter-mcp-server.datalayer.tech; domain: jupyter.org; domain: mcp.datalayer.run; domain: modelcontextprotocol.io; domain: opensource.org; domain: pepy.tech; domain: pypi.org

• 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). 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)

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

  Evidence: source host: github.com; repository: datalayer/jupyter-mcp-server; bytes scanned: 22457; fetched from: https://raw.githubusercontent.com/datalayer/jupyter-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 f3655b141e5d29be… · 22457 bytes · scanner resource-scan-v1 · ledger entry 1526