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

Malware flagged

A supply-chain scanner flagged a high-severity malware risk in this package. Treat it as unsafe to install until the finding is cleared. See Supply Chain Security in the trust breakdown.

io.github.xcodethink/pixelcheck

NPM · PIXELCHECK

Real eyes and hands on the web for AI agents. MCP-first. Local-first. Vendor-agnostic.

Available components

npm · pixelcheck 29
0 this week 29 Trust /100

Last scanned (1 hour ago)

Scores higher than 4% of npm servers

Category Browser Automation

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 Security30
  • Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 92 of 331 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to xcodethink/pixelcheck). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 92 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

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.

  • 5 Nov 26 0
    • Dependency health: partial → 0.89 functional
  • 3 Nov 26 0
    • Dependency health: 0.89 → partial functional
  • 28 Oct 26 0
    • CVE-2026-109932 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
  • 24 Oct 26 −3
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
  • 13 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 12 Oct 26 −1
    • CVE-2026-74866 affects this package: high ▼ security
    • Security disclosure: pass → unverified ▼ functional
  • 3 Oct 26 0
    • CVE-2026-19481 affects this package: high ▼ security
  • 2 Oct 26 0
    • Dependency health: partial → 0.88 functional
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 5 Nov 2026 · Analysed npm/pixelcheck@2.1.0

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 xcodethink/pixelcheck
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/xcodethink/pixelcheck/.github/workflows/release.yml@refs/tags/v2.1.0
Rekor log index 2340869542
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:947b419e701bc4152dca5d06d29cdb46e3b3724cb2a1e5b4ebb93aa66051cf535a897b4829003aca1a96367f04bae03381b4be23ffd97461227c3e72d

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall unreviewed node scripts/postinstall.mjs

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 19 findings
ID CVE Severity Vector Fix available
GHSA-gxm5-99cw-xjw9 CVE-2026-74866 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N yes
GHSA-x8mw-p69m-v3mx CVE-2026-19481 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-2m5v-pch6-74hx CVE-2026-109383 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-2mjp-6q6p-2qxm CVE-2026-1525 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-35p6-xmwp-9g52 CVE-2026-6733 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-4992-7rv2-5pvq CVE-2026-1527 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N yes
GHSA-8xcm-r25x-g524 CVE-2026-16728 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-9fm3-97px-rjf6 CVE-2026-109932 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-g8m3-5g58-fq7m CVE-2026-11525 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-g9mf-h72j-4rw9 CVE-2026-22036 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-m8rv-5g2x-5cg5 CVE-2026-15157 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-p88m-4jfj-68fv CVE-2026-9679 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-qrxm-fqhp-jwvm CVE-2026-87018 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-r53p-7pc4-xj5r CVE-2026-18540 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-v3r7-h72x-cjcm CVE-2026-16729 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-v9p9-hfj2-hcw8 CVE-2026-2229 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vrm6-8vpv-qv8q CVE-2026-1526 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vxpw-j846-p89q CVE-2026-12151 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 331 packages
Packages resolved 331
Deprecated 2
Stale 90
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the io.github.xcodethink/pixelcheck MCP server?

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

npm · pixelcheck

# add to Claude Code
claude mcp add xcodethink-pixelcheck -- npx -y pixelcheck
Common questions

What is the io.github.xcodethink/pixelcheck MCP server?

io.github.xcodethink/pixelcheck is an MCP server listed in the public MCP registry as io.github.xcodethink/pixelcheck. Real eyes and hands on the web for AI agents. MCP-first. Local-first. Vendor-agnostic. This page covers its npm package (pixelcheck).

Is the io.github.xcodethink/pixelcheck MCP server safe to use?

io.github.xcodethink/pixelcheck scores 29 out of 100 on VerifyMCP. A supply-chain scanner flagged a possible malware risk on one channel of this server. We recorded 19 known advisories against it as of 5 November 2026. 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.

Is the io.github.xcodethink/pixelcheck MCP server still maintained?

io.github.xcodethink/pixelcheck is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.xcodethink/pixelcheck MCP server under?

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