CertScore.ai — Light mode
REMOTE · MCP.CERTSCORE.AI · SCANNED AUG 3
No-account public website privacy risk scans with 20 new scans/day and free recent-result reuse.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 363 tokens (~121/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.certscore.ai
claude mcp add --transport http ai-certscore-mcp-light https://mcp.certscore.ai/mcp/light
[mcp_servers.ai-certscore-mcp-light] url = "https://mcp.certscore.ai/mcp/light"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-certscore-mcp-light": {
"type": "remote",
"url": "https://mcp.certscore.ai/mcp/light",
"enabled": true
}
}
} openclaw mcp add ai-certscore-mcp-light --url https://mcp.certscore.ai/mcp/light --transport streamable-http
mcp_servers:
ai-certscore-mcp-light:
url: "https://mcp.certscore.ai/mcp/light" {
"mcpServers": {
"ai-certscore-mcp-light": {
"type": "http",
"url": "https://mcp.certscore.ai/mcp/light"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +28
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → good ▲ functional
- Schema quality: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: fail → 0.27 functional
- New tool “get_scan_status” functional
- New tool “get_scan_bundle” functional
- New tool “scan_site” functional
- 2 Aug 26 −27
- Stability: 0.20 → fail ▼ security
- A breaking change shipped without a version bump: still 0.2.12 ▼ security
- Tool “scan_site” was removed ▼ security
- Tool “get_scan_bundle” was removed ▼ security
- Tool “get_scan_status” was removed ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: fail → unverified ▼ functional
- Schema quality: good → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 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
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
First indexed and scored.
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 3 Aug 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=YE1,O=Let's Encrypt,C=US | 18 Jun 2026 | 16 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 5e4ade338e0ca05e645704c5622b9d67a50 |
| SANs: *.certscore.ai, certscore.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
DNSSEC insecure
Validation of mcp.certscore.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| certscore.ai. | absent | 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 |
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.
get_scan_bundle Get compact CertScore scan bundle ~98
Recommended second call after scan_site. Returns the canonical scan state, compact report summary, findings, bounded evidence summary, and pre-consent inventory in one agent-friendly response.
| Name | Type | Req | Description |
|---|---|---|---|
| maxFindings | integer | — | Maximum compact findings to return. Defaults to 20. |
| maxPreConsentRows | integer | — | Maximum pre-consent inventory rows to return. Defaults to 20. |
| scanId | string | yes | Stable CertScore scan ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| disclaimer | string|null | yes | — |
| evidenceSummary | — | — | — |
| findings | array | yes | — |
| links | object | — | — |
| noGo | — | — | — |
| preConsentCookiesTrackers | — | — | — |
| recommendedNextTool | string|null | yes | — |
| resultDisposition | — | — | — |
| scan | object | yes | — |
| scanId | string | yes | — |
| status | string | yes | — |
| summary | — | — | — |
| type | string | yes | — |
No examples provided.
get_scan_status Get CertScore Pulse scan status ~81
Retrieve terminal status, including completed_limited no-go disposition and reason-specific guidance. Pass jobId only before a stable scanId is available.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | — | Pulse job ID for a just-created scan that has not yet returned a scanId. |
| scanId | string | — | Preferred stable CertScore scan ID for API v2 scan status. |
| Name | Type | Req | Description |
|---|---|---|---|
| completedAt | string|null | — | — |
| domain | string|null | — | — |
| error | object | — | — |
| jobId | string | — | — |
| noGo | object | — | — |
| resultDisposition | string | — | — |
| scanId | string|null | — | — |
| scanTimeSeconds | number|null | — | — |
| scan_id | string|null | — | — |
| startedAt | string|null | — | — |
| status | string | — | — |
| type | string | — | — |
No examples provided.
scan_site Scan site ~184
Recommended first call. Starts or reuses a public-web scan, reports freshness and anonymous quota decisions, and waits up to 45 seconds by default. If still running, use get_scan_status; otherwise use get_scan_bundle. Completed no-go scans retain completed_limited status and reason-specific guidance.
| Name | Type | Req | Description |
|---|---|---|---|
| freshness | string | — | Use latest to reuse recent scans or refresh to request a new scan when eligible. |
| maxWaitSeconds | integer | — | Maximum time to wait before returning the still-running job. Defaults to 45 seconds; never turns an active scan into an error. |
| scanFrom | string | — | Optional scan execution context for newly queued scans. |
| url | string | yes | Public URL or domain to scan. |
| waitForCompletion | boolean | — | Wait for a completed scan resource in this tool call. Defaults to true. Set false only for an explicitly asynchronous workflow. |
| Name | Type | Req | Description |
|---|---|---|---|
| completedAt | string|null | — | — |
| domain | string|null | — | — |
| jobId | string | — | — |
| noGo | object | — | — |
| resultDisposition | string | — | — |
| scanFrom | string | — | — |
| scanId | string|null | — | — |
| scanTimeSeconds | number|null | — | — |
| startedAt | string|null | — | — |
| status | string | yes | — |
| type | string | yes | — |
No examples provided.