Figma MCP Rust
Figma MCP build with Rust, server with full read/write access via plugin (no REST API, no rate limits, 73 tools)
Is Figma MCP Rust safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Figma MCP Rust
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Figma MCP Rust scores 48.9/100 (Grade D), ranked #970 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.2/10; recent commits are unsigned; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →
How Figma MCP Rust compares in MCP Servers
- #559 Zapier 48.9 ±0
- #560 Grok MCP 48.9 ±0
- #561 Figma MCP Rust 48.9 this agent
- #562 Mobile Device MCP 48.9 ±0
- #563 Codex MCP Tool 48.9 ±0
Bars show each HVTrust score; the tick marks Figma MCP Rust’s 48.9.
Where the 48.9 comes from
HVTrust dimensions vs the MCP Servers average
48.9 / 100 · 100.0% confidenceFigma MCP Rust MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
38.8 / 100Supply Chain Trust
Common questions about Figma MCP Rust
Does Figma MCP Rust publish package provenance?
Does Figma MCP Rust have an OpenSSF Scorecard?
Is Figma MCP Rust actively maintained?
What license does Figma MCP Rust use?
Are Figma MCP Rust's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Figma MCP Rust's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Figma MCP Rust?
For maintainers
HVTrust scores Figma MCP Rust from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/figma-mcp-rust)
<a href="https://hvtracker.net/agents/figma-mcp-rust"><img src="https://hvtracker.net/badge/figma-mcp-rust.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON