The MCP ecosystem often has several independent packages implementing the same tool — and "Graphql" currently has 7. Every one of them was scanned with the same deterministic engine, so the numbers below are directly comparable: the Trust Score (A–F), the capability blast radius, and how much of the package the scan could actually inspect. They are ranked by score; ties break toward unscoped, longer-established packages.
| Implementation | Package | Trust | Capability | Coverage | Findings | Scanned |
|---|---|---|---|---|---|---|
| Graphql Source verifiedbest by blurrah | mcp-graphql
npm |
A 100/100 | Minimal | Metadata | 0 | 2026-07-22 |
| Graphql Source verified by cubicecho | @cubicecho/graphql-mcp
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Graphql by iflow-mcp | @iflow-mcp/mcp-graphql
npm |
A 100/100 | Minimal | Metadata | 0 | 2026-07-22 |
| Graphql by zibu.app | @zibu.app/mcp-graphql
npm |
A 100/100 | Minimal | Metadata | 0 | 2026-07-22 |
| Graphql by noamski | graphql-mcp
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Graphql by supernova123 | @supernova123/graphql-mcp-server
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Graphql by PyPI | mcp-graphql
PyPI |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
A higher-ranked implementation is not "the official one" — ranking reflects only what the deterministic scan found in each published package. Open an implementation to read its individual findings with evidence, its scan history per version, and to grab an embeddable badge. Scores are automated opinions, recomputed on every rescan.