MCP LightNo account or API keyFree within daily limits

CertScore.ai for Muse

Find out what a website loads before consent, what remains after Reject, and what needs a closer look. Ask Muse, then open the evidence in CertScore.ai.

MuseCertScore.ai MCP LightScore + findings + evidence

Review a launch, investigate tracking, or check a vendor. Get clearly labeled GDPR/ePrivacy and California scores, the findings behind them, and a full report you can return to after a fix.

Results are automated observations of public pages. They are not legal advice, certification, or a compliance determination.

Version 1.0.4 · ZIP · No Python packages to install · Usage limits · Agent-readable guide

Start with the Muse skill

Save the skill once. Then ask Muse to review a site, inspect a finding, or compare a recheck with your baseline. It uses native MCP tools when available and includes a Python helper for other setups.

Download the Muse skill packageZIP

Version 1.0.4 · ZIP · No Python packages to install

  1. Download the ZIP and attach it to a Muse conversation.
  2. Ask Muse to save the contained skill for future website reviews and reuse your existing CertScore.ai connection.
  3. When you're ready, ask for a scan. Saving the skill does not start one.

After attaching the ZIP, ask Muse

Save the attached CertScore.ai skill for future website reviews and read its SKILL.md. Reuse an existing CertScore.ai MCP Light connection if available; otherwise use the included helper. Do not start a scan yet.

When to use CertScore.ai

  • Before launch

    Find consent, tracking, policy and accessibility issues on a public page before you share it widely.

  • After a change

    Keep a baseline, update the banner or tags, then compare a fresh scan from the same location.

  • For a vendor review

    Inspect a vendor's public website and take the evidence into your review.

  • Across client sites

    Review the URLs you choose, with separate reports and a consistent comparison.

Ask Muse

  • “What loads before consent?”
  • “What remains after Reject?”
  • “Compare these two sites.”
  • “Did the banner fix work?”

Ask for your first review

With the skill saved, paste this into Muse. Try the public test page below, or replace it with a website you want to review.

Already use native MCP connectors? Connect directly
MCP

Connect Muse

For Muse setups that support custom MCP connectors, use this prompt. The downloadable skill also includes a helper when native tools are unavailable:

Paste into Muse
Connect CertScore.ai MCP Light at https://mcp.certscore.ai/mcp/light using Streamable HTTP with no authentication. Reuse an existing connection if available. List its tools to verify the connection; do not start a scan until I ask.

If you are an agent that can add MCP servers, use the endpoint above as a remote Streamable HTTP server with no auth headers.

→

Ask for a scan

Use CertScore.ai to review https://ergoveritas.com/test1.html. Give me the top three things to check, their evidence, the labeled scores and coverage, and the full report link. Keep this scan as a baseline.

Try the demos, then use your own URL

These are owned demo pages with deliberately failing privacy and accessibility examples. Their findings and scores change when the pages or assessment policies change; they are not examples of a typical website.

Example reports checked October 26, 2026. Each report preserves its scan date, location and coverage.

After test1, ask Muse

Use CertScore.ai to review https://ergoveritas.com/test2.html from the same location as the test1 baseline. Compare the same review focus briefly, keep coverage limits visible, and link both reports.

For agents: the four-tool workflow
  1. 1

    Start the scan

    certscore_scan_site

    Call certscore_scan_site with the site URL. Declare a purpose when one fits: prelaunch_review, vendor_review, tracking_check, consent_gpc_check, policy_review, recheck.

  2. 2

    Wait for completion

    certscore_get_scan_status

    Poll the returned scan ID only while queued, running or finalizing. Honor retry guidance, wait at least five seconds between polls, and stop at a terminal state.

  3. 3

    Get the report

    certscore_get_scan_bundle

    Retrieve findings with maxBytes=8000. Label EU and California scores and their coverage separately. Preserve truncation notices and the returned report links; use a suggested larger budget or evidence pages if the core cannot fit.

  4. 4

    Check the evidence

    certscore_get_report_evidence_page

    Call certscore_get_report_evidence_page when a finding needs its underlying evidence.

By default, the service reuses a recent result for the same site. Request a fresh scan only when the user asks for one or wants a recheck after a change.

Share the results

