io.github.sunhome243/figma-mcp-express

The materials explicitly state that no keys or environment variables are required, and no API key, OAuth token, or other sensitive credential is mentioned; based on the available facts, credential exposure risk appears low.

The materials list no remote endpoint host, and the description emphasizes a 'local plugin bridge', with no evidence that user data is sent to a third-party remote service. Actual network behavior should still be verified through source review and runtime monitoring, but no clear egress red flag is present in the provided materials.

The system checks explicitly mark this tool as executes-code, meaning it runs local processes/code as part of its MCP functionality. This is a normal capability for such tools and does not by itself justify a high-risk rating, but it does create a local execution surface that warrants caution.

The description indicates it works through a local Figma plugin bridge, which typically means it may access design data involved in that bridge workflow; however, the missing README does not clearly document what local files, caches, or Figma resources it can read or write. There is no evidence of over-privileged access beyond its stated purpose, but the data boundary is insufficiently documented.

Positive factors include distribution via an official registry, open-source availability, and updates within the last year, all of which materially reduce supply-chain risk. However, the repository has no declared license, very low community adoption (0 stars), and missing documentation, which limits confidence in maturity and auditability; this supports a caution rating rather than high risk.