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 26, 2026, 6:46 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
64/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability86%Agent Easeof Use66%Security& Trust82%GEO, AIO, AEO62%SEO100%Performance73%Accessibility0%
  • AI Discoverability 86 out of 100
  • Agent Ease of Use 66 out of 100
  • Security & Trust 82 out of 100
  • GEO, AIO and AEO 62 out of 100
  • SEO 100 out of 100
  • Performance 73 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Email signature management for teams & AI agents | Scribe favicon

Email signature management for teams & AI agents | Scribe

Install consistent signatures company-wide in under a day. No employee installation. 12% average CTR on banners, conversion tracking from click to revenue.

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
86
Mostly ready4400
Discoverability
100
Strong1000
Content Readiness
86
Mostly ready2900
Bot Access Control
75
Mostly ready500
Agent Ease of Use
66
Needs work3130View details
API
79
Mostly ready700
Auth
78
Mostly ready1200
MCP
43
Priority fix100
Skill Discovery
65
Needs work920View details
Google Agentic Browsing
67
Needs work210View details
GEO, AIO and AEO
62
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
82
Mostly ready2000
Security & Trust
82
Mostly ready2000
Performance
73
Needs work1400
Performance
73
Needs work1400
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 "Validate version-specific card shape".

42 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.

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

58/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 "Validate version-specific card shape".

Validation steps

  1. Validate version-specific card shape

    A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.

    A2A Agent Card shape is invalid for its version
    Invalid skills
    • #0 (scribe-analytics): tags[]
    • #1 (scribe-campaigns): tags[]
    • #2 (scribe-signature-design): tags[]
    • #3 (scribe-teammates-and-smart-fields): tags[]
    • {
        "truncated": true,
        "omittedCount": 1,
        "originalCount": 5
      }
  2. Probe same-origin A2A endpoint

    The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.

    Advertised same-origin A2A endpoint did not answer a safe probe
Evidence log2 steps · 9 lines
Validate version-specific card shape [fail]! A2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.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=5 expected=0 invalidSkills=[{"index":0,"id":"scribe-analytics","issues":["tags[]"]},{"index":1,"id":"scribe-campaigns","issues":["tags[]"]},{"index":2,"id":"scribe-signature-design","issues":["tags[]"]},{"index":3,"id":"scribe-teammates-and-smart-fields","issues":["tags[]"]},{"index":4,"id":"scribe","issues":["tags[]"]}]INFOReview declared endpoint interfaces interfaces=[{"url":"https://www.scribe-mail.com/","protocolBinding":"HTTP+JSON","issues":[]}]FAILA2A Agent Card is missing required fields, contains invalid URLs, or exposes unsafe public metadata.Probe same-origin A2A endpoint [fail]! The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itFAILA2A endpoint probe did not validate url="https://www.scribe-mail.com/message:send" statusCode=404FAILThe same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.

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

ARIA attributes must conform to valid values

100 Fail

Check name

ARIA attributes must conform to valid values

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

ARIA attributes must conform to valid values

Evidence
{
  "ruleId": "aria-valid-attr-value",
  "impact": "critical",
  "description": "Ensure all ARIA attributes have valid values",
  "tags": [
    "cat.aria",
    "wcag2a",
    "wcag412",
    "EN-301-549",
    "EN-9.4.1.2",
    "RGAAv4",
    "RGAA-7.1.1"
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        "#tab-marketing"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 123
      },
      "failureSummary": "Fix all of the following:\n  Invalid ARIA attribute value: aria-controls=\"tabpanel-marketing\""
    }
  ]
}

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