Skip to main content
Glama

CertScore.ai MCP Light

Server Details

Free website privacy scanner for pre-consent cookies, trackers, consent, policy, and HTTPS/TLS.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
ergoveritas1-alt/certscore.ai
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation4/5

The four tools map cleanly onto a scan lifecycle: launch, poll status, read the summary bundle, and drill into report evidence. The only real overlap is between certscore_get_scan_bundle and certscore_get_report_evidence_page, both returning content from a completed scan, though the descriptions frame one as the concise 'main answer' and the other as exhaustive evidence. The evidence-page description is extremely dense with section/workpaper switches, which adds some selection friction but not true duplication.

Naming Consistency5/5

All names share a consistent certscore_ prefix and snake_case form, with get_* used uniformly for the three read operations and scan_site as the single creation verb. The pattern is predictable and readable.

Tool Count5/5

Four tools is exactly the right size for a scan lifecycle: launch, status, summary, and deep evidence. Each tool earns its place with no filler, and the surface stays well under the range where selection burden grows.

Completeness4/5

The core lifecycle is fully covered from scan creation through polling to summary and exhaustive evidence retrieval. Minor gaps exist: no tool to list or enumerate prior scans, no cancel/delete operation, and no scan-to-scan comparison, but agents can work around these if they retain scanIds.

Available Tools

4 tools
certscore_get_report_evidence_pageGet report evidence pageA
Read-only
Inspect

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. Use reviewFocus=gdpr_eprivacy or ccpa_cpra to match the corresponding web/PDF/Word view; omit it to retain the scan default. Preserve reviewFocus and 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.

Inputs: scanId (required), cursor, section, workpaper, +1 more. Returns: type, scanId, entries, section, +10 more

certscore_get_scan_bundleGet scan bundleA
Read-only
Inspect

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.

Inputs: scanId (required), detail, maxBytes, maxFindings, +1 more. Returns: url, noGo, type, error, +45 more

certscore_get_scan_statusGet scan statusA
Read-onlyIdempotent
Inspect

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.

Inputs: scanId (required). Returns: url, noGo, type, error, +42 more

certscore_scan_siteScan siteAInspect

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.

Inputs: url (required), scanFrom, freshness, taskContext. Returns: noGo, type, error, jobId, +32 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Audit any website for privacy, security, accessibility, and performance issues — with scores, grades, and actionable fix instructions. No account required.
      3
      11 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Scan any project or website for privacy compliance issues directly in your AI coding tool. Detects tracking tech, cookies, and third-party data collection. Works in Claude Code, Cursor, and Windsurf.
      3
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Scans public URLs for compliance and security issues such as leaked API keys, exposed files, missing privacy pages, and security headers, helping developers identify gaps before launch.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.