The MCP ecosystem often has several independent packages implementing the same tool — and "Knowledge" 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 |
|---|---|---|---|---|---|---|
| Knowledge Source verifiedbest by cristinecula | knowledge-mcp
npm |
A 100/100 | High | Source | 2 | 2026-07-22 |
| Knowledge by recon-fuzz-mcp | @recon-fuzz-mcp/knowledge
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Knowledge by ecomfe | knowledge
npm |
A 100/100 | High | Source | 1 | 2026-07-22 |
| Knowledge by codemcp | @codemcp/knowledge
npm |
A 100/100 | High | Source | 4 | 2026-07-22 |
| Knowledge by jpereraaracil | @jpereraaracil/mcp-knowledge
npm |
A 98/100 | Minimal | Metadata | 1 | 2026-07-22 |
| Knowledge by npm | knowledge-mcp-server
npm |
A 98/100 | Moderate | Source | 2 | 2026-07-22 |
| Knowledge by olafgeibig | knowledge-mcp
PyPI |
A 98/100 | High | Source | 2 | 2026-07-22 |
| Knowledge by spothlynx | @spothlynx/knowledge-mcp
npm |
A 94/100 | High | Source | 3 | 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.