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.

Image Puma

NPM · IMAGE-PUMA · 3 COMPONENTS · SCANNED SEP 20

Plan and run local batch image preparation with explicit confirmation before writing files.

0 this week 75 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
  • 35 of 154 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 298 tokens (~49/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Image Puma MCP server?

Image Puma runs locally as an npm package, launched with npx -y image-puma. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · image-puma

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

  • 19 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 +1
    • Stability: 0.97 → pass security
  • 9 Sept 26 +1
    • GHSA-rgj7-g3m4-5g8c affects this package: high security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

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/image-puma@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

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 154 packages
Packages resolved 154
Stale 35
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~256 tokens

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 →

Tool Tokens
image_puma_describe_preset ~31

Return exact settings for one MCP-available preset.

NameTypeReqDescription
presetIdstringyes
NameTypeReqDescription
builtInbooleanyes
presetobjectyesExact preset settings, matching the settings schema.

No examples provided.

image_puma_generate_favicon ~62

Generate browser favicon assets plus ICO, ICNS, and PNG app icons from one local image.

NameTypeReqDescription
confirmedbooleanyes
folderNamestring
outputDirstringyes
sourcePathstringyes
NameTypeReqDescription
filesarrayyes
outputDirectorystringyes
sourcePathstringyes

No examples provided.

image_puma_list_presets ~22

List MCP-available built-in and user presets.

Input schema present but exposes no named parameters.

NameTypeReqDescription
presetsarrayyes
unavailablePresetsarrayyesPresets the desktop app offers that this MCP server cannot run.

No examples provided.

image_puma_plan ~70

Create a read-only Image Puma batch plan for allowed local image paths.

NameTypeReqDescription
allowOverwriteboolean
customSettingsobject
inputsarrayyes
outputDirstring
presetIdstring
recursiveboolean
NameTypeReqDescription
acceptedFilesarrayyes
effectiveSettingsobjectyesFully resolved preset the run would apply.
errorsarrayyesNon-empty means the plan cannot be run as-is.
expiresAtstringyesISO timestamp after which the plan can no longer be run.
limitsobjectyes
planIdstringyesHandle to pass to image_puma_run after the user confirms.
plannedOutputsarrayyesEvery file the run would write.
requiresConfirmationbooleanyes
skippedFilesarrayyes
warningsarrayyes

No examples provided.

image_puma_run ~44

Run a previously created Image Puma plan after explicit confirmation.

NameTypeReqDescription
acceptWarningsboolean
confirmedbooleanyes
planIdstringyes
NameTypeReqDescription
outputFoldersarrayyesDirectories the run wrote into.
planIdstringyes
resultobjectyesPer-file outcomes plus batch byte and count totals.

No examples provided.

image_puma_settings_schema ~27

Return the JSON Schema for custom Image Puma settings accepted by image_puma_plan.

Input schema present but exposes no named parameters.

NameTypeReqDescription
schemaobjectyesJSON Schema for the customSettings accepted by image_puma_plan.

No examples provided.

Common questions

What is the Image Puma MCP server?

Image Puma is an MCP server listed in the public MCP registry as io.github.panth-net/Image-Puma. Plan and run local batch image preparation with explicit confirmation before writing files. This page covers its npm package (image-puma).

Is the Image Puma MCP server safe to use?

Image Puma scores 75 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. 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.

What tools does the Image Puma MCP server expose?

Image Puma exposes 6 tools: image_puma_plan, image_puma_run, image_puma_list_presets, image_puma_describe_preset, image_puma_settings_schema, image_puma_generate_favicon. Their descriptions and schemas cost roughly 256 tokens of context every time the server is loaded.

Is the Image Puma MCP server still maintained?

Image Puma 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 Image Puma MCP server under?

Image Puma declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.