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 3, 2026, 2:57 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
53/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability62%Agent Easeof Use58%Security& Trust44%GEO, AIO, AEO50%SEO100%Performance86%Accessibility9%
  • AI Discoverability 62 out of 100
  • Agent Ease of Use 58 out of 100
  • Security & Trust 44 out of 100
  • GEO, AIO and AEO 50 out of 100
  • SEO 100 out of 100
  • Performance 86 out of 100
  • Accessibility 9 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Aktuelle Nachrichten aus Berlin und der Welt - Berliner Morgenpost favicon

Aktuelle Nachrichten aus Berlin und der Welt - Berliner Morgenpost

Aktuelle Nachrichten und Hintergründe aus Politik, Wirtschaft und Sport aus Berlin, Deutschland und der Welt.

Open Agent View

Next step

Turn this report into a fix workflow

2 failed checks are 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
62
Needs work2500
Discoverability
67
Needs work800
Content Readiness
57
Needs work1400
Bot Access Control
63
Needs work300
Agent Ease of Use
58
Needs work300
Auth
48
Priority fix100
Google Agentic Browsing
97
Strong200
GEO, AIO and AEO
50
Needs work400
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable100
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
44
Priority fix1043View details
Security & Trust
44
Priority fix1043View details
Performance
86
Mostly ready1610View details
Performance
86
Mostly ready1610View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection failed at "Validate CSP frame-ancestors".

38 Fail

Needs attention

Frame protection

Failed check
01

Issue

frame-ancestors contains invalid source expressions: *.funke.cue.cloud, app.storyblok.com.

Details

02

Why it matters

Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking and UI redressing risk.

Check name

Frame protection

Score

25/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.

Result

Frame protection failed at "Validate CSP frame-ancestors".

Validation steps

  1. Validate CSP frame-ancestors

    frame-ancestors contains invalid source expressions: *.funke.cue.cloud, app.storyblok.com.

    CSP frame-ancestors is missing or ineffective
  2. Validate X-Frame-Options

    No valid X-Frame-Options fallback is present.

    X-Frame-Options is missing, invalid, or obsolete
  3. Review observed browser responses

    One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

    Observed same-origin HTML responses lack frame protection
Evidence log3 steps · 12 lines
Validate CSP frame-ancestors [fail]! frame-ancestors contains invalid source expressions: *.funke.cue.cloud, app.storyblok.com.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=true reportOnlyHeaderPresent=false metaFrameAncestors=false policyCount=1 duplicateDirectives=[]FAILCompare effective frame-ancestors directive actual={"values":["'self'","*.funke.cue.cloud","app.storyblok.com"],"mode":"malformed","valid":false,"restrictive":false,"broadSources":[]} expected="valid restrictive enforcing frame-ancestors" issue="frame-ancestors contains invalid source expressions: *.funke.cue.cloud, app.storyblok.com."FAILframe-ancestors contains invalid source expressions: *.funke.cue.cloud, app.storyblok.com.Validate X-Frame-Options [fail]! No valid X-Frame-Options fallback is present.INFOValidate X-Frame-OptionsINFORead X-Frame-Options fallback value="missing" parsedValues=[] normalizedValues=[]FAILCompare X-Frame-Options value actual="missing" expected="DENY or SAMEORIGIN" valid=false obsoleteAllowFrom=false duplicateOrConflicting=false issue="No valid X-Frame-Options fallback is present."FAILNo valid X-Frame-Options fallback is present.Review observed browser responses [warning]! One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.INFOReview observed browser responsesINFOSample Chrome-observed same-origin responses observedResponseCount=110 sameOriginCount=59 htmlDocumentCount=1WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":1,"broadFrameAncestorsCount":0,"affected":[{"url":"https://www.morgenpost.de/","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8","contentSecurityPolicy":"frame-ancestors 'self' *.funke.cue.cloud app.storyblok.com","contentSecurityPolicyReportOnly":null}]} expected="0 missing/invalid or broad same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome did not emit valid frame protection."WARNOne or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate fetch baseline".

25 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

CSP does not define default-src; several fetch directives may have no restrictive fallback.

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

50/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 "Evaluate fetch baseline".

Validation steps

  1. Evaluate fetch baseline

    CSP does not define default-src; several fetch directives may have no restrictive fallback.

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

    No script-src or default-src directive constrains script execution.

    CSP script execution policy is unsafe
  3. Review hardening directives

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

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

    CSP does not define a reporting endpoint.

    CSP reporting is missing or incomplete
Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=[]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives frameAncestors=["'self'","*.funke.cue.cloud","app.storyblok.com"] formCount=2WARNCompare recommended hardening coverage actual=["object-src","base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri, form-action."WARNCSP is missing recommended hardening directives: object-src, base-uri, form-action.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.

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 36 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.

1 reports
Public score history report links
Scan dateScoreReadinessReport
53/100Level 3, Bot-AwareCurrent report