MongoDB (official) (mongodb-js) MCP Server
mongodb-mcp-server
npm
v2.1.1
Source verified
Published by mongodb-js — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MongoDB’s official MCP server: query collections, inspect schemas and run aggregations.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 4
high Shell/command execution in server code (dist/cjs/setup/aiTool.js)MTC-SRC-002
In the server's implementation (`dist/cjs/setup/aiTool.js:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ("jsonc-parser"); const child_process_1 = require("child_process"); const setupAiToolsUtils_js_1 = require("./setupAiToo
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cjs/setup/aiTool.js
high Shell/command execution in server code (dist/cjs/setup/installSkills.js)MTC-SRC-002
In the server's implementation (`dist/cjs/setup/installSkills.js:11`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: o-console */ const node_child_process_1 = require("node:child_process"); const chalk_1 = __importDefault(require("chalk"
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cjs/setup/installSkills.js
high Shell/command execution in server code (dist/esm/setup/aiTool.js)MTC-SRC-002
In the server's implementation (`dist/esm/setup/aiTool.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ; import { exec } from "child_process"; import { formatError, getPlatform } from "./setupAiToolsUtils.js"; // These are
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/esm/setup/aiTool.js
high Shell/command execution in server code (dist/esm/setup/installSkills.js)MTC-SRC-002
In the server's implementation (`dist/esm/setup/installSkills.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import chalk from "chalk"; import { confirm } from "@inquirer/prompts"; import {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/esm/setup/installSkills.js
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions 4
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.1.1 latest |
A 94/100 | 4 | 1.13.0 | 2026-09-04 |
v2.1.0 |
A 94/100 | 4 | 1.13.0 | 2026-08-25 |
v2.0.0 |
A 94/100 | 4 | 1.12.1 | 2026-08-05 |
v1.14.0 |
A 94/100 | 4 | 1.12.1 | 2026-07-27 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mongodb-mcp-server --onlineOther implementations of MongoDB (official) 9
Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →
MCP server for comprehensive MongoDB integration: database operations, collections, aggregation, queries, connection management, monitoring
MongoDB MCP server for local mongodb queries
High-performance MongoDB Model Context Protocol (MCP) server optimized for LLMs - enables AI agents to safely and efficiently query and manipulate MongoDB data with type safety, schema validation, and controlled access patterns
Feature-rich MCP server for MongoDB with multi-connection support
Local stdio MCP server for MongoDB with multi-environment support and production write protection.
MongoDB MCP server for local mongodb queries
More in Databases
Security scan results for the A5sql MCP server.
Expose AgentsKit tools as an MCP server — use them from Claude Desktop, Cursor, Windsurf, or any MCP host.
MCP server for Aiven cloud data platform - manage PostgreSQL, Kafka, and other services
MCP Server for All-Inkl.com hosting via KAS API
Structured aquarium, marine, terrarium and paludarium data for AI agents.
MCP server that gives your AI agent real vehicle data — specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II DTC reference — from the CarVector API.