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 12, 2026, 5:32 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
32/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability22%Agent Easeof Use10%Security& Trust40%GEO, AIO, AEO75%SEO77%Performance12%Accessibility63%
  • AI Discoverability 22 out of 100
  • Agent Ease of Use 10 out of 100
  • Security & Trust 40 out of 100
  • GEO, AIO and AEO 75 out of 100
  • SEO 77 out of 100
  • Performance 12 out of 100
  • Accessibility 63 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Pixalate - Ad Fraud Protection, Privacy, and Compliance Platform (CTV) favicon

Pixalate - Ad Fraud Protection, Privacy, and Compliance Platform (CTV)

Pixalate, the market-leading ad fraud protection, privacy, and compliance analytics platform for Connected TV (CTV), Mobile Advertising, and Websites.

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
22
Priority fix400
Discoverability
33
Priority fix200
Content Readiness
38
Priority fix200
Agent Ease of Use
10
Priority fix110View details
MCP
25
Priority fix100
Skill Discovery
5
Priority fix010View details
GEO, AIO and AEO
75
Mostly ready600
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable200
SEO
77
Mostly ready700
SEO
77
Mostly ready700
Security & Trust
40
Priority fix200
Security & Trust
40
Priority fix200
Performance
12
Priority fix1000
Performance
12
Priority fix1000
Accessibility
63
Needs work320View details
Accessibility
63
Needs work320View 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 "Fetch to find resource".

100 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

A2A Agent Card was not found at the expected path.

02

Why it matters

A2A Agent Cards let compatible clients discover agent skills, input and output modes, and the endpoint used to invoke those skills.

Check name

A2A Agent Card

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent card so A2A-compatible clients can discover capabilities.

Result

A2A Agent Card failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    A2A Agent Card was not found at the expected path.

AccessibilityAccessibilityBrowser audit

`[aria-*]` attributes do not match their roles

50 Fail

Check name

`[aria-*]` attributes do not match their roles

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. [Learn how to match ARIA attributes to their roles](https://dequeuniversity.com/rules/axe/4.11/aria-allowed-attr).

Evidence
{
  "description": "Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. [Learn how to match ARIA attributes to their roles](https://dequeuniversity.com/rules/axe/4.11/aria-allowed-attr)."
}

AccessibilityAccessibilityBrowser audit

`[aria-hidden="true"]` elements contain focusable descendents

50 Fail

Check name

`[aria-hidden="true"]` elements contain focusable descendents

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements](https://dequeuniversity.com/rules/axe/4.11/aria-hidden-focus).

Evidence
{
  "description": "Focusable descendents within an `[aria-hidden=\"true\"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements](https://dequeuniversity.com/rules/axe/4.11/aria-hidden-focus)."
}

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