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.felixAnhalt/Figma-Context-MCP

NPM · @TMEGIT/FIGMA-DEVELOPER-MCP · SCANNED SEP 20

LLM-optimized Figma MCP server.

0 this week 39 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects sharp 0.34.5, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 44 of 177 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
  • Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to felixAnhalt/Figma-Context-MCP). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 184 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the io.github.felixAnhalt/Figma-Context-MCP server?

io.github.felixAnhalt/Figma-Context-MCP runs locally as an npm package, launched with npx -y @tmegit/figma-developer-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 · @tmegit/figma-developer-mcp

# add to Claude Code
claude mcp add felixanhalt-figma-context-mcp -- npx -y @tmegit/figma-developer-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "felixanhalt-figma-context-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tmegit/figma-developer-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "felixanhalt-figma-context-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tmegit/figma-developer-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add felixanhalt-figma-context-mcp -- npx -y @tmegit/figma-developer-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "felixanhalt-figma-context-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@tmegit/figma-developer-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add felixanhalt-figma-context-mcp --command npx --arg -y --arg @tmegit/figma-developer-mcp
# ~/.hermes/config.yaml
mcp_servers:
  felixanhalt-figma-context-mcp:
    command: "npx"
    args: ["-y", "@tmegit/figma-developer-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "felixanhalt-figma-context-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@tmegit/figma-developer-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add felixanhalt-figma-context-mcp -t stdio -c npx -a -y @tmegit/figma-developer-mcp
// mcp.json
{
  "mcpServers": {
    "felixanhalt-figma-context-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tmegit/figma-developer-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.

  • 15 Sept 26 0
    • CVE-2026-82562 no longer affects this package security
    • CVE-2026-82417 no longer affects this package security
  • 9 Sept 26 0
    • GHSA-rgj7-g3m4-5g8c affects this package: high security
    • Security disclosure: unverified → fail functional
  • 8 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 3 Sept 26 0
    • CVE-2026-82562 affects this package: high security
    • CVE-2026-82417 affects this package: high security
  • 29 Aug 26 0
    • Security disclosure: unverified → fail functional
  • 28 Aug 26 0
    • Security disclosure: fail → unverified functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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/@tmegit/figma-developer-mcp@0.13.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 felixAnhalt/Figma-Context-MCP
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/felixAnhalt/Figma-Context-MCP/.github/workflows/release.yml@refs/heads/main
Rekor log index 1075981638
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:e54a37759190d8aaf83bc118f33ced0627fc6b1d0feb2b1b7656985126adc58fd313d5cbd720b2e55d82489a0a857dd6e4c9a20e5fe0d298cf5dc378e

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-f88m-g3jw-g9cj high yes
GHSA-rgj7-g3m4-5g8c high yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 177 packages
Packages resolved 177
Stale 44
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the io.github.felixAnhalt/Figma-Context-MCP server?

io.github.felixAnhalt/Figma-Context-MCP is listed in the public MCP registry as io.github.felixAnhalt/Figma-Context-MCP. LLM-optimized Figma MCP server. This page covers its npm package (@tmegit/figma-developer-mcp).

Is the io.github.felixAnhalt/Figma-Context-MCP server safe to use?

io.github.felixAnhalt/Figma-Context-MCP scores 39 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.

Is the io.github.felixAnhalt/Figma-Context-MCP server still maintained?

io.github.felixAnhalt/Figma-Context-MCP 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.felixAnhalt/Figma-Context-MCP server under?

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