Twelvetake Gimp Studio MCP Server

twelvetake-gimp-studio-mcp PyPI v0.3.2

Published by twelvetake-studios — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A GIMP 3.x MCP server with structured returns, a compat layer, safety checkpoints, and print/DTF tooling.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 5

high Tool "gimp_exec" exposes command/code executionMTC-CAP-001

Tool "gimp_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool gimp_exec

high Shell/command execution in server code (src/gimp_mcp/bridge/client.py)MTC-SRC-002

In the server's implementation (`src/gimp_mcp/bridge/client.py:126`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: op=P.OP_INFO)) def exec(self, code: str, *, args=None, image=None, undo_group: bool = True, timeout: f

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/gimp_mcp/bridge/client.py

high Shell/command execution in server code (src/gimp_mcp/bridge/gimp_side.py)MTC-SRC-002

In the server's implementation (`src/gimp_mcp/bridge/gimp_side.py:134`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rebinds it, because exec() makes this dict the __globals__ of every function the agent defines and rebinding wou

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/gimp_mcp/bridge/gimp_side.py

high Shell/command execution in server code (src/gimp_mcp/bridge/launcher.py)MTC-SRC-002

In the server's implementation (`src/gimp_mcp/bridge/launcher.py:132`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: _var, None) proc = subprocess.Popen( [exe], env=env, stdin=subprocess.DEVNULL, # never in

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/gimp_mcp/bridge/launcher.py

low Mutating tool "gimp_exec" declares no destructiveHintMTC-CAP-005

Tool "gimp_exec" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool gimp_exec

Tools 119

Each tool and what it can reach — statically extracted from the published source.

  • gimp_execruns code / shell
  • add_alphano sensitive capability
  • add_maskno sensitive capability
  • apply_filterno sensitive capability
  • apply_maskno sensitive capability
  • assign_profileno sensitive capability
  • bleed_and_safeno sensitive capability
  • brightness_contrastno sensitive capability
  • bucket_fillno sensitive capability
  • check_fontsno sensitive capability
Show 109 more tools ↓
  • checkpointno sensitive capability
  • clean_for_dtfno sensitive capability
  • color_atno sensitive capability
  • color_balanceno sensitive capability
  • color_to_alphano sensitive capability
  • convert_profileno sensitive capability
  • create_layerno sensitive capability
  • create_text_layerno sensitive capability
  • curvesno sensitive capability
  • cutout_colorno sensitive capability
  • delete_layerno sensitive capability
  • desaturateno sensitive capability
  • describe_opno sensitive capability
  • despillno sensitive capability
  • drop_shadowno sensitive capability
  • duplicate_layerno sensitive capability
  • edge_chokeno sensitive capability
  • edge_spreadno sensitive capability
  • export_dtf_pngno sensitive capability
  • export_imageno sensitive capability
  • fillno sensitive capability
  • flattenno sensitive capability
  • foreground_selectno sensitive capability
  • fuzzy_selectno sensitive capability
  • gang_sheetno sensitive capability
  • gaussian_blurno sensitive capability
  • get_bitmapno sensitive capability
  • get_metadatano sensitive capability
  • get_profileno sensitive capability
  • gradientno sensitive capability
  • group_addno sensitive capability
  • group_createno sensitive capability
  • group_ungroupno sensitive capability
  • halftone_separationno sensitive capability
  • histogramno sensitive capability
  • hue_saturationno sensitive capability
  • invertno sensitive capability
  • knockout_backgroundno sensitive capability
  • layer_from_fileno sensitive capability
  • levelsno sensitive capability
  • list_brushesno sensitive capability
  • list_checkpointsno sensitive capability
  • list_fontsno sensitive capability
  • list_gegl_opsno sensitive capability
  • list_gradientsno sensitive capability
  • list_imagesno sensitive capability
  • list_palettesno sensitive capability
  • list_patternsno sensitive capability
  • list_proceduresno sensitive capability
  • list_profilesno sensitive capability
  • list_shirt_presetsno sensitive capability
  • lock_alphano sensitive capability
  • luminance_to_alphano sensitive capability
  • merge_downno sensitive capability
  • move_layerno sensitive capability
  • new_imageno sensitive capability
  • normalizeno sensitive capability
  • offset_contentno sensitive capability
  • offset_layerno sensitive capability
  • open_imageno sensitive capability
  • outline_textno sensitive capability
  • paintbrushno sensitive capability
  • pencilno sensitive capability
  • posterizeno sensitive capability
  • print_geometryno sensitive capability
  • read_regionno sensitive capability
  • redono sensitive capability
  • remove_maskno sensitive capability
  • rename_layerno sensitive capability
  • reorder_layerno sensitive capability
  • reset_namespaceno sensitive capability
  • restoreno sensitive capability
  • seam_checkno sensitive capability
  • select_allno sensitive capability
  • select_borderno sensitive capability
  • select_by_colorno sensitive capability
  • select_ellipseno sensitive capability
  • select_featherno sensitive capability
  • select_from_alphano sensitive capability
  • select_from_pathno sensitive capability
  • select_growno sensitive capability
  • select_invertno sensitive capability
  • select_noneno sensitive capability
  • select_rectno sensitive capability
  • select_shrinkno sensitive capability
  • selection_to_channelno sensitive capability
  • set_active_imageno sensitive capability
  • set_bgno sensitive capability
  • set_blend_modeno sensitive capability
  • set_brushno sensitive capability
  • set_fgno sensitive capability
  • set_opacityno sensitive capability
  • set_paint_opacityno sensitive capability
  • set_text_propsno sensitive capability
  • set_visibleno sensitive capability
  • soft_proofno sensitive capability
  • statusno sensitive capability
  • stroke_selectionno sensitive capability
  • substitute_fontno sensitive capability
  • thresholdno sensitive capability
  • threshold_alphano sensitive capability
  • to_grayscaleno sensitive capability
  • to_rgbno sensitive capability
  • trim_to_contentno sensitive capability
  • undono sensitive capability
  • undo_group_beginno sensitive capability
  • undo_group_endno sensitive capability
  • unsharp_maskno sensitive capability
  • white_underbaseno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.2 latest A 93/100 5 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/twelvetake-gimp-studio-mcp/badge.svg)](https://mcptrustchecker.com/registry/twelvetake-gimp-studio-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/twelvetake-gimp-studio-mcp"><img src="https://mcptrustchecker.com/registry/twelvetake-gimp-studio-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/twelvetake-gimp-studio-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan twelvetake-gimp-studio-mcp --online --registry pypi

Use the free API → How scoring works

More in Design & Media