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
Jun 15, 2026, 9:12 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
67/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability59%Agent Easeof Use45%Security& Trust93%GEO, AIO, AEO64%SEO100%Performance95%Accessibility100%
  • AI Discoverability 59 out of 100
  • Agent Ease of Use 45 out of 100
  • Security & Trust 93 out of 100
  • GEO, AIO and AEO 64 out of 100
  • SEO 100 out of 100
  • Performance 95 out of 100
  • Accessibility 100 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Authress - login and access control API favicon

Authress - login and access control API

Login and access control API - granular, role and resource-based access for users of your software. Deliver the Auth your users expect.

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
59
Needs work3300
Discoverability
67
Needs work800
Content Readiness
66
Needs work1900
Bot Access Control
47
Priority fix600
Agent Ease of Use
45
Priority fix3355View details
API
44
Priority fix700
Auth
41
Priority fix600
MCP
42
Priority fix400
Skill Discovery
52
Needs work835View details
Agent Commerce
46
Priority fix820View details
GEO, AIO and AEO
64
Needs work900
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable300
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
93
Strong2700
Security & Trust
93
Strong2700
Performance
95
Strong1500
Performance
95
Strong1500
Accessibility
100
Strong200
Accessibility
100
Strong200

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAgent CommerceInformational

ACP - Agentic Commerce Protocol

ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".

54 Fail

Needs attention

ACP - Agentic Commerce Protocol

Failed check
01

Issue

ACP discovery content type "text/html" is not JSON-compatible.

02

Why it matters

ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.

Check name

ACP - Agentic Commerce Protocol

Score

46/100

Status

fail

Category

Agent Commerce

Maturity

Informational

Goal

Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.

Result

ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".

Validation steps

  1. Fetch ACP discovery

    ACP discovery content type "text/html" is not JSON-compatible.

  2. Validate ACP discovery shape

    ACP discovery could not be parsed.

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

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

26 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

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

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

48/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.

  2. Validate version-specific card shape

    A2A Agent Card response is not valid JSON.

  3. Validate HTTP delivery

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

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

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

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

22 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index was not served with a JSON-compatible Content-Type.

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

55/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 was not served with a JSON-compatible Content-Type.

    Response is not valid JSON.

  2. Verify advertised artifacts

    No valid skill artifacts were available to verify.

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

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

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