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.

com.pulsemcp/image-diff

NPM · @PULSEMCP/IMAGE-DIFF-MCP-SERVER · SCANNED SEP 20

MCP server for programmatic image comparison and visual diff generation.

Available components

npm · @pulsemcp/image-diff-mcp-server 76
0 this week 76 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.33.5, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 32 of 127 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 564 tokens (~564/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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 com.pulsemcp/image-diff MCP server?

com.pulsemcp/image-diff runs locally as an npm package, launched with npx -y @pulsemcp/image-diff-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pulsemcp/image-diff-mcp-server

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

  • 17 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 11 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.

  • 10 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 9 Sept 26 0
    • GHSA-rgj7-g3m4-5g8c affects this package: high ▼ security
    • Stability: 0.97 → pass security
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/@pulsemcp/image-diff-mcp-server@0.1.3

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 127 packages
Packages resolved 127
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~564 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
get_diff_of_images ~564

Compare two images pixel-by-pixel and identify visual differences. Returns structured diff data including: - Overall diff percentage and pixel counts - Clusters of different regions with bounding box coordinates (x, y, width, height) - Severity rating per cluster (trivial/minor/moderate/major) - Clustering metadata with the gap used and suggestions for tuning - File paths to generated heatmap images showing diff intensity **Clustering**: By default, nearby diff regions are automatically grouped using a natural-breaks algorithm that finds the optimal merge distance. This produces a manageable number of clusters where each represents a distinct problem area. To override, set cluster_gap explicitly (0 = no merging, or a specific pixel distance). **Heatmap output**: A PNG image where diff regions are colored from yellow (subtle difference) to red (major difference). A composite version overlays this on the source image for easy comparison. **Use cases:** - Compare a design mock screenshot against actual UI implementation - Compare a Figma mock of a single component against a full-page screenshot (auto-aligned) - Detect visual regressions between two versions of a page - Verify CSS/layout changes only affect intended areas **Requirements:** - Images must be accessible as local file paths - Images can have different dimensions — the smaller image is automatically aligned within the larger one using template matching **Note:** Anti-aliased pixels (font smoothing, rounded corners) are excluded by default to reduce false positives. Set include_aa=true to include them.

NameTypeReqDescription
cluster_gapinteger–Maximum pixel distance between cluster bounding boxes to merge them into a single cluster. When omitted, an optimal gap is auto-computed using natural breaks in cluster distances. Set to 0 to disable…
include_aaboolean–Whether to count anti-aliased pixels (font smoothing, rounded corners) as differences. Default false excludes them to reduce noise.
min_cluster_sizeinteger–Minimum number of connected diff pixels to report as a cluster. Filters out isolated pixel noise. Default 4.
source_imagestringyesAbsolute file path to the source/reference image (e.g. the design mock). Supports PNG, JPEG, WebP, TIFF.
target_imagestringyesAbsolute file path to the target/comparison image (e.g. the actual UI screenshot). Supports PNG, JPEG, WebP, TIFF.
thresholdnumber–Color matching sensitivity from 0 to 1. Lower values detect subtler differences. 0.1 is a good default for UI comparison. Use 0.05 for strict comparison or 0.2 for lenient.

No output schema declared.

No examples provided.

Common questions

What is the com.pulsemcp/image-diff MCP server?

com.pulsemcp/image-diff is an MCP server listed in the public MCP registry as com.pulsemcp/image-diff. MCP server for programmatic image comparison and visual diff generation. This page covers its npm package (@pulsemcp/image-diff-mcp-server).

Is the com.pulsemcp/image-diff MCP server safe to use?

com.pulsemcp/image-diff scores 76 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 com.pulsemcp/image-diff MCP server expose?

com.pulsemcp/image-diff exposes 1 tool: get_diff_of_images. Their descriptions and schemas cost roughly 564 tokens of context every time the server is loaded.

Is the com.pulsemcp/image-diff MCP server still maintained?

com.pulsemcp/image-diff 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 com.pulsemcp/image-diff MCP server under?

com.pulsemcp/image-diff declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.