# io.github.CloudCorpRecords/pixelgrade (npm · @reneturcios/pixelgrade)

Check a page's Meta, TikTok and OpenAI pixels: grades, findings, reports and fix guides.

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/pixelgrade`: 74/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-pixelgrade/reneturcios-pixelgrade.md), [page](https://verifymcp.io/servers/cloudcorprecords-pixelgrade/reneturcios-pixelgrade)
- oci · `ghcr.io/cloudcorprecords/pixelgrade`: 44/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-pixelgrade/ghcr-io-cloudcorprecords-pixelgrade.md), [page](https://verifymcp.io/servers/cloudcorprecords-pixelgrade/ghcr-io-cloudcorprecords-pixelgrade)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/pixelgrade`
- Version: `0.1.0`
- 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-11-21.

- **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.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 775 tokens (~193/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**: 37/100
  - Stability observed for 11 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 io.github.CloudCorpRecords/pixelgrade MCP server?

io.github.CloudCorpRecords/pixelgrade runs locally as an npm package, launched with npx -y @reneturcios/pixelgrade 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 cloudcorprecords-pixelgrade -- npx -y @reneturcios/pixelgrade mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-pixelgrade": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/pixelgrade",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-pixelgrade": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/pixelgrade",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-pixelgrade -- npx -y @reneturcios/pixelgrade mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-pixelgrade": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/pixelgrade",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-pixelgrade --command npx --arg -y --arg @reneturcios/pixelgrade --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-pixelgrade:
    command: "npx"
    args: ["-y", "@reneturcios/pixelgrade", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-pixelgrade": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/pixelgrade",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-pixelgrade -t stdio -c npx -a -y @reneturcios/pixelgrade mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-pixelgrade": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/pixelgrade",
        "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-11-21 (score 74, +1)

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

### 2026-11-19 (score 73, +1)

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

### 2026-11-17 (score 72, +1)

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

### 2026-11-15 (score 71, +1)

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

### 2026-11-14 (score 70, +2)

- [functional improvement] Stability: unverified → 0.13

### 2026-11-10 (score 68)

First indexed and scored.

## MCP tools (4)

### `check_page` (~219 tokens)

Check a page's ad pixels

Check whether a web page's Meta, TikTok and OpenAI pixels work (the Meta Pixel is the former Facebook Pixel), with a grade for each: cookie consent, duplicate events, event IDs, the ad click IDs (e.g. fbclid -> _fbc) and signs of server-side tracking. A browser in the EU visits the page twice. Reuses a result from the last 24 hours unless recheck is true. Waits for the result up to wait_seconds (a check takes 20 to 60 seconds); if it is still running, call get_report later.

Input parameters:

- `recheck` (boolean): Start a fresh check instead of reusing a recent result (allowed once the last check is an hour old). Use after a fix was deployed.
- `url` (string, required): The page to check, usually the landing page the ads point to, e.g. https://example.com/landing
- `wait_seconds` (integer): How long to wait for the result, 0 to 45 seconds (default 40).

### `get_report` (~99 tokens)

Read a check report

Read the result of a check by its report id or report link (https://ispixelworking.com/r/<id>): status, a grade for each pixel found (Meta, TikTok and OpenAI), problems with explanations and fix guide links, checklist. Reports are kept for 90 days.

Input parameters:

- `report` (string, required): Report id (e.g. Ab3dE5fG7hJ9kL2m) or report link

### `get_fix_guide` (~423 tokens)

Get a step-by-step fix guide

Step-by-step guide (Markdown) for fixing a problem the check found, for the site's platform when one exists (otherwise the general version). With consent_tool, returns the guide for wiring the Meta, TikTok and OpenAI pixels to that consent tool instead. Guides exist for: meta.fires_before_consent, meta.not_firing_after_consent, meta.duplicate_pixel, meta.missing_event_id, meta.fbc_not_set, meta.server_copy_without_event_id, meta.server_event_id_mismatch, tiktok.fires_before_consent, tiktok.not_firing_after_consent, tiktok.event_id_reused, tiktok.duplicate_pixel, tiktok.missing_event_id, tiktok.click_id_not_set, tiktok.mobile_cta_tracking_mismatch, tiktok.multiple_pixels, tiktok.server_copy_without_event_id, tiktok.server_event_id_mismatch, openai.fires_before_consent, openai.not_firing_after_consent, openai.event_id_reused, openai.duplicate_pixel, openai.missing_event_id, openai.click_id_not_set, openai.mobile_cta_tracking_mismatch, openai.multiple_pixels, openai.server_copy_without_event_id, openai.server_event_id_mismatch. Setup guides (pass the id as issue_id): general.server_side_not_detected (setting up the Meta Conversions API), tiktok.events_api_setup (setting up the TikTok Events API), openai.pixel_setup (installing the OpenAI Pixel), openai.conversions_api_setup (setting up the OpenAI Conversions API).

Input parameters:

- `consent_tool` (string): Consent tool guide: complianz (Complianz), cookiebot (Cookiebot), cookieyes (CookieYes), onetrust (OneTrust), usercentrics (Usercentrics)
- `issue_id` (string): Problem id from a report, e.g. meta.fires_before_consent
- `platform` (string): Site platform from the report, e.g. framer, shopify, webflow, wordpress

### `list_findings` (~34 tokens)

List the problems a check can find

Every problem (finding) the check can report, with id, severity, title, explanation and whether a fix guide exists.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-pixelgrade/reneturcios-pixelgrade#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 73
- 2026-11-19: 73
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 70
- 2026-11-13: 68
- 2026-11-12: 68
- 2026-11-11: 68
- 2026-11-10: 68

## Common questions

### What is the io.github.CloudCorpRecords/pixelgrade MCP server?

io.github.CloudCorpRecords/pixelgrade is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/pixelgrade. Check a page's Meta, TikTok and OpenAI pixels: grades, findings, reports and fix guides. This page covers its npm package (@reneturcios/pixelgrade).

### Is the io.github.CloudCorpRecords/pixelgrade MCP server safe to use?

io.github.CloudCorpRecords/pixelgrade scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 io.github.CloudCorpRecords/pixelgrade MCP server expose?

io.github.CloudCorpRecords/pixelgrade exposes 4 tools: check_page, get_report, get_fix_guide, list_findings. Their descriptions and schemas cost roughly 775 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/pixelgrade MCP server still maintained?

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

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

### What did VerifyMCP test on the io.github.CloudCorpRecords/pixelgrade MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/pixelgrade, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/pixelgrade
- Socket report: https://socket.dev/npm/package/@reneturcios/pixelgrade
- Repository: https://github.com/CloudCorpRecords/pixelgrade
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-pixelgrade/reneturcios-pixelgrade.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-pixelgrade/reneturcios-pixelgrade/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-pixelgrade/reneturcios-pixelgrade.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-pixelgrade/reneturcios-pixelgrade
