Safety rating · all kinds

mongodb-js/mongodb-mcp-server

Score 37/100 — Limited 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 — Not found (0/12): The scan flagged this check: 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.
• 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 — Not found (0/10): The scan flagged this check: 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.
• Outbound network references — Not found (0/10): The scan flagged this check: 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.
• 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: mongodb-js/mongodb-mcp-server; bytes scanned: 109231; fetched from: https://raw.githubusercontent.com/mongodb-js/mongodb-mcp-server/HEAD/README.md.