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 9, 2026, 7:39 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
50/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability16%Agent Easeof Use10%Security& Trust40%GEO, AIO, AEO69%SEO92%Performance79%Accessibility92%
  • AI Discoverability 16 out of 100
  • Agent Ease of Use 10 out of 100
  • Security & Trust 40 out of 100
  • GEO, AIO and AEO 69 out of 100
  • SEO 92 out of 100
  • Performance 79 out of 100
  • Accessibility 92 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Vivodyne - Human Data Before The Clinic favicon

Vivodyne - Human Data Before The Clinic

We create predictive human data before clinical trials to accelerate the discovery of new targets and better therapeutics.

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
16
Priority fix300
Discoverability
14
Priority fix100
Content Readiness
38
Priority fix200
Agent Ease of Use
10
Priority fix120View details
MCP
25
Priority fix100
Skill Discovery
5
Priority fix020View details
GEO, AIO and AEO
69
Needs work500
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable100
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
40
Priority fix200
Security & Trust
40
Priority fix200
Performance
79
Mostly ready1100
Performance
79
Mostly ready1100
Accessibility
92
Strong810View details
Accessibility
92
Strong810View 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".

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

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Fetch to find resource".

50 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index was not found at the expected path.

02

Why it matters

An Agent Skills index lets clients find task-specific SKILL.md documents that describe how to use site capabilities correctly.

Check name

Agent Skills index

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent skills discovery index.

Result

Agent Skills index failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    Agent Skills index was not found at the expected path.

AccessibilityAccessibilityBrowser audit

`<html>` element does not have a `[lang]` attribute

100 Fail

Check name

`<html>` element does not have a `[lang]` attribute

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. [Learn more about the `lang` attribute](https://dequeuniversity.com/rules/axe/4.11/html-has-lang).

Evidence
{
  "description": "If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. [Learn more about the `lang` attribute](https://dequeuniversity.com/rules/axe/4.11/html-has-lang)."
}

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