IsPixelWorking
REMOTE · ISPIXELWORKING.COM
Check a page's Meta, TikTok and OpenAI pixels, read reports and step-by-step fix guides.
Available components
Last scanned (2 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 26 Oct 26 −1
- Tool “get_fix_guide” rewrote its description, which is the text the model reads security
- Schema quality: 221 → 276 ▼ functional
- 25 Oct 26 +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.
- 23 Oct 26 +1
- 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 security
- Server version: 1.0.0 → 1.1.0 functional
- Tool “check_page” changed its title: Check a page's Meta Pixel → Check a page's ad pixels cosmetic
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 · Probed https://ispixelworking.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ispixelworking.com | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fd60446bd85e087f0e7272e5c76ac7be |
| SANs: ispixelworking.com, *.ispixelworking.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ispixelworking.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ispixelworking.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com https://static.cloudflareinsights.com; frame-src https://challenges.cloudflare.com; connect-src 'self' https://cloudflareinsights.com; img-src 'self' data:; style-src 'self' 'unsafe-inline'; font-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ispixelworking.com/mcp | Verified | 200 | |
| http (plaintext) | http://ispixelworking.com/mcp | HTTPS enforced | 301 | https://ispixelworking.com/mcp |
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 →
check_page Check a page's ad pixels ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
get_fix_guide Get a step-by-step fix guide ~423
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_report Read a check report ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| report | string | yes | Report id (e.g. Ab3dE5fG7hJ9kL2m) or report link |
No output schema declared.
No examples provided.
list_findings List the problems a check can find ~34
Every problem (finding) the check can report, with id, severity, title, explanation and whether a fix guide exists.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · ispixelworking.com
claude mcp add --transport http com-ispixelworking-pixel-check 'https://ispixelworking.com/mcp'
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.