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, 7:41 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
62/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability50%Agent Easeof Use62%Security& Trust84%GEO, AIO, AEO69%SEO85%Performance61%Accessibility61%
  • AI Discoverability 50 out of 100
  • Agent Ease of Use 62 out of 100
  • Security & Trust 84 out of 100
  • GEO, AIO and AEO 69 out of 100
  • SEO 85 out of 100
  • Performance 61 out of 100
  • Accessibility 61 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Home | Doctors Without Borders - USA favicon

Home | Doctors Without Borders - USA

Médecins Sans Frontières/Doctors Without Borders (MSF) treats people where the need is greatest. We are an international medical humanitarian organisation. We

Open Agent View

Next step

Turn this report into a fix workflow

3 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
50
Needs work2221View details
Discoverability
47
Priority fix600
Content Readiness
59
Needs work1511View details
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
62
Needs work400
API
67
Needs work100
Auth
48
Priority fix100
Google Agentic Browsing
100
Strong200
GEO, AIO and AEO
69
Needs work1000
GEO Readiness
Not Applicable
Not Applicable400
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable300
SEO
85
Mostly ready800
SEO
85
Mostly ready800
Security & Trust
84
Mostly ready2321View details
Security & Trust
84
Mostly ready2321View details
Performance
61
Needs work1300
Performance
61
Needs work1300

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

69 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

Details

02

Why it matters

AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.

Check name

AI bot rules in robots.txt

Score

31/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.

Result

AI bot rules in robots.txt failed at "Classify AI crawler rules".

Validation steps

  1. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

    robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

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

47 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

53/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
Evidence log3 steps · 12 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=["child-src","frame-src"]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 formCount=4WARNCompare 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.

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

33 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are invalid: json-ld datePublished is not a parseable date (March 7 2018, 2:24pm).; json-ld dateModified is not a parseable date (March 24 2026, 2:55pm)..

Details

02

Why it matters

Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.

Check name

Content freshness signals

Score

67/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose modified and published dates for freshness-aware retrieval, citation, and ranking.

Result

Content freshness signals is missing or incomplete.

Validation steps

  1. Validate structured freshness dates

    No Schema.org freshness dates were found.

    Structured freshness dates are missing or invalid
  2. Check date validity and consistency

    json-ld datePublished is not a parseable date (March 7 2018, 2:24pm).; json-ld dateModified is not a parseable date (March 24 2026, 2:55pm).

    Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Validate structured freshness dates [warning]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaWARNCheck structured freshness date count actual=2 expected="> 0" invalidDateCount=2 formats={"json-ld":2} alternateDates=[{"source":"http","channel":"header","property":"Last-Modified","value":"Thu, 02 Jul 2026 16:19:39 GMT","parsed":"2026-07-02T16:19:39.000Z","location":"HTTP response header: Last-Modified"},{"source":"sitemap","channel":"sitemap","property":"lastmod","value":"2026-03-24T14:55:49-04:00","parsed":"2026-03-24T18:55:49.000Z","location":"matching sitemap <lastmod> entry for this page URL"}]WARNStructured freshness dates include invalid values invalidDateCount=2Check date validity and consistency [fail]! json-ld datePublished is not a parseable date (March 7 2018, 2:24pm).; json-ld dateModified is not a parseable date (March 24 2026, 2:55pm).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=2 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"json-ld datePublished is not a parseable date (March 7 2018, 2:24pm)."},{"severity":"fail","message":"json-ld dateModified is not a parseable date (March 24 2026, 2:55pm)."}]FAILInvalid freshness date issue found issues=["json-ld datePublished is not a parseable date (March 7 2018, 2:24pm).","json-ld dateModified is not a parseable date (March 24 2026, 2:55pm)."]

Sign in to see 42 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
62/100Level 3, Bot-AwareCurrent report