IsPixelWorking MCP server
com.ispixelworking/pixel-checkispixelworking.comstreamable-httpv1.1.0Scanned
Check a page's Meta, TikTok and OpenAI pixels, read reports and step-by-step fix guides.
4 tools: 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the IsPixelWorking MCP server can do
The IsPixelWorking MCP server is published by ispixelworking.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: check_page), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (check_page and get_report); 1 tool can send data out of your system (check_page).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
check_pageCheck 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, th…Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 3Show 3 read-only tools
get_fix_guideStep-by-step guide (Markdown) for fixing a problem the check found, for the site's platform when one exists (otherwise the general version).No findings
Why it is in this group
- The name "get_fix_guide" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_reportRead 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 explan…Reads text others writeNo findings
Why it is in this group
- The name "get_report" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "read" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_findingsEvery problem (finding) the check can report, with id, severity, title, explanation and whether a fix guide exists.No findings
Why it is in this group
- The name "list_findings" says "list": a word for reading.
Description, as the server wrote it Every problem (finding) the check can report, with id, severity, title, explanation and whether a fix guide exists.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ispixelworking.com/mcp: tools/list returned 4 tools to an anonymous client, including check_page (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:get_fix_guideOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:check_pageChanges thingstitledescription
- Changed:get_reportOnly readsdescription
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http pixel-check https://ispixelworking.com/mcpclaude mcp add --transport http pixel-check https://ispixelworking.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pixel-check__get_report",
"mcp__pixel-check__get_fix_guide",
"mcp__pixel-check__list_findings"
],
"ask": [
"mcp__pixel-check__check_page"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pixel-check. Review it before you use it.
Capability tags behind 2 rules
- mcp__pixel-check__check_page untrusted-input, outbound
- mcp__pixel-check__get_report untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.ispixelworking/pixel-check/verify?hash=1caacad698af9632299a18ed30bbcdfb69c03700e0435c3613776df7f306cedf" | jq -e '.changed == false'Pinned hash 1caacad698af, from Nov 8, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.ispixelworking/pixel-check/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.ispixelworking/pixel-check)Source: MCP Registry. Synced Oct 23, 2026, 07:17 UTC.
IsPixelWorking MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the IsPixelWorking MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the IsPixelWorking MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the IsPixelWorking MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the IsPixelWorking MCP server have?
- 4 tools: 1 write, 3 read. check_page, get_report, get_fix_guide and list_findings.
Does the IsPixelWorking MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the IsPixelWorking MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_page.
Has the IsPixelWorking MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.