CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jul 11, 2026, 4:41 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
70/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability75%Agent Easeof Use59%Security& Trust73%GEO, AIO, AEO42%SEO92%Performance84%Accessibility86%
  • AI Discoverability 75 out of 100
  • Agent Ease of Use 59 out of 100
  • Security & Trust 73 out of 100
  • GEO, AIO and AEO 42 out of 100
  • SEO 92 out of 100
  • Performance 84 out of 100
  • Accessibility 86 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Email marketing platform | Mailercloud favicon

Email marketing platform | Mailercloud

No page metadata or readable excerpt was captured.

Open Agent View

Next step

Turn this report into a fix workflow

1 failed check is ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
75
Mostly ready3300
Discoverability
67
Needs work800
Content Readiness
89
Mostly ready2100
Bot Access Control
69
Needs work400
Agent Ease of Use
59
Needs work300
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
42
Priority fix400
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable100
SEO
92
Strong910View details
SEO
92
Strong910View details
Security & Trust
73
Needs work1932View details
Security & Trust
73
Needs work1932View details
Performance
84
Mostly ready1210View details
Performance
84
Mostly ready1210View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Parse CSP directives".

65 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

CSP directive "default-src" appears more than once; browsers use the first occurrence.

Details

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

35/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Parse CSP directives".

Validation steps

  1. Parse CSP directives

    CSP directive "default-src" appears more than once; browsers use the first occurrence.

    Content-Security-Policy directives are malformed or duplicated

    Duplicate CSP directive: default-src. Browsers use the first occurrence and ignore later duplicates.

    Duplicate CSP directive: script-src. Browsers use the first occurrence and ignore later duplicates.

    Duplicate CSP directive: worker-src. Browsers use the first occurrence and ignore later duplicates.

  2. Evaluate fetch baseline

    default-src is present but not meaningfully restrictive.

    CSP fetch baseline is too broad or missing
  3. Evaluate script execution

    script-src leaves script execution broadly unrestricted.

    CSP script execution policy is unsafe
  4. Review hardening directives

    CSP is missing recommended hardening directives: object-src, base-uri.

    CSP hardening directives are missing or weak
  5. Review CSP reporting

    CSP does not define a reporting endpoint.

    CSP reporting is missing or incomplete
Evidence log5 steps · 20 lines
Parse CSP directives [fail]! CSP directive "default-src" appears more than once; browsers use the first occurrence.INFOParse CSP directivesINFOParse enforcing CSP directives directives=["default-src","script-src","worker-src","style-src","font-src","img-src","frame-src","frame-ancestors","media-src"] reportOnlyDirectives=[]FAILCheck directive syntax actual={"duplicateDirectives":["default-src","script-src","worker-src","style-src","font-src","img-src","frame-src","frame-ancestors","media-src"],"unknownDirectives":[],"malformedDirectives":[],"emptyPolicy":false} expected="parseable directives with no duplicate or malformed names" issue="CSP directive \"default-src\" appears more than once; browsers use the first occurrence."FAILCSP directive "default-src" appears more than once; browsers use the first occurrence.Evaluate fetch baseline [fail]! default-src is present but not meaningfully restrictive.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback defaultSrc=["'self'","http:","https:","data:","wss:"] explicitFetchDirectives=["font-src","frame-src","img-src","media-src","script-src","style-src","worker-src"]FAILCompare fetch baseline actual=["'self'","http:","https:","data:","wss:"] expected="restricted default-src or broad explicit fetch coverage" issue="default-src is present but not meaningfully restrictive."FAILdefault-src is present but not meaningfully restrictive.Evaluate script execution [fail]! script-src leaves script execution broadly unrestricted.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","'unsafe-inline'","'unsafe-eval'","https:"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":false,"hasBroadScheme":true,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="script-src leaves script execution broadly unrestricted."FAILscript-src leaves script execution broadly unrestricted.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrcFallback=["'self'","http:","https:","data:","wss:"] frameAncestors=["'self'"] formCount=0WARNCompare recommended hardening coverage actual=["object-src","base-uri"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri."WARNCSP is missing recommended hardening directives: object-src, base-uri.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.

SEOSEOBrowser audit

Document does not have a meta description

100 Fail

Check name

Document does not have a meta description

Score

0/100

Status

fail

Device

desktop

Category

SEO

Fix guidance

Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/).

Evidence
{
  "description": "Meta descriptions may be included in search results to concisely summarize page content. [Learn more about the meta description](https://developer.chrome.com/docs/lighthouse/seo/meta-description/)."
}

PerformancePerformanceBrowser audit

Forced reflow

100 Fail

Check name

Forced reflow

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations.

Evidence
{
  "description": "A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and possible mitigations."
}

Sign in to see 33 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Email code

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

Fix with MCP / CLI

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

2 reports
Public score history report links
Scan dateScoreReadinessReport
70/100Level 3, Bot-AwareCurrent report
69/100Level 3, Bot-AwareView report