CertScore.ai MCP Light

CertScore.ai MCP Light

Recommended discovery entry: no-auth Streamable HTTP website privacy scans for MCP clients. Give an agent a public URL and retrieve evidence-backed observations about cookies and storage, trackers and vendors, consent controls, privacy-policy surfaces, and HTTPS/TLS signals.

CertScore.ai MCP Light is live in the GitHub MCP Registry as ai.certscore/mcp-light. It exposes four tools and requires no signup, API key, bearer token, browser login, or OAuth.

Start with MCP Light · Install in Cursor · Read the installation reference

Try it in about a minute

Add the public endpoint to Codex:

codex mcp add certscore --url https://mcp.certscore.ai/mcp/light

Then ask:

Review https://ergoveritas.com/.well-known/certscore-canary/sentinels/broad-baseline.html for website privacy risks. Explain the main findings, supporting evidence, coverage limits, and what to inspect next.

ErgoVeritas is a stable, owned canary with intentional test signals. For an ordinary review, substitute any public HTTP or HTTPS URL you are authorized to assess.

Light MCP — no authentication: start here

Light is the anonymous Streamable HTTP endpoint for first-time and low-volume agent workflows:

Light:

https://mcp.certscore.ai/mcp/light

Authentication: None Tools: certscore_scan_site, certscore_get_scan_status, certscore_get_scan_bundle, certscore_get_report_evidence_page

Light applies session, requester-IP and shared creation limits. See the current policy at https://certscore.ai/developers/mcp#light-usage-limits. Reused eligible results do not consume quota.

Light is a free website privacy scanner and cookie checker for public websites. It can return canonical evidence and findings for pre-consent cookies and storage, trackers and vendors, cookie banners, CMP and consent controls, the jurisdiction-neutral GPC comparison, Accept and Reject Path post-action observations or explicit limitations, privacy-policy and transparency surfaces, GDPR/ePrivacy and CCPA/CPRA review signals, and HTTPS/TLS transport observations. Typical uses include release privacy preflight, public vendor-domain review, landing-page tracker inspection, audit triage, and evidence collection before human privacy review.

First-run prompt:

Review https://ergoveritas.com/.well-known/certscore-canary/sentinels/broad-baseline.html for website privacy risks. Explain the main findings, supporting evidence, coverage limits, and what to inspect next.

Canonical Light workflow:

1. Call certscore_scan_site with a public URL.
2. If a retryable error has no scanId, wait retryAfterSeconds and retry certscore_scan_site.
3. If preConsentPreview is present, it is a partial preview of checkpoint passive observations. Its counts are partial, not the full scan tally; never report them as final totals. It contains no canonical findings or score and does not replace the completed bundle.
4. If the result is queued, running, or finalizing, retain scanId.
5. Poll certscore_get_scan_status using scanId only. Never poll until scanId exists.
6. Stop polling at any terminal status. At completed or completed_limited, call certscore_get_scan_bundle before reporting full scan results, and use its final returned tally, canonical findings, and limitations; for other terminal states, follow the returned error guidance.
7. Use detail=findings for a compact finding review.
8. Use detail=evidence for finding digests, bounded external-request examples, policy-surface candidates, and references, including when no finding was projected. A request for an external script does not by itself establish tracking; use certscore_get_report_evidence_page for deeper retained report evidence.
9. If truncated, follow recommendedNextAction or increase maxBytes.
10. Summarize findings together with coverage limitations and the report URL.

Recommended bundle budgets are maxBytes=5000 for summary, maxBytes=8000 for findings, maxBytes=8000 for evidence, and maxBytes=12000 to 25000 for full. MCP Light applies a 25,000-byte response ceiling so results remain within practical client limits; larger requested budgets are reported but clamped. At the 5,000-byte floor, compact core finding rows take priority over optional inventory and duplicate envelope fields. When repeated per-finding URLs are omitted, evidenceUrlTemplate points to contentUrls.findings and the returned finding ID so the same canonical evidence endpoint remains derivable. Inspect canonicalFindingsComplete, requestedMaxBytes, effectiveMaxBytes, responseCeilingBytes, actualBytes, fullPayloadBytes, truncated, omittedSections, nextRecommendedMaxBytes, and returned report or evidence content URLs. When canonicalFindingsComplete is true, retry only if omitted envelope detail is needed.

