MCP server · trust report

io.github.tunglt1810/figma-mcp-go

1 check that ran failed — version behavior — so this release can’t be trusted as-is.

Publisher
io.github.tunglt1810
Repository
github.com/tunglt1810/figma-mcp-go
Install
npm:@tunglt1810/figma-mcp-go, npm:@tunglt1810/figma-mcp-go, npm:@tunglt1810/figma-mcp-go, npm:@tunglt1810/figma-mcp-go, npm:@tunglt1810/figma-mcp-go, npm:@tunglt1810/figma-mcp-go, npm:@tunglt1810/figma-mcp-go, npm:@tunglt1810/figma-mcp-go, npm:@tunglt1810/figma-mcp-go
Versions
9
Inspected
4 of 6 checks · 75%
Scored
2026-09-03 · rubric 1.0.0

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

6 checks2 clean2 flagged2 not inspected
  • Injection surface

    warn25% of grade

    Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

    tool "set_reactions" description: off-vendor URL in a description (example.com); capability text should not name where data goes.

  • Supply chain

    pass25% of grade

    Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

    repository linkage verified

  • Credential hygiene

    pass15% of grade

    How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

    No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    unscannable15% of grade

    Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

    No source files, package.json, or pyproject were fetched; cannot infer capability scope.

  • Version behavior

    fail10% of grade

    Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

    vs prior 0.2.0 (minor bump): new tool "apply_style_to_node" appeared; new tool "batch_execute_pipeline" touches a sensitive surface (email/exec/net/fs); new tool "batch_rename_nodes" appeared; new tool "boolean_operation" appeared; new tool "clone_node" appeared; new tool "combine_as_variants" appeared; new tool "create_component" appeared; new tool "create_component_instance" appeared; new tool "create_connector" appeared; new tool "create_node" appeared; new tool "create_style" appeared; new tool "create_text" appeared; new tool "create_vector" appeared; new tool "delete_nodes" touches a sensitive surface (email/exec/net/fs); new tool "delete_style" touches a sensitive surface (email/exec/net/fs); new tool "detach_instance" appeared; new tool "export_frames_to_pdf" touches a sensitive surface (email/exec/net/fs); new tool "export_screenshots" touches a sensitive surface (email/exec/net/fs); new tool "export_tokens" appeared; new tool "find_replace_text" appeared; new tool "flatten_nodes" appeared; new tool "get_annotations" appeared; new tool "get_document" touches a sensitive surface (email/exec/net/fs); new tool "get_fonts" appeared; new tool "get_image_bytes" touches a sensitive surface (email/exec/net/fs); new tool "get_instance_overrides" appeared; new tool "get_local_components" touches a sensitive surface (email/exec/net/fs); new tool "get_metadata" touches a sensitive surface (email/exec/net/fs); new tool "get_nodes_info" touches a sensitive surface (email/exec/net/fs); new tool "get_reactions" touches a sensitive surface (email/exec/net/fs); new tool "get_selection" appeared; new tool "get_styles" appeared; new tool "get_variable_defs" appeared; new tool "get_viewport" appeared; new tool "group_nodes" appeared; new tool "import_image" touches a sensitive surface (email/exec/net/fs); new tool "manage_component_properties" touches a sensitive surface (email/exec/net/fs); new tool "manage_page" touches a sensitive surface (email/exec/net/fs); new tool "manage_plugin_data" touches a sensitive surface (email/exec/net/fs); new tool "manage_variable" touches a sensitive surface (email/exec/net/fs); new tool "outline_stroke" appeared; new tool "reparent_nodes" appeared; new tool "save_version_checkpoint" touches a sensitive surface (email/exec/net/fs); new tool "search_nodes" touches a sensitive surface (email/exec/net/fs); new tool "set_annotations" appeared; new tool "set_auto_layout" appeared; new tool "set_codegen_result" touches a sensitive surface (email/exec/net/fs); new tool "set_effects" touches a sensitive surface (email/exec/net/fs); new tool "set_export_settings" touches a sensitive surface (email/exec/net/fs); new tool "set_instance_overrides" appeared; new tool "set_layout_grids" appeared; new tool "set_node_properties" appeared; new tool "set_paint" appeared; new tool "set_reactions" whose description contains embedded outbound URL; new tool "set_selection" appeared; new tool "set_text" appeared; new tool "set_text_ranges" appeared; new tool "swap_component" appeared; new tool "ungroup_nodes" appeared; new tool "update_paint_style" touches a sensitive surface (email/exec/net/fs).

  • Transport config

    unscannable10% of grade

    Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

    local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.

Version history

Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.

VersionPublishedGradeScoreInspectedChange
v0.3.1 · current2026-08-30 B77.54/6 · 75%±0
v0.2.02026-08-27 B1004/6 · 65%±0
v0.1.12026-08-19 B77.54/6 · 75%±0
v0.1.02026-08-17 B1003/6 · 55%±0
v0.0.62026-07-28 B77.54/6 · 75%±0
v0.0.52026-07-10 B87.53/6 · 65%