io.github.CloudCorpRecords/pixelgrade
OCI · GHCR.IO/CLOUDCORPRECORDS/PIXELGRADE · 2 COMPONENTS
Check a page's Meta, TikTok and OpenAI pixels: grades, findings, reports and fix guides.
Available components
Last scanned (18 hours ago)
Scores higher than 45% of OCI servers
Category Marketing and SEO
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. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 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 4 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 39
First indexed and scored.
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 21 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/pixelgrade@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 io.github.CloudCorpRecords/pixelgrade MCP server?
io.github.CloudCorpRecords/pixelgrade runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/pixelgrade:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/pixelgrade
claude mcp add cloudcorprecords-pixelgrade -- docker run --rm -i ghcr.io/cloudcorprecords/pixelgrade:0.1.0 mcp
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 container image (ghcr.io/cloudcorprecords/pixelgrade).
Is the io.github.CloudCorpRecords/pixelgrade MCP server safe to use?
io.github.CloudCorpRecords/pixelgrade scores 44 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 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 12 checks on io.github.CloudCorpRecords/pixelgrade, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/pixelgrade: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.