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.

pixelpact

NPM · PIXELPACT-MCP · SCANNED SEP 20

Extract a visual contract from a reference page and measure an implementation against it

Available components

npm · pixelpact-mcp 87
+7 this week 87 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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to jamalkamaladdin/pixelpact). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1056 tokens (~264/item across 4 items; 4 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 Management47
  • Stability observed for 14 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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 pixelpact MCP server?

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

npm · pixelpact-mcp

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +4
    • Stability: unverified → 0.27 ▲ functional
  • 7 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 6 Sept 26 65

    First indexed and scored.

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/pixelpact-mcp@0.1.6

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo jamalkamaladdin/pixelpact
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/jamalkamaladdin/pixelpact/.github/workflows/release.yml@refs/heads/main
Rekor log index 2738407797
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:2f075194e5ea5ccaa0a320377dc76c9df6a2be52ceb0e1884a1112a3acd7d7b0e3a9646ab0fcf413149f9e8d2d340f70d2fd2ec2388ba037f7996c287

Background: How many MCP packages publish verified provenance →

Dependencies 98 packages
Packages resolved 98
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,056 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
check_implementation ~291

Measures an implementation URL against a previously saved visual contract: box position and size, computed styles, hover and focus states, and pseudo-elements. Call this after building or changing a UI to verify it matches the reference without a human looking at it. Needs contractPath from a prior extract_contract call. Returns a formatted deviation table (capped at 40 rows, with a note on how many were left out) plus the numeric totals, the pass rate, any missing selectors, and ok, which is true only when nothing deviated and nothing is missing.

NameTypeReqDescription
contractPathstringyesPath to a contract JSON file previously written by extract_contract.
headlessboolean–Run the browser headless. Defaults to true.
maxStatesinteger–Maximum interactive elements to probe. Defaults to 120.
selectorstring–CSS selector to scope the check to. Defaults to the contract root.
timeoutinteger–Navigation timeout in milliseconds. Defaults to 30000.
tolerancenumber–Allowed pixel tolerance for box and length values. Defaults to 1.
urlstringyesThe implementation URL to measure against the contract.
viewportstring–Viewport name to check, for example desktop. Defaults to the first viewport in the contract.
waitinteger–Extra settle time in milliseconds after navigation. Defaults to 2000.

No output schema declared.

No examples provided.

diff_pixels ~289

Renders the implementation URL and compares it pixel by pixel against the reference screenshot stored in the contract. Use this for a stricter visual check than check_implementation, after the structural check passes or when a subtle rendering difference is suspected. Requires the contract to have been extracted with screenshotDir set. Returns the percentage of differing pixels, the threshold it was compared against, ok, and the filesystem path of the generated diff image.

NameTypeReqDescription
contractPathstringyesPath to a contract JSON file previously written by extract_contract.
headlessboolean–Run the browser headless. Defaults to true.
masksarray–CSS selectors to blank out before comparing, for example ads or timestamps.
outDirstring–Directory to write the diff image to. Defaults to the OS temp directory.
selectorstring–CSS selector to scope the comparison to. Defaults to the contract root.
thresholdnumber–Allowed percent of differing pixels before the comparison fails. Defaults to 0.5.
timeoutinteger–Navigation timeout in milliseconds. Defaults to 30000.
urlstringyesThe implementation URL to capture and compare pixel by pixel.
viewportstring–Viewport name to compare. Defaults to the first viewport in the contract.
waitinteger–Extra settle time in milliseconds after navigation. Defaults to 2000.

No output schema declared.

No examples provided.

extract_contract ~367

Extracts a visual contract from a reference URL and saves it as JSON at outputPath. Call this once per reference design, before check_implementation or diff_pixels can be used, since both need a saved contract to compare against. Pass screenshotDir to also capture reference screenshots, which diff_pixels requires later. Returns a summary: the element count per viewport, any extraction warnings, and the path the contract was written to.

NameTypeReqDescription
freezeAnimationsboolean–Freeze CSS animations before measuring. Defaults to true.
fullPageboolean–Capture the full scrollable page instead of only the viewport. Defaults to true.
headlessboolean–Run the browser headless. Defaults to true.
masksarray–CSS selectors to exclude from the walk, for example ads or timestamps.
maxElementsinteger–Maximum elements to walk, 0 means unbounded. Defaults to 600.
maxStatesinteger–Maximum interactive elements to probe for hover and focus. Defaults to 120.
outputPathstringyesFilesystem path to write the contract JSON to, for example ./contracts/home.json.
screenshotDirstring–Directory to save reference screenshots to. Required later for diff_pixels to work.
selectorstring–CSS selector to scope the walk to. Defaults to the document body.
timeoutinteger–Navigation timeout in milliseconds. Defaults to 30000.
urlstringyesThe reference URL to extract a visual contract from.
viewportsarray–Viewports to capture. Defaults to desktop 1440x900, tablet 768x1024, mobile 390x844.
waitinteger–Extra settle time in milliseconds after navigation. Defaults to 2000.

No output schema declared.

No examples provided.

read_contract_summary ~109

Reads a saved contract file and describes it without opening a browser or making any network request. Use this to inspect what a contract covers, for example before deciding whether diff_pixels is possible, since that needs screenshots to already exist. Returns the original source URL, when it was extracted, the viewports it covers, the element count per viewport, whether reference screenshots exist, and any warnings recorded at extraction time.

NameTypeReqDescription
contractPathstringyesPath to a contract JSON file previously written by extract_contract.

No output schema declared.

No examples provided.

Common questions

What is the pixelpact MCP server?

pixelpact is an MCP server listed in the public MCP registry as io.github.jamalkamaladdin/pixelpact. Extract a visual contract from a reference page and measure an implementation against it. This page covers its npm package (pixelpact-mcp).

Is the pixelpact MCP server safe to use?

pixelpact scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 pixelpact MCP server expose?

pixelpact exposes 4 tools: extract_contract, check_implementation, diff_pixels, read_contract_summary. Their descriptions and schemas cost roughly 1,056 tokens of context every time the server is loaded.

Is the pixelpact MCP server still maintained?

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

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