Gqldb MCP Server
@ultipa-graph/gqldb-mcp
npm
v1.1.3
Published by @ultipa-graph — 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.
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:
| Points | Adoption-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
Tools 56
Each tool and what it can reach — statically extracted from the published source.
get_instance_logsingests untrusted inputadd_firewall_ruleno sensitive capabilityclear_backup_scheduleno sensitive capabilitycreate_backupno sensitive capabilitycreate_graphno sensitive capabilitycreate_instanceno sensitive capabilitydelete_backupno sensitive capabilitydelete_graphno sensitive capabilitydelete_instanceno sensitive capabilitydescribe_schemano sensitive capability
Show 46 more tools ↓
explain_queryno sensitive capabilityget_accountno sensitive capabilityget_auto_reloadno sensitive capabilityget_balanceno sensitive capabilityget_db_licenseno sensitive capabilityget_db_versionno sensitive capabilityget_enterprise_statusno sensitive capabilityget_instanceno sensitive capabilityget_instance_credentialsno sensitive capabilityget_latest_versionno sensitive capabilityget_live_metricsno sensitive capabilityget_metrics_historyno sensitive capabilityget_my_ipno sensitive capabilityget_operations_lockno sensitive capabilityget_payment_methodno sensitive capabilityget_trial_statusno sensitive capabilityget_usageno sensitive capabilityimport_datano sensitive capabilitylist_alertsno sensitive capabilitylist_backupsno sensitive capabilitylist_deleted_instancesno sensitive capabilitylist_firewall_rulesno sensitive capabilitylist_graphsno sensitive capabilitylist_instance_alertsno sensitive capabilitylist_instance_sizesno sensitive capabilitylist_instancesno sensitive capabilitylist_regionsno sensitive capabilitylist_transactionsno sensitive capabilitylookup_docsno sensitive capabilitypause_instanceno sensitive capabilityreload_db_statsno sensitive capabilityremove_firewall_ruleno sensitive capabilityrename_instanceno sensitive capabilityreset_admin_passwordno sensitive capabilityrestart_instanceno sensitive capabilityrestore_backupno sensitive capabilityresume_instanceno sensitive capabilityrun_algono sensitive capabilityrun_gql_queryno sensitive capabilityset_backup_scheduleno sensitive capabilityset_log_levelno sensitive capabilitytest_connectionno sensitive capabilityupgrade_versionno sensitive capabilitywait_for_instance_statusno sensitive capabilitywrite_datano sensitive capabilitywrite_procedureno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (56 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.3 latest |
A 96/100 | 0 | 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.
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 @ultipa-graph/gqldb-mcp --onlineMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.