Graphql Enhanced MCP Server
@letoribo/mcp-graphql-enhanced
npm
v4.15.3
Published by @letoribo — 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.
Enhanced MCP server for GraphQL with dynamic headers and robust variables parsing — a drop-in replacement for mcp-graphql.
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 − 1 = 99. 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 |
|---|---|
| −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 1
medium Dynamic module load from a non-literal (dist/index.js)MTC-SRC-005
In the server's implementation (`dist/index.js:28`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. 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 pkg = require(pkgPath); return pkg.version; } catch { return "dev-version";
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
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v4.15.3 latest |
A 99/100 | 1 | 1.13.0 | 2026-08-31 |
v4.15.2 |
A 99/100 | 1 | 1.13.0 | 2026-08-29 |
v4.15.1 |
A 99/100 | 1 | 1.13.0 | 2026-08-28 |
v4.14.5 |
A 99/100 | 1 | 1.13.0 | 2026-08-25 |
v4.14.4 |
A 99/100 | 0 | 1.12.1 | 2026-08-12 |
Show 5 more versions ↓
v4.14.2 |
A 99/100 | 0 | 1.12.1 | 2026-08-09 |
v4.14.0 |
A 99/100 | 0 | 1.12.1 | 2026-08-07 |
v4.13.3 |
A 99/100 | 0 | 1.12.1 | 2026-07-31 |
v4.13.1 |
A 99/100 | 0 | 1.12.1 | 2026-07-27 |
v4.12.1 |
A 99/100 | 0 | 1.9.0 | 2026-07-23 |
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 @letoribo/mcp-graphql-enhanced --onlineMore in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.