The MCP ecosystem often has several independent packages implementing the same tool — and "Google Docs" currently has 8. 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 |
|---|---|---|---|---|---|---|
| Google Docsbest by node2flow | @node2flow/google-docs-mcp
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Google Docs by a-bonus | @a-bonus/google-docs-mcp
npm |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Google Docs & Drive by npm | mcp-google-docs
npm |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Google Docs by npm | google-docs-mcp
npm |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Google Docs by PyPI | google-docs-mcp
PyPI |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Google Docs by npm | google-docs-mcp-server
npm |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Google Docs by gigabrainobserver | google-docs-mcp-server
PyPI |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Google Docs by suncreation | @suncreation/mcp-google-docs
npm |
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.