CertScore.ai MCP Light
ai.certscore/mcp-lightcertscore.aistreamable-httpv0.2.32Scanned
Free website privacy scanner for pre-consent cookies, trackers, consent, policy, and HTTPS/TLS.
4 tools: 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CertScore.ai MCP Light can do
The CertScore.ai MCP Light is published by certscore.ai, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: certscore_scan_site), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (certscore_scan_site and certscore_get_scan_bundle); 1 tool can send data out of your system (certscore_scan_site).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.2.32.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
certscore_scan_siteUse for a user-requested website launch review, vendor assessment, cookie/tracker inventory, consent/GPC investigation or privacy-policy review.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- title: Scan site
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
certscore_get_report_evidence_pageFor a focused question, use section=cmp, cms, consent, gpc, policy, tracking, transport, forms or accessibility.1 finding
Why it is in this group
- The name "certscore_get_report_evidence_page" says "get": a word for reading.
Findings
- Info
The description is 2,192 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...summaries; use this tool for exhaustive report evidence. No new scan is created."
Description, as the server wrote it 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.
Annotations the server declares
- title: Get report evidence page
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
certscore_get_scan_bundleMain answer for a completed or completed-limited scan: canonical findings, next steps, supporting evidence, score, date/region, coverage and report URL.Reads text others writeNo findings
Why it is in this group
- The name "certscore_get_scan_bundle" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get scan bundle
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
certscore_get_scan_statusReturns lifecycle status for a stable CertScore scanId.No findings
Why it is in this group
- The name "certscore_get_scan_status" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get scan status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.certscore.ai/mcp/light: tools/list returned 4 tools to an anonymous client, including certscore_scan_site (write)
Findings
Matches of fixed checks, with the text they matched.
The description is 2,192 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...summaries; use this tool for exhaustive report evidence. No new scan is created."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:certscore_get_report_evidence_pageOnly readsdescriptioninputSchema
Install
Pinned to version 0.2.32. Values in angle brackets are yours to fill in.
claude mcp add --transport http light https://mcp.certscore.ai/mcp/lightclaude mcp add --transport http light https://mcp.certscore.ai/mcp/lightRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__light__certscore_get_scan_status",
"mcp__light__certscore_get_report_evidence_page",
"mcp__light__certscore_get_scan_bundle"
],
"ask": [
"mcp__light__certscore_scan_site"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as light. Review it before you use it.
Capability tags behind 2 rules
- mcp__light__certscore_scan_site untrusted-input, outbound
- mcp__light__certscore_get_scan_bundle untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.certscore/mcp-light/verify?hash=7da104ae435c64142d3d7158608528c70e118e1ef065782ca2c7847c88202d9d" | jq -e '.changed == false'Pinned hash 7da104ae435c, from Nov 16, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.certscore/mcp-light/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.certscore/mcp-light)Source: MCP Registry · repository. Synced Nov 2, 2026, 19:17 UTC.
CertScore.ai MCP Light: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CertScore.ai MCP Light safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CertScore.ai MCP Light delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CertScore.ai MCP Light do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CertScore.ai MCP Light have?
- 4 tools: 1 write, 3 read. certscore_scan_site, certscore_get_scan_status, certscore_get_report_evidence_page and certscore_get_scan_bundle.
Does the CertScore.ai MCP Light need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CertScore.ai MCP Light send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): certscore_scan_site.
Has the CertScore.ai MCP Light changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.