MCP.so
Sign In

CertScore.ai MCP Light

@ergoveritas1-alt

Basic information

Transport

streamable-http

Authentication

None

Category

Data & Analytics

Author

ergoveritas1-alt

Submitted by

ben masek

About CertScore.ai MCP Light

No-auth website privacy scanning through CertScore.ai MCP Light, with tools for scan submission, status and results. Authenticated upgrades are separate.

Connection details

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

Setup

claude mcp add certscore-ai-0e8a5a --transport http https://mcp.certscore.ai/mcp/light

CertScore.ai MCP Light tools

4

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.

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.

For a focused question, use section=cmp, cms, consent, gpc, policy, tracking, transport, forms or accessibility. This returns selected retained report sections plus shared scan, score, findings and coverage context. CMP includes all 13 criteria with their assessment results and retained comparisons; CMS includes platform/version evidence and existing advisories. Policy also includes retained privacy-choice controls, unverified link candidates and notice passages; California-focused reports include their shared privacy section. detailedEvidence carries shared display wording, counts and cross-links; these audit rows are not additional findings. Preserve section on cursor continuation; unselected or not-returned fields are not evidence of absence. Use workpaper=tracking separately for the starting-page tracking inventory, privacy choices/notices and GPC evidence, with JSON and CSV downloads. Never combine section and workpaper. The workpaper selector also applies to every continuation request. Otherwise retrieve scan report display content as paginated JSON, without internal diagnostic JSON downloads. The response also offers a single-file full JSON download; private JSON download links expire after five minutes and need no OAuth header; use pagination if your host blocks file downloads. Repeated display records use reportContentRef JSON Pointers. Includes evidence tables, full-site page and resource inventories, all retained additional-page form fields, form snapshot download references, and retained limitations. Snapshot images are downloaded separately from the returned URLs, with OAuth bearer authentication for workspace scans. Available on OAuth and Light. Start with scanId; follow pagination.nextCursor until complete. Pages share a snapshot; restart if it changes. Each entry has a JSON Pointer path and value; oversized strings use numbered parts. Export completion is not complete observation coverage. Use the concise scan bundle for summaries; use this tool for exhaustive report evidence. No new scan is created.

Main answer for a completed or completed-limited scan: canonical findings, next steps, supporting evidence, score, date/region, coverage and report URL. An existing scanId is enough; no new scan is created. The evidence index describes response delivery, never evidence absence. Optional next actions lead to deeper report tables, tracking workpapers and JSON/CSV exports. Use detail=evidence for request examples and policy candidates, including scans with no findings; detail=full adds bounded retained context. Preserve returned/total counts and omission metadata. Accept/Reject execution succeeded means a completed click and bounded observation; succeeded_with_confirmation additionally verifies the consent decision. Retained after-click facts remain distinct from registered decisions. Absent or failed capture remains explicitly limited. Use canonical findings for scoring effects. A later missing finding does not prove a fix. Results are automated public-web observations, not legal advice, certification, or a compliance determination.

Overview

What is CertScore.ai MCP Light?

No-auth website privacy scanning through CertScore.ai MCP Light, with tools for scan submission, status and results. Authenticated upgrades are separate.

How to use CertScore.ai MCP Light?

Connect an MCP-compatible client to https://mcp.certscore.ai/mcp/light using the authentication documented by the service.

Tools

  • certscore_scan_site — Use for a user-requested website launch review, vendor assessment, cookie/tracker inventory, consent
  • certscore_get_scan_status — Returns lifecycle status for a stable CertScore scanId. Active responses include phase, heartbeat, e
  • certscore_get_report_evidence_page — For a focused question, use section=cmp, cms, consent, gpc, policy, tracking, transport, forms or ac
  • certscore_get_scan_bundle — Main answer for a completed or completed-limited scan: canonical findings, next steps, supporting ev

Documentation

Repository · Documentation

Frequently asked questions

1

What is the CertScore.ai MCP Light remote MCP server?

The CertScore.ai MCP Light remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.certscore.ai/mcp/light, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the CertScore.ai MCP Light MCP server?

Add the endpoint https://mcp.certscore.ai/mcp/light to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the CertScore.ai MCP Light MCP server require authentication?

No. CertScore.ai MCP Light's MCP server does not require authentication — you can connect directly with the endpoint URL.

4

Which transport does the CertScore.ai MCP Light MCP server use?

CertScore.ai MCP Light exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments