Database (nam088) MCP Server

@nam088/mcp-database-server npm v1.0.10

Published by @nam088 — 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 multiple database operations (PostgreSQL, MySQL, SQLite, Redis, MongoDB, LDAP)

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 52

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

  • execute_sqlreads sensitive data
  • explain_queryreads sensitive data
  • queryreads sensitive data
  • describe_tableno sensitive capability
  • describe_viewno sensitive capability
  • get_foreign_keysno sensitive capability
  • get_indexesno sensitive capability
  • get_table_sizeno sensitive capability
  • get_table_statsno sensitive capability
  • ldap_addno sensitive capability
Show 42 more tools ↓
  • ldap_authenticateno sensitive capability
  • ldap_compareno sensitive capability
  • ldap_deleteno sensitive capability
  • ldap_list_foldersno sensitive capability
  • ldap_modifyno sensitive capability
  • ldap_searchno sensitive capability
  • ldap_search_folder_structureno sensitive capability
  • list_schemasno sensitive capability
  • list_tablesno sensitive capability
  • list_viewsno sensitive capability
  • mongo_aggregateno sensitive capability
  • mongo_countno sensitive capability
  • mongo_create_indexno sensitive capability
  • mongo_delete_manyno sensitive capability
  • mongo_delete_oneno sensitive capability
  • mongo_findno sensitive capability
  • mongo_find_oneno sensitive capability
  • mongo_get_collection_statsno sensitive capability
  • mongo_get_database_statsno sensitive capability
  • mongo_get_indexesno sensitive capability
  • mongo_insert_manyno sensitive capability
  • mongo_insert_oneno sensitive capability
  • mongo_list_collectionsno sensitive capability
  • mongo_update_manyno sensitive capability
  • mongo_update_oneno sensitive capability
  • redis_dbsizeno sensitive capability
  • redis_delno sensitive capability
  • redis_existsno sensitive capability
  • redis_expireno sensitive capability
  • redis_getno sensitive capability
  • redis_hgetno sensitive capability
  • redis_hgetallno sensitive capability
  • redis_hsetno sensitive capability
  • redis_infono sensitive capability
  • redis_keysno sensitive capability
  • redis_lrangeno sensitive capability
  • redis_setno sensitive capability
  • redis_smembersno sensitive capability
  • redis_ttlno sensitive capability
  • redis_typeno sensitive capability
  • redis_zrangeno sensitive capability
  • search_tablesno 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.0.10 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/nam088-mcp-database-server/badge.svg)](https://mcptrustchecker.com/registry/nam088-mcp-database-server)
HTML
<a href="https://mcptrustchecker.com/registry/nam088-mcp-database-server"><img src="https://mcptrustchecker.com/registry/nam088-mcp-database-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/nam088-mcp-database-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 @nam088/mcp-database-server --online

Use the free API → How scoring works

Other implementations of Database 14

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

More in Databases