CertScore.ai MCP Light
REMOTE · MCP.CERTSCORE.AI
Free website privacy scanner for pre-consent cookies, trackers, consent, policy, and HTTPS/TLS.
Available components
Last scanned (12 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2256 tokens (~376/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Nov 26 0
- Server version: 0.2.34 → 0.2.35 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 308 → 376 ▼ functional
- Server version: 0.2.32 → 0.2.34 functional
- 2 Nov 26 0
- Server version: 0.2.31 → 0.2.32 functional
- 31 Oct 26 0
- Tool “certscore_get_report_evidence_page” rewrote its description, which is the text the model reads security
- “certscore_get_report_evidence_page” added an optional parameter “reviewFocus” cosmetic
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.2.30 → 0.2.31 functional
- 23 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 22 Oct 26 +2
- HSTS header: fail → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://mcp.certscore.ai/mcp/light
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=certscore.ai | CN=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 624332b977083e18ac97248e622bc87adbb |
| SANs: *.certscore.ai, certscore.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.certscore.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| certscore.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.certscore.ai/mcp/light | Verified | 200 | |
| http (plaintext) | http://mcp.certscore.ai/mcp/light | HTTPS enforced | 301 | https://mcp.certscore.ai:443/mcp/light |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
certscore_get_report_evidence_page Get report evidence page ~446
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 str…
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| reviewFocus | string | – | – |
| scanId | string | yes | – |
| section | string | – | – |
| workpaper | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | object | yes | – |
| download | object | – | – |
| entries | array | yes | – |
| pagination | object | yes | – |
| reconstruction | string | yes | – |
| reportUrl | string | yes | – |
| reviewFocus | string | – | – |
| scanId | string | yes | – |
| section | string | – | – |
| selection | object | – | – |
| snapshot | string | yes | – |
| type | string | yes | – |
| version | number | yes | – |
| workpaper | string | – | – |
No examples provided.
certscore_get_scan_bundle Get scan bundle ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Response detail. Defaults to summary; evidence and full opt into heavier retained context. |
| maxBytes | integer | – | Requested serialized structured response budget in bytes. The full profile defaults to 50000. MCP Light defaults to and applies a transport-safe 25000-byte ceiling; larger Light requests are clamped… |
| maxFindings | integer | – | Maximum compact findings to return. Defaults to 5 for summary and 20 otherwise. |
| maxPreConsentRows | integer | – | Maximum compact pre-consent inventory rows to return. Defaults to 20. |
| scanId | string | yes | Stable CertScore scan ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| accessibilityAudit | – | – | – |
| completedAt | string|null | yes | – |
| coverage | – | – | – |
| createdAt | string|null | yes | – |
| detail | string | yes | – |
| disclaimer | string|null | yes | – |
| domain | string | yes | – |
| error | – | yes | – |
| evidenceSummary | object | – | – |
| evidenceUrlTemplate | string | – | – |
| findings | array | yes | – |
| findingsMetadata | object | yes | – |
| formsSummary | – | – | – |
| fullReport | object | – | – |
| gpcResponse | – | – | – |
| interpretationGuidance | object | yes | – |
| links | object | – | – |
| mcpMetadata | object | yes | – |
| noGo | – | – | – |
| observationOnlyDisclaimer | string | yes | – |
| postAcceptObservation | – | – | – |
| postRefusalObservation | – | – | – |
| postureScores | object | – | – |
| preConsentCookiesTrackers | object | – | – |
| privacyAuditEvidence | – | – | – |
| privacyAuditSummary | object | – | – |
| provenance | object | yes | – |
| recommendedNextAction | string | yes | – |
| recommendedNextTool | – | yes | – |
| reportUrl | string|null | yes | – |
| resultDisposition | – | – | – |
| reviewNavigation | object | – | – |
| riskLevel | string|null | yes | – |
| scanFrom | – | yes | – |
| scanId | string | yes | – |
| scanTimeSeconds | number|null | yes | – |
| score | – | yes | – |
| scoreExplanation | – | – | – |
| scoreLabel | string | yes | – |
| scoreStatus | string | yes | – |
| scoreUpdatedAt | string|null | yes | – |
| scoreVersion | string|null | yes | – |
| startedAt | string|null | yes | – |
| status | string | yes | – |
| summary | object | – | – |
| timing | object | – | – |
| transportSecurity | – | yes | – |
| type | string | yes | – |
| url | string|null | yes | – |
No examples provided.
certscore_get_scan_status Get scan status ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scanId | string | yes | Stable CertScore scan ID returned by certscore_scan_site. |
| Name | Type | Req | Description |
|---|---|---|---|
| accessibilityAudit | – | – | – |
| completedAt | string|null | – | – |
| coverage | – | – | – |
| createdAt | string|null | – | – |
| domain | string|null | – | – |
| error | – | yes | – |
| estimatedRemainingSeconds | – | – | – |
| formsSummary | – | – | – |
| gpcResponse | – | – | – |
| interpretationGuidance | object | yes | – |
| jobId | string | – | – |
| lastHeartbeatAt | string|null | – | – |
| lastUpdatedAt | string | – | – |
| links | object | – | – |
| noGo | object | – | – |
| observationOnlyDisclaimer | string | yes | – |
| phase | string | – | – |
| phaseStartedAt | string|null | – | – |
| postAcceptObservation | – | – | – |
| postRefusalObservation | – | – | – |
| postureScores | object | – | – |
| preConsentPreview | object | – | – |
| progressIsEstimate | boolean | – | – |
| progressPercent | integer | – | – |
| provenance | object | yes | – |
| recommendedNextAction | string | yes | – |
| recommendedNextTool | – | yes | – |
| reportUrl | string|null | – | – |
| resultDisposition | string | – | – |
| retryAfterSeconds | – | – | – |
| riskLevel | string|null | – | – |
| scanFrom | – | – | – |
| scanId | string|null | – | – |
| scanTimeSeconds | number|null | – | – |
| scan_id | string|null | – | – |
| score | – | – | – |
| scoreExplanation | – | – | – |
| scoreLabel | string | yes | – |
| scoreStatus | string | – | – |
| scoreUpdatedAt | string|null | – | – |
| scoreVersion | string|null | – | – |
| stalled | boolean | – | – |
| startedAt | string|null | – | – |
| status | string | – | – |
| type | string | – | – |
| url | string|null | – | – |
No examples provided.
certscore_scan_site Scan site ~327
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.
| Name | Type | Req | Description |
|---|---|---|---|
| freshness | string | – | Scan freshness policy. latest allows eligible recent completed-result reuse when available; refresh requests a new scan. Defaults to latest. |
| scanFrom | string | – | Optional execution region for a newly queued scan: eu_de, eu_ie, california, or the service default when omitted. |
| taskContext | object | – | Optional caller-declared purpose and integration ID/version for usage research. Only include questionSummary when the user knowingly agrees to share a brief non-sensitive question for product improve… |
| url | string | yes | Public URL or domain to scan. |
| Name | Type | Req | Description |
|---|---|---|---|
| accessibilityAudit | – | – | – |
| completedAt | string|null | – | – |
| coverage | – | – | – |
| createdAt | string|null | – | – |
| demoSubstitution | object | – | – |
| domain | string|null | – | – |
| error | – | yes | – |
| formsSummary | – | – | – |
| gpcResponse | – | – | – |
| interpretationGuidance | object | yes | – |
| jobId | string | – | – |
| links | object | – | – |
| noGo | object | – | – |
| observationOnlyDisclaimer | string | yes | – |
| postAcceptObservation | – | – | – |
| postRefusalObservation | – | – | – |
| postureScores | object | – | – |
| preConsentPreview | object | – | – |
| provenance | object | yes | – |
| recommendedNextAction | string | yes | – |
| recommendedNextTool | – | yes | – |
| reportUrl | string|null | – | – |
| resultDisposition | string | – | – |
| riskLevel | string|null | – | – |
| scanFrom | string | – | – |
| scanId | string|null | – | – |
| scanTimeSeconds | number|null | – | – |
| score | – | – | – |
| scoreExplanation | – | – | – |
| scoreLabel | string | yes | – |
| scoreStatus | string | – | – |
| scoreUpdatedAt | string|null | – | – |
| scoreVersion | string|null | – | – |
| startedAt | string|null | – | – |
| status | – | yes | – |
| type | string | yes | – |
No examples provided.
How do I install the CertScore.ai MCP Light server?
CertScore.ai MCP Light is a hosted endpoint at https://mcp.certscore.ai/mcp/light, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.certscore.ai
claude mcp add --transport http ai-certscore-mcp-light 'https://mcp.certscore.ai/mcp/light'
What is the CertScore.ai MCP Light server?
CertScore.ai MCP Light is listed in the public MCP registry as ai.certscore/mcp-light. Free website privacy scanner for pre-consent cookies, trackers, consent, policy, and HTTPS/TLS. This page covers its hosted endpoint (https://mcp.certscore.ai/mcp/light).
Is the CertScore.ai MCP Light server safe to use?
CertScore.ai MCP Light scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CertScore.ai MCP Light server expose?
CertScore.ai MCP Light exposes 4 tools: certscore_scan_site, certscore_get_scan_status, certscore_get_report_evidence_page, certscore_get_scan_bundle. Their descriptions and schemas cost roughly 1,207 tokens of context every time the server is loaded.
Does the CertScore.ai MCP Light server require authentication?
No. We connected to CertScore.ai MCP Light without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CertScore.ai MCP Light server still maintained?
CertScore.ai MCP Light is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CertScore.ai MCP Light server?
VerifyMCP ran 13 checks on CertScore.ai MCP Light, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.