The MCP ecosystem often has several independent packages implementing the same tool — and "Figma Mcp Bridge" currently has 5. 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 |
|---|---|---|---|---|---|---|
| Figma Mcp Bridgebest by magic-spells | @magic-spells/figma-mcp-bridge
npm |
A 99/100 | Minimal | Source | 0 | 2026-09-07 |
| Figma Mcp Bridge Source verified by gethopp | @gethopp/figma-mcp-bridge
npm |
A 97/100 | Moderate | Source | 0 | 2026-09-06 |
| Figma Mcp Bridge by maxisoft | @maxisoft/figma-mcp-bridge
npm |
A 96/100 | Moderate | Source | 0 | 2026-09-07 |
| Figma Mcp Bridge by symmetry-labs | figma-mcp-bridge
npm |
B 87/100 | Minimal | Metadata | 0 | 2026-09-07 |
| Figma Mcp Bridge by atezer | @atezer/figma-mcp-bridge
npm |
D 67/100 | Critical | Source | 7 | 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.