The MCP ecosystem often has several independent packages implementing the same tool — and "Aws S3" currently has 4. 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 |
|---|---|---|---|---|---|---|
| Aws S3 Source verifiedbest by samuraikun | aws-s3-mcp
npm |
A 100/100 | Minimal | Source | 0 | 2026-07-22 |
| Aws S3 Source verified by antidrift | @antidrift/mcp-aws-s3
npm |
A 100/100 | High | Source | 2 | 2026-07-22 |
| Aws S3 Source verified by gangadharrr | @gangadharrr/aws-s3
npm |
A 100/100 | Minimal | Metadata | 0 | 2026-07-22 |
| Aws S3 by npm | aws-s3-mcp-server
npm |
A 100/100 | Minimal | Source | 0 | 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.