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 28, 2026, 3:26 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
49/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability62%Agent Easeof Use56%Security& Trust78%GEO, AIO, AEO57%SEO85%Performance37%Accessibility0%
  • AI Discoverability 62 out of 100
  • Agent Ease of Use 56 out of 100
  • Security & Trust 78 out of 100
  • GEO, AIO and AEO 57 out of 100
  • SEO 85 out of 100
  • Performance 37 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Fontainebleau Las Vegas: The Best Hotel Experience favicon

Fontainebleau Las Vegas: The Best Hotel Experience

Fontainebleau Las Vegas offers luxury stays, fine dining, nightlife, casino games, and relaxation in the heart of the Strip.

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 work3100
Discoverability
40
Priority fix400
Content Readiness
68
Needs work2200
Bot Access Control
75
Mostly ready500
Agent Ease of Use
56
Needs work1354View details
API
70
Needs work600
MCP
43
Priority fix100
Skill Discovery
48
Priority fix444View details
Google Agentic Browsing
67
Needs work210View details
GEO, AIO and AEO
57
Needs work500
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable100
SEO
85
Mostly ready800
SEO
85
Mostly ready800
Security & Trust
78
Mostly ready1800
Security & Trust
78
Mostly ready1800
Performance
37
Priority fix1200
Performance
37
Priority fix1200

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate discovery index schema".

30 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.

Details

02

Why it matters

An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.

Check name

Agent Skills index

Score

40/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.

Result

Agent Skills index failed at "Validate discovery index schema".

Validation steps

  1. Validate discovery index schema

    Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.

    Agent Skills discovery index schema is invalid
    Top-level issues
    • $schema must be https://schemas.agentskills.io/discovery/0.2.0/schema.json
    Invalid skills
    [
      {
        "index": 0,
        "valid": false,
        "name": "site-content-discovery",
        "type": "",
        "description": "Discover public content, llms.txt, expanded Markdown context, sitemap resources, and public discovery manifests.",
        "url": "https://www.fontainebleaulasvegas.com/.well-known/agent-skills/site-content-discovery/SKILL.md",
        "digest": "",
        "resolvedUrl": "https://www.fontainebleaulasvegas.com/.well-known/agent-skills/site-content-discovery/SKILL.md",
        "originClass": "same-origin",
        "missing": [
          "type",
          "digest"
        ],
        "invalid": [],
        "warnings": [
          "description should explain when to use the skill"
        ]
      }
    ]
  2. Validate skill entries

    One or more Agent Skills entries have invalid required fields.

    One or more skill entries are invalid
    Skill entry findings
    [
      {
        "index": 0,
        "valid": false,
        "name": "site-content-discovery",
        "type": "",
        "description": "Discover public content, llms.txt, expanded Markdown context, sitemap resources, and public discovery manifests.",
        "url": "https://www.fontainebleaulasvegas.com/.well-known/agent-skills/site-content-discovery/SKILL.md",
        "digest": "",
        "resolvedUrl": "https://www.fontainebleaulasvegas.com/.well-known/agent-skills/site-content-discovery/SKILL.md",
        "originClass": "same-origin",
        "missing": [
          "type",
          "digest"
        ],
        "invalid": [],
        "warnings": [
          "description should explain when to use the skill"
        ]
      }
    ]
  3. Verify advertised artifacts

    No valid skill artifacts were available to verify.

  4. Validate skill content

    For skill-md artifacts, include valid YAML frontmatter with name and description followed by Markdown. For archives, include a safe root SKILL.md and no unsafe paths.

  5. Review skill artifact security

    Do not publish secrets or prompt-injection instructions in skill artifacts. Treat scripts, archives, and cross-origin artifacts as software supply-chain surfaces.

Evidence log5 steps · 19 lines
Validate discovery index schema [fail]! Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.INFOValidate discovery index schemaINFOParse Agent Skills index JSON validJson=true contentTypeCompatible=trueFAILCompare $schema URI expected="https://schemas.agentskills.io/discovery/0.2.0/schema.json"FAILCompare top-level schema issue count actual=1 expected=0WARNCompare unknown top-level field count actual=4 expected=0FAILAgent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.Validate skill entries [fail]! One or more Agent Skills entries have invalid required fields.INFOValidate skill entriesFAILCompare advertised skill count actual=1 expected="> 0"FAILCompare valid skill entry count actual=0 expected="same as advertised skill count"FAILInvalid skill entry skill={"index":0,"valid":false,"name":"site-content-discovery","type":"","description":"Discover public content, llms.txt, expanded Markdown context, sitemap resources, and public discovery manifests.","url":"https://www.fontainebleaulasvegas.com/.well-known/agent-skills/site-content-discovery/SKILL.md","digest":"","resolvedUrl":"https://www.fontainebleaulasvegas.com/.well-known/agent-skills/site-content-discovery/SKILL.md","originClass":"same-origin","missing":["type","digest"],"invalid":[],"warnings":["description should explain when to use the skill"]}FAILOne or more Agent Skills entries have invalid required fields.Verify advertised artifacts [warning]! No valid skill artifacts were available to verify.INFOVerify advertised artifactsWARNCompare artifact fetch count actual=0 expected="> 0"WARNNo valid skill artifacts were available to verify.Validate skill content [warning]INFOValidate skill contentWARNAgent Skills step completed with warningsReview skill artifact security [warning]INFOReview skill artifact securityWARNCompare security finding count actual=0 expected=0WARNAgent Skills step completed with warnings

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Detect A2A card version".

24 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

The discovered JSON document does not match a supported A2A Agent Card version family.

Details

02

Why it matters

A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.

Check name

A2A Agent Card

Score

53/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.

Result

A2A Agent Card failed at "Detect A2A card version".

Validation steps

  1. Detect A2A card version

    The discovered JSON document does not match a supported A2A Agent Card version family.

    A2A Agent Card version cannot be classified cleanly
  2. Validate version-specific card shape

    Document does not match a supported A2A Agent Card shape.

    A2A Agent Card shape is invalid for its version
    Missing required fields
    • skills[]
  3. Probe same-origin A2A endpoint

    A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.

    Advertised same-origin A2A endpoint did not answer a safe probe
Evidence log3 steps · 13 lines
Detect A2A card version [fail]! The discovered JSON document does not match a supported A2A Agent Card version family.INFODetect A2A card versionINFORead version indicators from the card detectionEvidence=[]FAILCompare detected A2A version family actual="unknown" expected="v0.1, v0.2, v0.3, or v1"FAILThe discovered JSON document does not match a supported A2A Agent Card version family.Validate version-specific card shape [fail]! Document does not match a supported A2A Agent Card shape.INFOValidate version-specific card shapeFAILCompare missing required card fields actual=["skills[]"] expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[{"url":"https://www.fontainebleaulasvegas.com/","protocolBinding":"JSONRPC","issues":[]}]FAILDocument does not match a supported A2A Agent Card shape.Probe same-origin A2A endpoint [warning]! A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itSKIPSkipped endpoint probe reason="No valid A2A card was available to probe."WARNA2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.

Agent Ease of UseGoogle Agentic BrowsingBrowser audit

Accessibility tree is not well-formed

100 Fail

Check name

Accessibility tree is not well-formed

Score

0/100

Status

fail

Device

desktop

Category

Google Agentic Browsing

Fix guidance

A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.

Evidence
{
  "description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}

Sign in to see 45 other issues and the full report

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

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