io.github.jamalkamaladdin/pixelpact

pixelpact

Is the pixelpact MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-31.

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

alive probed 2026-11-14 · unchanged since 2026-10-31

4tools

2.8ktokens in Claude Opus 5.5

1.4 %of Claude's 200k window

1.1×the median server

227 msto initialize

8 msto list tools

Run it: npx -y pixelpact-mcp@0.1.6 (stdio, probed in a container with the network off)
Host: npmjs.com
Reports itself as: pixelpact-mcp 0.1.6
Capabilities: tools
Instructions: none
Of a 1M window: 0.3 % of a 1M context window
Count: 2.8k tokens in Claude Opus 5.5, exact, measured 2026-10-17. With the Claude Code prefix mcp__…__ on each tool name: 2.9k. The o200k_base estimate is 1.6k. Counted again when the tool definitions change. Method.
Repository: https://github.com/jamalkamaladdin/pixelpact
Website: https://pixelpact.dev
Registry: active, updated 2026-09-06 · registry entry

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.81×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
extract_contract	1 060	586	38 %
diff_pixels	752	416	27 %
check_implementation	738	408	26 %
read_contract_summary	266	147	9 %

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention implementation or reference.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.