Sqemo MCP Server

sqemo-mcp npm v2.8.1

Published by sqemo — 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 Sqemo - query and edit ERDs with your team's naming standards

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 99 − adoption risk = 92/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 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Hardcoded JSON Web Token in server code MTC-SRC-008 exfiltration

2. Client adoption risk — 99 − 7 = 92. 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 3

high Shell/command execution in server code (dist/index.js)MTC-SRC-002

In the server's implementation (`dist/index.js:14`): 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 { spawn } from "child_process"; function buildOpenCommand(url, platform) { if (platform === "win32") { ret

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/index.js

low Hardcoded JSON Web Token in server code (dist/chunk-XH77B4QM.js)MTC-SRC-008

A hardcoded JSON Web Token (a public-by-design (anon/publishable) key — RLS, not secrecy, protects it) appears in `dist/chunk-XH77B4QM.js:192`. Verify whether this is a real credential; if so, remove and rotate it.

Evidence: JSON Web Token: eyJh…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server dist/chunk-XH77B4QM.js

low Unconstrained path parameter "file" on "create_erd"MTC-CAP-008

Tool "create_erd" takes a path parameter "file" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool create_erd · inputSchema.properties.file

Tools 39

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

  • check_db_driftreads sensitive data
  • create_erdreads sensitive data
  • import_sqlreads sensitive data
  • auto_layoutno sensitive capability
  • check_namingno sensitive capability
  • delete_attributeno sensitive capability
  • delete_dictionary_wordno sensitive capability
  • delete_domainno sensitive capability
  • delete_entityno sensitive capability
  • delete_relationshipno sensitive capability
Show 29 more tools ↓
  • diff_erdsno sensitive capability
  • export_alter_sqlno sensitive capability
  • export_dbmlno sensitive capability
  • export_sqlno sensitive capability
  • generate_physical_nameno sensitive capability
  • get_entityno sensitive capability
  • get_erd_overviewno sensitive capability
  • import_dbmlno sensitive capability
  • introspect_dbno sensitive capability
  • lint_erdno sensitive capability
  • list_domainsno sensitive capability
  • list_entitiesno sensitive capability
  • list_erdsno sensitive capability
  • list_proposalsno sensitive capability
  • list_relationshipsno sensitive capability
  • list_workspacesno sensitive capability
  • propose_dictionary_wordno sensitive capability
  • search_dictionaryno sensitive capability
  • update_naming_rulesno sensitive capability
  • upsert_attributeno sensitive capability
  • upsert_attributesno sensitive capability
  • upsert_dictionary_wordno sensitive capability
  • upsert_dictionary_wordsno sensitive capability
  • upsert_domainno sensitive capability
  • upsert_domainsno sensitive capability
  • upsert_entityno sensitive capability
  • upsert_relationshipno sensitive capability
  • validate_erdno sensitive capability
  • withdraw_proposalno sensitive capability

What this scan could not see

Versions 10

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
v2.8.1 latest A 92/100 3 1.13.0 2026-09-08
v2.6.0 A 92/100 3 1.13.0 2026-08-28
v2.5.4 A 92/100 3 1.13.0 2026-08-27
v2.5.1 A 92/100 3 1.12.1 2026-08-10
v2.4.0 A 92/100 3 1.12.1 2026-08-09
Show 5 more versions ↓
v2.1.1 A 92/100 3 1.12.1 2026-08-07
v2.0.0 A 92/100 3 1.12.1 2026-08-06
v1.5.0 A 92/100 3 1.12.1 2026-08-05
v1.3.0 A 95/100 2 1.12.1 2026-07-29
v1.2.1 A 95/100 2 1.10.0 2026-07-25

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

Use the free API → How scoring works

More in Developer Tools