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

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability28%Agent Easeof Use40%Security& Trust45%GEO, AIO, AEO51%SEO91%Performance95%Accessibility0%
  • AI Discoverability 28 out of 100
  • Agent Ease of Use 40 out of 100
  • Security & Trust 45 out of 100
  • GEO, AIO and AEO 51 out of 100
  • SEO 91 out of 100
  • Performance 95 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

싼도메인- 임대형 쇼핑몰 솔루션 1위, KR도메인 공식 등록기관 favicon

싼도메인- 임대형 쇼핑몰 솔루션 1위, KR도메인 공식 등록기관

싼도메인 도메인 신규등록 KR 도메인 등록기관

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
28
Priority fix1100
Discoverability
28
Priority fix300
Content Readiness
17
Priority fix700
Bot Access Control
38
Priority fix100
Agent Ease of Use
40
Priority fix1433View details
API
50
Needs work400
Auth
38
Priority fix400
MCP
37
Priority fix300
Skill Discovery
41
Priority fix223View details
Google Agentic Browsing
33
Priority fix110View details
GEO, AIO and AEO
51
Needs work400
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable100
SEO
91
Strong700
SEO
91
Strong700
Security & Trust
45
Priority fix700
Security & Trust
45
Priority fix700
Performance
95
Strong1500
Performance
95
Strong1500
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

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

61 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

39/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. Discover A2A Agent Card

    The A2A Agent Card was found at a legacy or fallback path.

    A2A Agent Card is missing or discovered at a non-canonical path
  2. 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
  3. Validate version-specific card shape

    A2A Agent Card response is not valid JSON.

    A2A Agent Card shape is invalid for its version
  4. Validate HTTP delivery

    The card was parseable JSON but was not served with a JSON-compatible content type.

    A2A Agent Card HTTP delivery is not standards-aligned
  5. 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 log5 steps · 26 lines
Discover A2A Agent Card [warning]! The A2A Agent Card was found at a legacy or fallback path.INFODiscover A2A Agent CardINFOTry A2A discovery paths in priority order paths=["/.well-known/agent-card.json","/.well-known/agent.json","/agent-card.json","/.well-known/a2a/agent-card.json"]WARNA2A candidate path did not return a usable card path="/.well-known/agent-card.json" statusCode=404 contentType="text/html"WARNA2A candidate path did not return a usable card path="/.well-known/agent.json" statusCode=404 contentType="text/html"PASSFound an A2A candidate path="/agent-card.json" statusCode=200 contentType="text/html" bytes=552WARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=404 contentType="text/html"WARNSelected non-canonical A2A Agent Card path="/agent-card.json" pathClass="fallback" requestedUrl="https://www.ssandomain.com/agent-card.json"WARNThe A2A Agent Card was found at a legacy or fallback path.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]! A2A Agent Card response is not valid JSON.INFOValidate version-specific card shapeFAILCompare missing required card fields actual="none" expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[]FAILA2A Agent Card response is not valid JSON.Validate HTTP delivery [warning]! The card was parseable JSON but was not served with a JSON-compatible content type.INFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="text/html" expected="application/json or +json"INFOReview selected discovery path path="/agent-card.json" pathClass="fallback"WARNHTTP delivery/path warning warning="card was found only at a non-standard fallback path"WARNThe card was parseable JSON but was not served with a JSON-compatible content type.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."
}

AccessibilityAccessibilityBrowser audit

Active <area> elements must have alternative text

100 Fail

Check name

Active <area> elements must have alternative text

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Active <area> elements must have alternative text

Evidence
{
  "ruleId": "area-alt",
  "impact": "critical",
  "description": "Ensure <area> elements of image maps have alternative text",
  "tags": [
    "cat.text-alternatives",
    "wcag2a",
    "wcag244",
    "wcag412",
    "section508",
    "section508.22.a",
    "TTv5",
    "TT6.a",
    {
      "truncated": true,
      "omittedCount": 6,
      "originalCount": 14
    }
  ],
  "affectedNodeCount": 2,
  "nodes": [
    {
      "target": [
        "area[coords=\"877,29,910,61\"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 55
      },
      "failureSummary": "Fix any of the following:\n  Element has no alt attribute\n  aria-label attribute does not exist or is empty\n  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n  Element has no title attribute"
    },
    {
      "target": [
        "area[coords=\"115,0,784,92\"]"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 54
      },
      "failureSummary": "Fix any of the following:\n  Element has no alt attribute\n  aria-label attribute does not exist or is empty\n  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n  Element has no title attribute"
    }
  ]
}

Sign in to see 51 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