The MCP ecosystem often has several independent packages implementing the same tool — and "Testrail" 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 |
|---|---|---|---|---|---|---|
| Testrail Source verifiedbest by bun913 | @bun913/mcp-testrail
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Testrail Source verified by uarlouski | @uarlouski/testrail-mcp-server
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Testrail by denys-ispaniuk | mcp-testrail
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Testrail by Derrbal | testrail-mcp-server
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Testrail by g-tiwari | @g-tiwari/mcp-testrail
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Testrail by tenbarrel6 | @tenbarrel6/testrail-mcp
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Testrail by PyPI | testrail-mcp
PyPI |
A 98/100 | Minimal | Source | 1 | 2026-07-22 |
| Testrail by Sergey-Bl | testrail-mcp-server
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.