Safety rating · all kinds

datalayer/jupyter-mcp-server

Score 61/100 — Moderate public signals

Automated checks of public signals as of the date shown. Not a security audit, certification or endorsement, and not a statement about the people who maintain the project. Signals can be incomplete or out of date; each check shows its evidence and source so anyone can verify it.

Checks

• Credential and environment access — Not found (0/15): The scan flagged this check: 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.
• Known-bad indicators — Found (15/15): The scan recorded a pass: None of the scanner's published known-bad indicator patterns matched the scanned bytes.
• Shell-outs and download-and-execute — Found (12/12): The scan recorded a pass: No shell-out or download-and-execute patterns were found in the scanned bytes.
• Install and postinstall hooks — Found (12/12): The scan recorded a pass: No install or postinstall hooks were found in the scanned bytes.
• Obfuscation and encoded payloads — Found (10/10): The scan recorded a pass: No obfuscation or encoded-payload signs were found in the scanned bytes.
• Outbound network references — Not found (0/10): The scan flagged this check: 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.
• Permission declarations vs behavior — Not found (0/10): The scan flagged this check: The bytes show network, credentials behavior, and no permissions declaration was found in the scanned bytes to compare it against.
• Provenance facts (weak signals) — Found (6/6): The scan recorded a 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.