# IsPixelWorking (remote · ispixelworking.com)

Check a page's Meta, TikTok and OpenAI pixels, read reports and step-by-step fix guides.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ispixelworking.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-ispixelworking-pixel-check/ispixelworking.md), [page](https://verifymcp.io/servers/com-ispixelworking-pixel-check/ispixelworking)

## Channel facts

- Endpoint: `https://ispixelworking.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1107 tokens (~276/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**: 73/100
  - Stability observed for 22 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 5 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 IsPixelWorking MCP server?

IsPixelWorking is a hosted endpoint at https://ispixelworking.com/mcp, so there is nothing to install locally. 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 --transport http com-ispixelworking-pixel-check 'https://ispixelworking.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ispixelworking-pixel-check": {
      "url": "https://ispixelworking.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-ispixelworking-pixel-check": {
      "type": "http",
      "url": "https://ispixelworking.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-ispixelworking-pixel-check]
url = "https://ispixelworking.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ispixelworking-pixel-check": {
      "type": "remote",
      "url": "https://ispixelworking.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-ispixelworking-pixel-check --url 'https://ispixelworking.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ispixelworking-pixel-check:
    url: "https://ispixelworking.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ispixelworking-pixel-check": {
      "Transport": "http",
      "Url": "https://ispixelworking.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ispixelworking-pixel-check -t streamable-http -u 'https://ispixelworking.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-ispixelworking-pixel-check": {
      "type": "http",
      "url": "https://ispixelworking.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-04 (score 81, +1)

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

### 2026-11-02 (score 80, +1)

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

### 2026-10-31 (score 79, +1)

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

### 2026-10-29 (score 78, +1)

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

### 2026-10-27 (score 77, +1)

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

### 2026-10-26 (score 76, −1)

- [security] Tool “get_fix_guide” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 221 → 276

### 2026-10-25 (score 77, +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-10-23 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_page” rewrote its description, which is the text the model reads
- [security] Tool “get_report” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] Tool “check_page” changed its title: Check a page's Meta Pixel → Check a page's ad pixels

## 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: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-ispixelworking-pixel-check/ispixelworking#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 76
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72

## Common questions

### What is the IsPixelWorking MCP server?

IsPixelWorking is an MCP server listed in the public MCP registry as com.ispixelworking/pixel-check. Check a page's Meta, TikTok and OpenAI pixels, read reports and step-by-step fix guides. This page covers its hosted endpoint (https://ispixelworking.com/mcp).

### Is the IsPixelWorking MCP server safe to use?

IsPixelWorking scores 81 out of 100 on VerifyMCP. 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 IsPixelWorking MCP server expose?

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

### Does the IsPixelWorking MCP server require authentication?

No. We connected to IsPixelWorking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the IsPixelWorking MCP server still maintained?

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

## Links

- Remote endpoint: https://ispixelworking.com/mcp
- Website: https://ispixelworking.com/ai-agents
- Changelog RSS feed: https://verifymcp.io/servers/com-ispixelworking-pixel-check/ispixelworking.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ispixelworking-pixel-check/ispixelworking.json
- HTML version of this page: https://verifymcp.io/servers/com-ispixelworking-pixel-check/ispixelworking