# pixelpact (npm · pixelpact-mcp)

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

- Trust score: 87/100 (high trust)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `pixelpact-mcp`: 87/100 (this document), [markdown](https://verifymcp.io/servers/jamalkamaladdin-pixelpact/pixelpact-mcp.md), [page](https://verifymcp.io/servers/jamalkamaladdin-pixelpact/pixelpact-mcp)

## Channel facts

- Registry: `npm`
- Package: `pixelpact-mcp`
- Version: `0.1.6`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 32 of 98 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to jamalkamaladdin/pixelpact).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add jamalkamaladdin-pixelpact -- npx -y pixelpact-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "jamalkamaladdin-pixelpact": {
      "command": "npx",
      "args": [
        "-y",
        "pixelpact-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jamalkamaladdin-pixelpact": {
      "command": "npx",
      "args": [
        "-y",
        "pixelpact-mcp"
      ]
    }
  }
}
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jamalkamaladdin-pixelpact --command npx --arg -y --arg pixelpact-mcp
```

### Hermes

```yaml
mcp_servers:
  jamalkamaladdin-pixelpact:
    command: "npx"
    args: ["-y", "pixelpact-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "jamalkamaladdin-pixelpact": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pixelpact-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add jamalkamaladdin-pixelpact -t stdio -c npx -a -y pixelpact-mcp
```

### Other

```json
{
  "mcpServers": {
    "jamalkamaladdin-pixelpact": {
      "command": "npx",
      "args": [
        "-y",
        "pixelpact-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 87, +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.

### 2026-09-18 (score 86, +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.

### 2026-09-16 (score 85, +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.

### 2026-09-14 (score 84, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-06 (score 65)

First indexed and scored.

## MCP tools (4)

### `extract_contract` (~367 tokens)

Extract a visual contract

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.

Input parameters:

- `freezeAnimations` (boolean): Freeze CSS animations before measuring. Defaults to true.
- `fullPage` (boolean): Capture the full scrollable page instead of only the viewport. Defaults to true.
- `headless` (boolean): Run the browser headless. Defaults to true.
- `masks` (array): CSS selectors to exclude from the walk, for example ads or timestamps.
- `maxElements` (integer): Maximum elements to walk, 0 means unbounded. Defaults to 600.
- `maxStates` (integer): Maximum interactive elements to probe for hover and focus. Defaults to 120.
- `outputPath` (string, required): Filesystem path to write the contract JSON to, for example ./contracts/home.json.
- `screenshotDir` (string): Directory to save reference screenshots to. Required later for diff_pixels to work.
- `selector` (string): CSS selector to scope the walk to. Defaults to the document body.
- `timeout` (integer): Navigation timeout in milliseconds. Defaults to 30000.
- `url` (string, required): The reference URL to extract a visual contract from.
- `viewports` (array): Viewports to capture. Defaults to desktop 1440x900, tablet 768x1024, mobile 390x844.
- `wait` (integer): Extra settle time in milliseconds after navigation. Defaults to 2000.

### `check_implementation` (~291 tokens)

Check an implementation against a contract

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.

Input parameters:

- `contractPath` (string, required): Path to a contract JSON file previously written by extract_contract.
- `headless` (boolean): Run the browser headless. Defaults to true.
- `maxStates` (integer): Maximum interactive elements to probe. Defaults to 120.
- `selector` (string): CSS selector to scope the check to. Defaults to the contract root.
- `timeout` (integer): Navigation timeout in milliseconds. Defaults to 30000.
- `tolerance` (number): Allowed pixel tolerance for box and length values. Defaults to 1.
- `url` (string, required): The implementation URL to measure against the contract.
- `viewport` (string): Viewport name to check, for example desktop. Defaults to the first viewport in the contract.
- `wait` (integer): Extra settle time in milliseconds after navigation. Defaults to 2000.

### `diff_pixels` (~289 tokens)

Pixel-diff an implementation against a contract screenshot

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.

Input parameters:

- `contractPath` (string, required): Path to a contract JSON file previously written by extract_contract.
- `headless` (boolean): Run the browser headless. Defaults to true.
- `masks` (array): CSS selectors to blank out before comparing, for example ads or timestamps.
- `outDir` (string): Directory to write the diff image to. Defaults to the OS temp directory.
- `selector` (string): CSS selector to scope the comparison to. Defaults to the contract root.
- `threshold` (number): Allowed percent of differing pixels before the comparison fails. Defaults to 0.5.
- `timeout` (integer): Navigation timeout in milliseconds. Defaults to 30000.
- `url` (string, required): The implementation URL to capture and compare pixel by pixel.
- `viewport` (string): Viewport name to compare. Defaults to the first viewport in the contract.
- `wait` (integer): Extra settle time in milliseconds after navigation. Defaults to 2000.

### `read_contract_summary` (~109 tokens)

Read a saved contract summary

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.

Input parameters:

- `contractPath` (string, required): Path to a contract JSON file previously written by extract_contract.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/jamalkamaladdin-pixelpact/pixelpact-mcp#diagnostics

## Score history

- 2026-09-20: 87
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 85
- 2026-09-16: 85
- 2026-09-15: 84
- 2026-09-14: 84
- 2026-09-13: 80
- 2026-09-12: 80
- 2026-09-11: 80
- 2026-09-10: 80
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 80
- 2026-09-06: 65

## 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.

## Links

- npm package: https://www.npmjs.com/package/pixelpact-mcp
- Socket report: https://socket.dev/npm/package/pixelpact-mcp
- Repository: https://github.com/jamalkamaladdin/pixelpact
- Website: https://pixelpact.dev/
- Changelog RSS feed: https://verifymcp.io/servers/jamalkamaladdin-pixelpact/pixelpact-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/jamalkamaladdin-pixelpact/pixelpact-mcp.json
- HTML version of this page: https://verifymcp.io/servers/jamalkamaladdin-pixelpact/pixelpact-mcp