Figma Context MCP

MCP server to provide Figma layout information to AI coding agents like Cursor

Protocols & Tool Integration TypeScript Grade C Listed MIT
55.2/100
Rank #395 of 1283
Compare Figma Context MCP

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-07 · 8d ago
Recent change
Rank +4

Is Figma Context MCP safe? Figma Context MCP scores 55.2/100 (Grade C), ranked #395 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.4/10; 82% of recent commits are signed; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-15
Rank Moved
Rank rose 15 spots (#410 → #395)
2026-08-13
Rank Moved
Rank dropped 16 spots (#393 → #409)
2026-08-12
Rank Moved
Rank rose 12 spots (#405 → #393)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
63.5
Activity sub-score · out of 100
#27

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-15 10:32 UTC · Repo last pushed 8 days ago

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
15.7k
Forks
1.2k
Last Push
2026-08-07
8 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
6
Rank Change
▲15
was #410

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

55.2 / 100 · 100.0% confidence

Figma Context MCP Protocols & Tool Integration average (57 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.6 / 25
1.0 above avg 8.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
0.8 above avg 11.4
Maintenance60% last-push freshness · 40% commit activity
11.5 / 20
2.3 below avg 13.8
AdoptionLog-scaled stars · package downloads
10.1 / 20
in line with avg 10.4

Activity Inputs

63.5 / 100
StarsRepository reach
25.2 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
14.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.4 / 10
OpenSSF Scorecard · scanned Aug 15, 2026
Signed Commits
82%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 9
CII-Best-Practices 0
Code-Review 2
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Figma Context MCP safe?

Figma Context MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Figma Context MCP publish package provenance?
No published build provenance is currently detected for Figma Context MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Figma Context MCP have an OpenSSF Scorecard?
Figma Context MCP has an OpenSSF Scorecard score of 4.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Figma Context MCP actively maintained?
Maintained. Last push was 8 days ago.
What license does Figma Context MCP use?
Figma Context MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Figma Context MCP's commits signed?
82% of the last 100 commits to Figma Context MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
high confidence
Implemented
Figma Context MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Figma Context MCP?

For maintainers

HVTrust scores Figma Context MCP 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
Rank 13HVTrust 2Listed 1Grade 1Scorecard 1Score 1
2026-08-15
Rank Moved
Rank rose 15 spots (#410 → #395)
2026-08-13
Rank Moved
Rank dropped 16 spots (#393 → #409)
2026-08-12
Rank Moved
Rank rose 12 spots (#405 → #393)
2026-08-10
Rank Moved
Rank dropped 18 spots (#386 → #404)
2026-08-08
Rank Moved
Rank dropped 93 spots (#290 → #383)
2026-07-24
Rank Moved
Rank dropped 10 spots (#263 → #273)
2026-07-18
Rank Moved
Rank dropped 47 spots (#212 → #259)
2026-07-18
HVTrust Changed
HVTrust down 3.6pts (59.2 → 55.6)
2026-07-18
Activity Score Changed
Activity score down 11pts (77 → 66)
2026-07-15
Rank Moved
Rank dropped 10 spots (#198 → #208)
2026-07-14
Rank Moved
Rank dropped 15 spots (#183 → #198)
2026-07-13
Rank Moved
Rank dropped 24 spots (#159 → #183)
2026-06-24
Rank Moved
Rank dropped 13 spots (#161 → #174)
2026-06-22
Scorecard Added
OSSF Scorecard: 4.4/10
2026-06-22
Grade Changed
Trust grade D → C
2026-06-22
Rank Moved
Rank rose 101 spots (#257 → #156)
2026-06-22
HVTrust Changed
HVTrust up 34.4pts (25.4 → 59.8)
2026-06-21
Rank Moved
Rank dropped 15 spots (#242 → #257)
2026-06-20
Newly Listed
First tracked at rank #242

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 55.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/figma-context-mcp.svg)](https://hvtracker.net/agents/figma-context-mcp)
HTML:
<a href="https://hvtracker.net/agents/figma-context-mcp"><img src="https://hvtracker.net/badge/figma-context-mcp.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON