UI Design to Code

The material explicitly states that no keys or environment variables are required. No API token, account password, or other sensitive credential is requested, so credential exposure and misuse risk appears low.

No remote endpoint is declared, and the description points to a local design-to-code workflow. Based on the provided material, there is no explicit evidence of user data being sent to third-party services.

The system checks indicate that the tool has code-execution capability. For an MCP tool, this commonly means starting local processes or running a conversion pipeline. The material does not show requests for system privileges beyond its stated design-to-code purpose, so this falls under normal caution rather than a red flag.

From the functional description, the tool may read UI screenshots, Figma node data, and visual review artifacts, and may output code or related artifacts. This implies access to local design and generated files. No obvious overbroad authorization is stated, but it should ideally be confined to project-specific directories.

Positive factors include its official registry source, open-source code, and updates within the last year, all of which reduce supply-chain risk. Remaining concerns are the sparse README/documentation, unspecified license, and currently low community adoption (0 stars), so reviewing the repository code and dependency list is still advisable.