com.ispixelworking/pixel-check·Other

IsPixelWorking

Check whether a page's Meta Pixel works, read reports and step-by-step fix guides.

Connect

remote

Terminal

$claude mcp add --transport http pixel-check https://ispixelworking.com/mcp \  --header "Authorization: <authorization>"

Authorizationsecret
Optional: "Bearer ipw_…" with an API key from your IsPixelWorking account, for your plan's limits and monitored pages

Review passed

Reviewed 15m ago.

No findings.

check_page
Check whether a web page's Meta Pixel (Facebook Pixel) works: cookie consent, duplicate events, event IDs, the ad click ID (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.
get_report
Read the result of a check by its report id or report link (https://ispixelworking.com/r/<id>): status, grade, problems with explanations and fix guide links, checklist. Reports are kept for 90 days.
get_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 Pixel 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, and general.server_side_not_detected (setting up the Conversions API).
list_findings
Every problem (finding) the check can report, with id, severity, title, explanation and whether a fix guide exists.