TalkToFigma MCP

TalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate

MCP Servers JavaScript Grade D Listed MIT
43.7/100
Rank #954 of 1320
Compare TalkToFigma MCP

Thin or incomplete trust evidence. Review carefully before production use.

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

Is TalkToFigma MCP safe? TalkToFigma MCP scores 43.7/100 (Grade D), ranked #954 of 1320 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 1.6/10; 16% of recent commits are signed; last pushed 2026-07-26. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 18 spots (#936 → #954)
2026-09-03
Scorecard Added
OSSF Scorecard: 1.6/10
2026-09-03
Rank Moved
Rank rose 323 spots (#1259 → #936)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.6/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 40 days ago. Fresh activity helps separate stable projects from stale ones.
55.9
Activity sub-score · out of 100
#523

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 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-09-04 14:33 UTC · Repo last pushed 40 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
7.0k
Forks
772
Last Push
2026-07-26
40 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
69
Rank Change
▼18
was #936

Analysis

HVTrust Dimensions vs MCP Servers

43.7 / 100 · 100.0% confidence

TalkToFigma MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.8 / 25
6.7 below avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
9.9 / 17
1.9 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
9.3 / 20
2.9 below avg 12.2
AdoptionLog-scaled stars · package downloads
9.2 / 20
3.0 above avg 6.2

Activity Inputs

55.9 / 100
StarsRepository reach
23.1 / 30
FreshnessLast push recency
19.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.4 / 20

Supply Chain Trust

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

Is TalkToFigma MCP safe?

Public trust evidence for TalkToFigma MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does TalkToFigma MCP publish package provenance?
No published build provenance is currently detected for TalkToFigma 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 TalkToFigma MCP have an OpenSSF Scorecard?
TalkToFigma MCP has an OpenSSF Scorecard score of 1.6/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 TalkToFigma MCP actively maintained?
Slowing down. Last push was 40 days ago — keep an eye on whether activity resumes.
What license does TalkToFigma MCP use?
TalkToFigma MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are TalkToFigma MCP's commits signed?
16% of the last 100 commits to TalkToFigma 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
TalkToFigma MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 TalkToFigma MCP?

For maintainers

HVTrust scores TalkToFigma 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 15Listed 1HVTrust 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 18 spots (#936 → #954)
2026-09-03
Scorecard Added
OSSF Scorecard: 1.6/10
2026-09-03
Rank Moved
Rank rose 323 spots (#1259 → #936)
2026-09-03
HVTrust Changed
HVTrust up 22.7pts (21.1 → 43.8)
2026-09-02
Rank Moved
Rank dropped 26 spots (#1233 → #1259)
2026-09-01
Rank Moved
Rank dropped 23 spots (#1210 → #1233)
2026-08-31
Rank Moved
Rank dropped 24 spots (#1186 → #1210)
2026-08-30
Rank Moved
Rank dropped 26 spots (#1160 → #1186)
2026-08-29
Rank Moved
Rank dropped 30 spots (#1130 → #1160)
2026-08-28
Rank Moved
Rank dropped 25 spots (#1105 → #1130)
2026-08-27
Rank Moved
Rank dropped 16 spots (#1089 → #1105)
2026-08-26
Rank Moved
Rank dropped 67 spots (#1022 → #1089)
2026-08-25
Rank Moved
Rank dropped 42 spots (#980 → #1022)
2026-08-24
Rank Moved
Rank dropped 13 spots (#967 → #980)
2026-08-22
Rank Moved
Rank rose 12 spots (#979 → #967)
2026-08-16
Rank Moved
Rank dropped 26 spots (#951 → #977)
2026-08-13
Rank Moved
Rank dropped 13 spots (#939 → #952)
2026-08-10
Newly Listed
First tracked at rank #940

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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