Drawdb MCP Server

drawdb-mcp npm v0.6.0

Published by iceyxsm — 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.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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.
A Why this grade threat 100 − adoption risk = 93/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 − 7 = 93. 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
−6 capability blast radius (high) — 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 2

high Shell/command execution in server code (src/tools/browser.js)MTC-SRC-002

In the server's implementation (`src/tools/browser.js:3`): 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 { existsSync } from "node:fs"; import { homedir, platform, tmpdir } fro

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 src/tools/browser.js

medium Hardcoded egress to an external endpoint (src/tools/browser.js)MTC-SRC-003

In the server's implementation (`src/tools/browser.js:68`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { const res = await fetch(`http://${host}:${port}/json`); if (!res.ok) { throw new Error( `Failed to

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 src/tools/browser.js

Tools 44

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

  • export_to_filenetwork egress
  • add_enumno sensitive capability
  • add_fieldno sensitive capability
  • add_indexno sensitive capability
  • add_noteno sensitive capability
  • add_relationshipno sensitive capability
  • add_tableno sensitive capability
  • apply_templateno sensitive capability
  • describe_relationshipno sensitive capability
  • describe_tableno sensitive capability
Show 34 more tools ↓
  • design_schemano sensitive capability
  • explain_schemano sensitive capability
  • export_dbmlno sensitive capability
  • export_ddlno sensitive capability
  • export_deployment_bundleno sensitive capability
  • export_jsonno sensitive capability
  • find_drawdb_tabno sensitive capability
  • generate_migrationno sensitive capability
  • get_design_promptno sensitive capability
  • get_schema_summaryno sensitive capability
  • get_thinking_contextno sensitive capability
  • launch_browserno sensitive capability
  • list_enumsno sensitive capability
  • list_relationshipsno sensitive capability
  • list_tablesno sensitive capability
  • list_templatesno sensitive capability
  • list_typesno sensitive capability
  • new_diagramno sensitive capability
  • open_in_drawdbno sensitive capability
  • reload_drawdb_tabno sensitive capability
  • remove_fieldno sensitive capability
  • remove_relationshipno sensitive capability
  • remove_tableno sensitive capability
  • reset_thinkingno sensitive capability
  • review_schemano sensitive capability
  • search_tablesno sensitive capability
  • snapshot_schemano sensitive capability
  • think_about_editno sensitive capability
  • think_about_reviewno sensitive capability
  • think_about_schemano sensitive capability
  • update_fieldno sensitive capability
  • upgrade_to_productionno sensitive capability
  • validate_constraintsno sensitive capability
  • validate_schema_qualityno 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
v0.6.0 latest A 93/100 2 1.9.0 2026-07-24

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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/drawdb-mcp/badge.svg)](https://mcptrustchecker.com/registry/drawdb-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/drawdb-mcp"><img src="https://mcptrustchecker.com/registry/drawdb-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/drawdb-mcp/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 drawdb-mcp --online

Use the free API → How scoring works

More in Developer Tools