The final minimum-core fallback also enforces the requested structured-byte budget. Under pressure it removes empty envelopes, redundant retrieval URLs and duplicate prose while retaining typed posture scores and coverage, forms, accessibility, scan identity and core finding data. contentUrls may be empty with an explicit omission marker; use reportUrl or the same-scan evidence tool. If the core itself cannot fit, the tool returns a bounded, non-retryable response_budget_exceeded error instead of an oversized or altered report. Its guidance recommends a sufficient budget only when it fits within the transport ceiling; otherwise use bounded report-evidence pages. Never create a replacement scan to recover from a response-budget error.

Verification prompt:

List the available CertScore tools. Read certscore://example-report if resources are supported; otherwise call certscore_get_scan_bundle with scanId=9ba99a8c-b1ad-44c1-985f-92cef760ab40. Report the retained example’s original date and coverage. If unavailable, report that; do not create a new scan to test the connection.

Connection verification succeeds when the four Light tools are listed without an authorization page and the retained example can be retrieved with its original date and coverage. An unavailable historical example does not authorize a replacement scan. For your first website review, scan creation separately returns a stable scan ID and a new-or-reused decision; eligible reuse consumes no new-scan quota.

CertScore results are automated observations from a public-web scan. No-go, not-observed, and limited-coverage results are not proof of compliance, absence of risk, or legal status. Review the retained evidence and applicable context before relying on a finding.

Scans describe observable behavior at a point in time. Public sites may behave differently on later visits or in another execution context. CertScore findings and the CertScore score support human and agentic review; they are not legal advice, certification, or a compliance determination.

Which MCP route should I use?

The full/authenticated Streamable HTTP endpoint is https://mcp.certscore.ai/mcp. Use it after Light when the workflow requires authentication, higher volume, history, or advanced tools. Core identifiers and canonical response fields remain compatible when moving from Light to authenticated access.

Weighted read limits

MCP scan-resource reads use the same weighted, rolling policy as the direct CertScore API. Hosted MCP rejects an over-limit composite call before internal fan-out; local MCP receives the same protection from the underlying API. Poll only active status resources, stop at a terminal status, do not repeatedly retrieve terminal scan resources, and honor Retry-After before retrying. The current limits and weights are published at https://certscore.ai/developers/reference#read-rate-limits and in the x-certscore-read-rate-policy extension of the public OpenAPI documents.

Authenticated and local MCP tool reference

The sections below document the broader authenticated and local package surfaces. The Light contract exposes certscore_scan_site, certscore_get_scan_status, certscore_get_scan_bundle, and certscore_get_report_evidence_page.

• certscore_scan_site - Use for a user-requested website launch review, vendor assessment, cookie/tracker inventory, consent/GPC investigation or privacy-policy review. A public URL or domain is enough. Creates a privacy scan or reuses an eligible recent completed scan; default freshness=latest saves new-scan quota. Use refresh only for an explicitly requested fresh scan or post-fix recheck. Retain scanId, poll certscore_get_scan_status only while active at retryAfterSeconds, then read certscore_get_scan_bundle. A preliminary preConsentPreview is not final findings or totals. Coverage includes pre-consent storage, trackers, consent and CMP signals, privacy-policy disclosures, transport security and GDPR/ePrivacy or CCPA/CPRA review signals. Results are automated observations, not legal advice, certification, or a compliance determination. https://certscore.ai/developers/mcp.

Workflow note: a new scan may include preConsentPreview when the runtime lane completes or reaches its six-second checkpoint. The preview separates captured totals from bounded returned identities. trackingVendorCount excludes infrastructure, security, and consent-management vendors, which appear in operationalVendors; the compatibility preview count is not comparable to the completed inventory's broader trackerCount. Continue with certscore_get_scan_status, never poll in parallel, and never resubmit certscore_scan_site while the scan is active. Then call certscore_get_scan_bundle at completed or completed_limited.

• certscore_get_scan - Retrieve the API v2 public-safe scan resource, including completed-limited no-go disposition, reason-specific guidance, and timing when available.
• certscore_get_scan_status - Returns lifecycle status for a stable CertScore scanId. Active responses include phase, heartbeat, estimated progress, retryAfterSeconds, and sometimes a bounded preliminary preConsentPreview. Terminal responses include completion status, CertScore score and risk metadata when available, coverage, persisted execution region and timestamps, report URL, and a next-action field. Preliminary observations are distinct from completed findings.
• certscore_get_report - Focused follow-up: retrieve a bounded Pulse report with high-signal TextContent and typed structuredContent, including customer-safe no-go messaging. For broad privacy questions, use certscore_get_scan_bundle first because it combines canonical findings, limitations, and pre-consent rows without redundant calls.
• certscore_get_evidence - Focused follow-up: retrieve a bounded public-safe