Figmind MCP Server

figmind npm v1.0.0

Published by guhcostan — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Connect Cursor AI to Figma via MCP (Model Context Protocol) — read and modify designs in real time

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([get_pages, set_current_page]) co-exist with external-action tools ([create_comment]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [get_pages, set_current_page] → sinks [create_comment]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow get_pages → create_comment

Tools 55

Each tool and what it can reach — statically extracted from the published source.

  • create_commentnetwork egress
  • get_pagesingests untrusted input
  • set_current_pageingests untrusted input
  • add_variable_modeno sensitive capability
  • apply_styleno sensitive capability
  • apply_variable_to_nodeno sensitive capability
  • bulk_updateno sensitive capability
  • create_component_instanceno sensitive capability
  • create_frameno sensitive capability
  • create_from_htmlno sensitive capability
Show 45 more tools ↓
  • create_from_svgno sensitive capability
  • create_pageno sensitive capability
  • create_sectionno sensitive capability
  • create_shapeno sensitive capability
  • create_textno sensitive capability
  • create_variableno sensitive capability
  • create_variable_collectionno sensitive capability
  • delete_nodesno sensitive capability
  • delete_variableno sensitive capability
  • delete_variable_collectionno sensitive capability
  • detach_instanceno sensitive capability
  • duplicate_nodeno sensitive capability
  • executeno sensitive capability
  • export_batchno sensitive capability
  • export_nodeno sensitive capability
  • export_pageno sensitive capability
  • find_component_setsno sensitive capability
  • find_componentsno sensitive capability
  • find_components_in_pageno sensitive capability
  • find_nodesno sensitive capability
  • get_commentsno sensitive capability
  • get_component_propertiesno sensitive capability
  • get_design_system_kitno sensitive capability
  • get_file_contextno sensitive capability
  • get_file_infono sensitive capability
  • get_file_nodesno sensitive capability
  • get_file_variablesno sensitive capability
  • get_full_treeno sensitive capability
  • get_linked_library_tokensno sensitive capability
  • get_nodeno sensitive capability
  • get_selectionno sensitive capability
  • get_used_fontsno sensitive capability
  • move_nodeno sensitive capability
  • rename_variable_modeno sensitive capability
  • save_versionno sensitive capability
  • scroll_into_viewno sensitive capability
  • set_effectsno sensitive capability
  • set_fillno sensitive capability
  • set_image_fillno sensitive capability
  • set_instance_propertiesno sensitive capability
  • set_reactionsno sensitive capability
  • set_text_propertiesno sensitive capability
  • swap_componentno sensitive capability
  • update_auto_layoutno sensitive capability
  • update_variableno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 96/100 1 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/figmind/badge.svg)](https://mcptrustchecker.com/registry/figmind)
HTML
<a href="https://mcptrustchecker.com/registry/figmind"><img src="https://mcptrustchecker.com/registry/figmind/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/figmind/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan figmind --online

Use the free API → How scoring works

More in AI & Agents