Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.rudraptpsingh/figbridge

NPM · FIGBRIDGE-MCP · SCANNED SEP 20

Free, local MCP bridge for Figma — HTML, CSS, Tailwind, tokens, agent handoff bundles.

Available components

−1 this week 90 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • A known CVE affects extract-zip, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
  • No install/post-install scripts declared.Pass
  • 56 of 176 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to rudraptpsingh/figbridge). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 101 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6876 tokens (~134/item across 51 items; 51 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_node" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 51 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.rudraptpsingh/figbridge MCP server?

io.github.rudraptpsingh/figbridge runs locally as an npm package, launched with npx -y figbridge-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · figbridge-mcp

# add to Claude Code
claude mcp add rudraptpsingh-figbridge -- npx -y figbridge-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "rudraptpsingh-figbridge": {
      "command": "npx",
      "args": [
        "-y",
        "figbridge-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rudraptpsingh-figbridge": {
      "command": "npx",
      "args": [
        "-y",
        "figbridge-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add rudraptpsingh-figbridge -- npx -y figbridge-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rudraptpsingh-figbridge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "figbridge-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add rudraptpsingh-figbridge --command npx --arg -y --arg figbridge-mcp
# ~/.hermes/config.yaml
mcp_servers:
  rudraptpsingh-figbridge:
    command: "npx"
    args: ["-y", "figbridge-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rudraptpsingh-figbridge": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "figbridge-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add rudraptpsingh-figbridge -t stdio -c npx -a -y figbridge-mcp
// mcp.json
{
  "mcpServers": {
    "rudraptpsingh-figbridge": {
      "command": "npx",
      "args": [
        "-y",
        "figbridge-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 17 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 15 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/figbridge-mcp@0.4.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo rudraptpsingh/figbridge
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/rudraptpsingh/figbridge/.github/workflows/publish.yml@refs/tags/v0.4.0
Rekor log index 1778192314
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:ed204cf68a6fa654752ca28cc651de1d8d272c3624898ab051dfca3cc8f102a00bebf2b8b6c634c0af8a08c9020877723a8f09812fc3601d80c9cbbe6

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-7pqw-9j4j-h8q3 CVE-2026-19693 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H no
GHSA-jmr9-qjv8-65gv CVE-2026-56876 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N no

Background: What a vulnerability scan can and cannot prove →

Dependencies 176 packages
Packages resolved 176
Stale 56
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 51 exposed · ~6,876 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
visual_diff ~171

One-call visual reference: take a live Chrome screenshot of `url` AND export the Figma frame at `nodeId`, write both PNGs to `outDir` (default /tmp), and return their paths. Hand the paths to the Read tool to view side-by-side. Replaces the chrome-devtools-mcp + python-decode + manual-write dance.

NameTypeReqDescription
nodeIdstringyesFigma node id of the imported frame.
outDirstringDirectory to write PNGs into. Default /tmp.
prefixstringFilename prefix. Default 'diff'.
scalenumberFigma export scale. Default 0.5.
urlstringyesLive page URL.
widthnumberChrome viewport width. Default 1280.

No output schema declared.

No examples provided.

Common questions

What is the io.github.rudraptpsingh/figbridge MCP server?

io.github.rudraptpsingh/figbridge is an MCP server listed in the public MCP registry as io.github.rudraptpsingh/figbridge. Free, local MCP bridge for Figma, HTML, CSS, Tailwind, tokens, agent handoff bundles. This page covers its npm package (figbridge-mcp).

Is the io.github.rudraptpsingh/figbridge MCP server safe to use?

io.github.rudraptpsingh/figbridge scores 90 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.rudraptpsingh/figbridge MCP server expose?

io.github.rudraptpsingh/figbridge exposes 51 tools: get_current_selection, get_last_export, list_history, get_tokens, bridge_status, and 46 more. Their descriptions and schemas cost roughly 6,876 tokens of context every time the server is loaded.

Is the io.github.rudraptpsingh/figbridge MCP server still maintained?

io.github.rudraptpsingh/figbridge is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.rudraptpsingh/figbridge MCP server under?

io.github.rudraptpsingh/figbridge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.