Resource-scan receipts

mongodb-js/mongodb-mcp-server

Canonical URL: https://github.com/mongodb-js/mongodb-mcp-server · Fetched from: https://raw.githubusercontent.com/mongodb-js/mongodb-mcp-server/HEAD/README.md · Machine form: /v1/resource-scans/github-com-mongodb-js-mongodb-mcp-server-2118aa6129 · Markdown

Latest receipt: 5 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 977afdb3eedfd395a38d87f0e18758de6e9926f09ae00d7b2d4302d60f12ea92 · 109231 bytes · scanned 2026-10-27T12:21:24.473Z · scanner resource-scan-v1 · ledger entry 1548.

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: claude.com, cloud.mongodb.com, cursor.com, geminicli.com, github.com, hub.docker.com, img.shields.io, insiders.vscode.dev, knowledge.mongodb.com, modelcontextprotocol.io, nodejs.org, proxy.example.com, www.mongodb.com, 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: claude.com; domain: cloud.mongodb.com; domain: cursor.com; domain: geminicli.com; domain: github.com; domain: hub.docker.com; domain: img.shields.io; domain: insiders.vscode.dev; domain: knowledge.mongodb.com; domain: modelcontextprotocol.io; domain: nodejs.org; domain: proxy.example.com; domain: www.mongodb.com; domain: www.npmjs.com

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

  The scanned bytes carry obfuscation or encoding signs: 2 long base64-shaped runs (120+ characters). Encoded content cannot be read from the bytes alone, so what it does cannot be checked from the bytes alone either.

  Evidence: 2 long base64-shaped runs (120+ characters)

• Shell-outs and download-and-execute — flag

  The scanned bytes contain shell-out or download patterns: shell command tools named in the bytes (curl, wget, powershell). Code that runs shell commands acts with the full permissions of whoever runs it.

  Evidence: shell command tools named in the bytes (curl, wget, powershell)

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

  Evidence: source host: github.com; repository: mongodb-js/mongodb-mcp-server; bytes scanned: 109231; fetched from: https://raw.githubusercontent.com/mongodb-js/mongodb-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 — 5 of 8 checks flagged · SHA-256 977afdb3eedfd395… · 109231 bytes · scanner resource-scan-v1 · ledger entry 1548