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 31, 2026, 11:25 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
68/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability64%Agent Easeof Use57%Security& Trust46%GEO, AIO, AEO66%SEO100%Performance76%Accessibility100%
  • AI Discoverability 64 out of 100
  • Agent Ease of Use 57 out of 100
  • Security & Trust 46 out of 100
  • GEO, AIO and AEO 66 out of 100
  • SEO 100 out of 100
  • Performance 76 out of 100
  • Accessibility 100 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

AI Customer Service Software For Smarter Support | Desku favicon

AI Customer Service Software For Smarter Support | Desku

Unify email, live chat and social support with Desku's AI-powered helpdesk. Automate repetitive queries, respond faster and delight every customer.

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
64
Needs work3810View details
Discoverability
67
Needs work800
Content Readiness
84
Mostly ready2900
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
57
Needs work1232View details
Auth
54
Needs work300
Skill Discovery
58
Needs work732View details
Google Agentic Browsing
73
Needs work200
GEO, AIO and AEO
66
Needs work900
GEO Readiness
Not Applicable
Not Applicable400
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
46
Priority fix800
Security & Trust
46
Priority fix800
Performance
76
Mostly ready1400
Performance
76
Mostly ready1400

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

69 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

Details

02

Why it matters

AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.

Check name

AI bot rules in robots.txt

Score

31/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.

Result

AI bot rules in robots.txt failed at "Classify AI crawler rules".

Validation steps

  1. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

    robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0

Agent Ease of UseSkill DiscoveryEmerging recommendation

agents.json

agents.json failed at "Validate Wildcard schema shape".

22 Fail

Needs attention

agents.json

Failed check
01

Issue

agents.json does not match the expected Wildcard OpenAPI workflow shape.

Details

02

Why it matters

Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.

Check name

agents.json

Score

55/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a Wildcard-style agents.json file so agents can discover OpenAPI-backed workflows, links, examples, and authentication requirements.

Result

agents.json failed at "Validate Wildcard schema shape".

Validation steps

  1. Validate Wildcard schema shape

    agents.json does not match the expected Wildcard OpenAPI workflow shape.

    agents.json schema shape is invalid or incomplete
  2. Validate flows and links

    No executable flows were found.

    agents.json flows or links are invalid
  3. Review examples and LLM usability

    Examples or descriptions are too thin for reliable agent argument generation.

    agents.json examples or descriptions need improvement
Evidence log3 steps · 18 lines
Validate Wildcard schema shape [fail]! agents.json does not match the expected Wildcard OpenAPI workflow shape.INFOValidate Wildcard schema shapeINFOParse agents.json and classify contract shape shape="unknown"FAILCompare contract shape actual="unknown" expected="wildcard"FAILCompare missing required schema fields actual="none" expected="none"FAILCompare Content-Type with JSON expectation actual=true expected=trueINFORecorded remote OpenAPI/schema reference reference="https://desku.io/wp-json/airewp/v1/info"INFORecorded remote OpenAPI/schema reference reference="https://desku.io/wp-json/wp/v2/pages?per_page=100&_fields=id,title,link,excerpt"INFORecorded remote OpenAPI/schema reference reference="https://desku.io/wp-json/wp/v2/posts"WARNSchema-shape warning warning="no examples were found for LLM argument generation"FAILagents.json does not match the expected Wildcard OpenAPI workflow shape.Validate flows and links [fail]! No executable flows were found.INFOValidate flows and linksFAILCompare workflow flow count actual=0 expected="> 0"FAILCompare operation link issues actual=0 expected=0FAILNo executable flows were found.Review examples and LLM usability [warning]! Examples or descriptions are too thin for reliable agent argument generation.INFOReview examples and LLM usabilityWARNCompare usable example count actual=0 expected="> 0 when actions are present"WARNLLM usability warning warning="no examples were found for LLM argument generation"WARNExamples or descriptions are too thin for reliable agent argument generation.

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Probe same-origin A2A endpoint".

12 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

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

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

77/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 "Probe same-origin A2A endpoint".

Validation steps

  1. Validate HTTP delivery

    legacy A2A card is served at the current agent-card.json path

    A2A Agent Card HTTP delivery is not standards-aligned
  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 HTTP delivery [warning]! legacy A2A card is served at the current agent-card.json pathINFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="application/json" expected="application/json or +json"INFOReview selected discovery path path="/.well-known/agent-card.json" pathClass="canonical-current"WARNHTTP delivery/path warning warning="legacy A2A card is served at the current agent-card.json path"WARNlegacy A2A card is served at the current agent-card.json pathProbe 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://desku.io/" statusCode=200FAILThe same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.

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