Score and date
Label EU (GDPR/ePrivacy) and California (CCPA/CPRA) scores clearly, with their coverage and scan date.
Review focus
Open the EU or California report view using the same scan. Changing the view does not run another visit.
Scan location
Ask for Ireland, Germany, or California when you need a new visit from that location.
Findings and evidence
Show the findings that matter most, with the evidence for each.
Coverage and report link
Say what was captured and what remains unknown. Link the relevant report evidence so you can inspect the findings, tables and available screenshots.
Scan ID
Keep the scan ID as the baseline for a later recheck.

Never present a finding as a legal violation or describe a site as compliant or non-compliant. These are observations for human review.

If a call returns rate_limited, tell the user and stop. Do not retry in a loop.

Get more from the same scan

You do not need another scan to understand the one you already have. Ask a narrower question, or open the full report to inspect the evidence yourself.

Same scan

Inspect the evidence

See the cookies, trackers and timing behind a finding.

“Show me the cookies and trackers found on this page. Use the existing scan and keep it brief.”

Same scan

Hand it to a developer

Turn the priority findings into a practical checklist.

“Give me the top three fixes, with the evidence and a way to verify each. Use this scan.”

Same scan

Switch report focus

Read the same visit through EU or California topics.

“Show the EU and California scores with their coverage and a link to each report view. Do not scan again.”

Use CertScore.ai after the first scan

Recheck after changes

Keep the first scan as a baseline. After you change the site, ask Muse for a fresh scan and compare the results.

  1. 1Scan

    Keep the baseline scan ID.

  2. 2Make changes

    Update the site, banner, tags, or policy.

  3. 3Recheck

    Request a fresh scan with purpose recheck.

  4. 4Compare

    Review changed findings and their evidence.

  1. Keep the scan ID from the first scan.
  2. After the site changes, run a fresh scan with purpose recheck from the same location.
  3. Compare the same review focus and equivalent coverage against the baseline scan ID.
  4. Report what changed. A finding missing from a later scan is a change to note, not proof of a fix; say so.

When the fix is live, ask Muse

The banner fix is live. Run a fresh CertScore.ai scan of the same URL from the baseline location. Compare the same review focus in a short table, explain the main evidence changes and coverage limits, and link both reports.

When to scan again

Before launch
Scan a public staging or production URL before a launch or redesign.
After consent changes
Rescan when the banner, CMP, or tag setup changes.
New vendors
Review a vendor or partner's site before signing.
Periodic checks
With the user's approval, repeat a scan and compare it with the previous result.
Agency portfolios
Run the same review across client sites, with a separate report for each.

Only run scans the user has asked for or approved as a recurring pattern. Never scan sites on your own initiative.

Connect to a workspace with Hosted MCP OAuth

With MCP Light, keep a scan ID or report link to revisit that result. For saved workspace history, access across conversations, or team work, connect Hosted MCP OAuth. It links Muse to your CertScore.ai workspace without copying an API key. A CertScore.ai account and workspace authorization are required.

Hosted MCP OAuth setup guide

Connection details

Remote MCP endpoint

https://mcp.certscore.ai/mcp/light
Service
CertScore.ai MCP Light
Transport
Streamable HTTP
Authentication
None. No account, API key, OAuth flow, or Authorization header.
Hosted release
0.2.31 (verified October 26, 2026)
Registry identity
ai.certscore/mcp-light
Cost
Free to use, with a scoped daily allowance.
Scope
Public websites only. The scanner cannot sign in to login-protected pages.

Current limits: https://certscore.ai/developers/mcp#light-usage-limits

Questions about CertScore.ai in Muse

Can I try it before scanning my own website?
Yes. Try ergoveritas.com/test1.html, then test2.html, or open the example reports on this page. They are owned demo pages with deliberate defects. Scores and findings can change after updates; request a fresh scan when checking a change.
Do I need an account or API key?
No. MCP Light works without an account, API key or OAuth sign-in, within its scoped daily allowance. The skill download is free.
Does switching to the California view create a scan?
No. EU and California report views use the same visit's evidence. To test a visit from Ireland, Germany or California, request a new scan from that location.
Can I return to a report later?
Yes. Keep its report link or scan ID. Ask Muse to retrieve that existing result; request a fresh scan when you want to check a later site change.
Does a high score mean the site is compliant?
No. Scores summarize the returned findings and coverage. Unknown checks remain unknown; automated observations are not a legal determination.

Quick reference

First scan
Connect, scan, poll, then present the bundle with evidence, coverage limits, and the report link.
Recheck
Request a fresh scan with purpose recheck and compare it with the baseline scan ID.
Rate limited
Tell the user and stop. Do not loop.
Need to verify a finding?
Retrieve its evidence page before reporting it.