The MCP ecosystem often has several independent packages implementing the same tool — and "Clockify" currently has 11. 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 |
|---|---|---|---|---|---|---|
| Clockify Source verifiedbest by honeyfield | @honeyfield/clockify-mcp
npm |
A 100/100 | Minimal | Source | 0 | 2026-09-07 |
| Clockify by jeremyvyska | @jeremyvyska/clockify-mcp
npm |
A 99/100 | Minimal | Source | 0 | 2026-09-07 |
| Mcp Clockify by aslamanver | mcp_clockify
npm |
A 99/100 | Minimal | Source | 0 | 2026-09-07 |
| Clockify by yikizi | @yikizi/clockify-mcp
npm |
A 99/100 | Minimal | Source | 0 | 2026-09-07 |
| Clockify by lewinnovation | @lewinnovation/clockify-mcp-server
npm |
A 99/100 | Minimal | Source | 0 | 2026-09-07 |
| Clockify by ratheesh-aot | @ratheesh-aot/clockify-mcp-server
npm |
A 99/100 | Minimal | Source | 0 | 2026-09-07 |
| Clockify by ivanherula | @ivanherula/clockify-mcp-server
npm |
A 98/100 | Minimal | Source | 0 | 2026-09-07 |
| Clockify by PyPI | clockify-mcp-server
PyPI |
A 98/100 | Minimal | Source | 0 | 2026-08-25 |
| Clockify by tracegazer | clockify-mcp
PyPI |
A 96/100 | Moderate | Source | 1 | 2026-08-25 |
| Clockify by npm | clockify-mcp-server
npm |
B 87/100 | Minimal | Metadata | 0 | 2026-09-07 |
| Clockify by npm | clockify-mcp
npm |
B 87/100 | Minimal | Metadata | 0 | 2026-09-07 |
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.