Mongodb Atlas (montumodi) MCP Server

mongodb-atlas-mcp-server npm v1.7.0

Published by montumodi — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for MongoDB Atlas API using mongodb-atlas-api-client

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

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 − 4 = 96. 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 76

Each tool and what it can reach — statically extracted from the published source.

  • datalake_get_logs_streamreads sensitive data
  • alert_acknowledgeno sensitive capability
  • alert_getno sensitive capability
  • alert_get_allno sensitive capability
  • atlas_search_createno sensitive capability
  • atlas_search_deleteno sensitive capability
  • atlas_search_getno sensitive capability
  • atlas_search_get_allno sensitive capability
  • atlas_search_get_all_analyzersno sensitive capability
  • atlas_search_updateno sensitive capability
Show 66 more tools ↓
  • atlas_search_upsert_analyzerno sensitive capability
  • atlas_user_createno sensitive capability
  • atlas_user_get_allno sensitive capability
  • atlas_user_get_by_idno sensitive capability
  • atlas_user_get_by_nameno sensitive capability
  • atlas_user_updateno sensitive capability
  • cloud_backup_create_restore_jobno sensitive capability
  • cloud_backup_get_restore_jobno sensitive capability
  • cloud_backup_get_snapshotno sensitive capability
  • cloud_backup_get_snapshotsno sensitive capability
  • cloud_provider_access_createno sensitive capability
  • cloud_provider_access_deleteno sensitive capability
  • cloud_provider_access_get_allno sensitive capability
  • cloud_provider_access_updateno sensitive capability
  • cluster_createno sensitive capability
  • cluster_deleteno sensitive capability
  • cluster_getno sensitive capability
  • cluster_get_advanced_configurationno sensitive capability
  • cluster_get_allno sensitive capability
  • cluster_test_primary_failoverno sensitive capability
  • cluster_updateno sensitive capability
  • cluster_update_advanced_configurationno sensitive capability
  • custom_db_role_createno sensitive capability
  • custom_db_role_deleteno sensitive capability
  • custom_db_role_getno sensitive capability
  • custom_db_role_get_allno sensitive capability
  • custom_db_role_updateno sensitive capability
  • datalake_createno sensitive capability
  • datalake_deleteno sensitive capability
  • datalake_getno sensitive capability
  • datalake_get_allno sensitive capability
  • datalake_updateno sensitive capability
  • events_getno sensitive capability
  • events_get_allno sensitive capability
  • events_get_all_by_orgno sensitive capability
  • events_get_by_orgno sensitive capability
  • organization_deleteno sensitive capability
  • organization_get_allno sensitive capability
  • organization_get_by_idno sensitive capability
  • organization_get_projectsno sensitive capability
  • organization_get_usersno sensitive capability
  • organization_inviteno sensitive capability
  • organization_renameno sensitive capability
  • project_access_list_createno sensitive capability
  • project_access_list_deleteno sensitive capability
  • project_access_list_getno sensitive capability
  • project_access_list_get_allno sensitive capability
  • project_access_list_updateno sensitive capability
  • project_assign_teamsno sensitive capability
  • project_createno sensitive capability
  • project_deleteno sensitive capability
  • project_get_allno sensitive capability
  • project_get_by_idno sensitive capability
  • project_get_by_nameno sensitive capability
  • project_get_teamsno sensitive capability
  • project_remove_userno sensitive capability
  • project_whitelist_createno sensitive capability
  • project_whitelist_deleteno sensitive capability
  • project_whitelist_getno sensitive capability
  • project_whitelist_get_allno sensitive capability
  • project_whitelist_updateno sensitive capability
  • user_createno sensitive capability
  • user_deleteno sensitive capability
  • user_getno sensitive capability
  • user_get_allno sensitive capability
  • user_updateno sensitive capability

What this scan could not see

Versions 1

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.

VersionScoreFindingsEngineScanned
v1.7.0 latest A 96/100 0 1.13.0 2026-09-07

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.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mongodb-atlas-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/mongodb-atlas-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/mongodb-atlas-mcp-server"><img src="https://mcptrustchecker.com/registry/mongodb-atlas-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mongodb-atlas-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

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-atlas-mcp-server --online

Use the free API → How scoring works

Other implementations of Mongodb Atlas 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Cloud & DevOps