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, 6:44 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
AIDiscoverability81%Agent Easeof Use51%Security& Trust73%GEO, AIO, AEO62%SEO92%Performance61%Accessibility97%
  • AI Discoverability 81 out of 100
  • Agent Ease of Use 51 out of 100
  • Security & Trust 73 out of 100
  • GEO, AIO and AEO 62 out of 100
  • SEO 92 out of 100
  • Performance 61 out of 100
  • Accessibility 97 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

DeployHQ — Deploy Your Website Automatically from Git favicon

DeployHQ — Deploy Your Website Automatically from Git

Deploy your website from GitHub, GitLab & Bitbucket automatically. Zero-downtime deployments, build pipelines, one-click rollbacks. Trusted by...

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
81
Mostly ready4100
Discoverability
80
Mostly ready800
Content Readiness
90
Strong2800
Bot Access Control
75
Mostly ready500
Agent Ease of Use
51
Needs work2383View details
API
75
Mostly ready700
Auth
39
Priority fix300
MCP
52
Needs work300
Skill Discovery
47
Priority fix453View details
Agent Commerce
41
Priority fix630View 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
92
Strong900
SEO
92
Strong900
Security & Trust
73
Needs work1600
Security & Trust
73
Needs work1600
Performance
61
Needs work1900
Performance
61
Needs work1900
Accessibility
97
Strong600
Accessibility
97
Strong600

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 "Validate ACP discovery shape".

55 Fail

Needs attention

ACP - Agentic Commerce Protocol

Failed check
01

Issue

ACP discovery is missing transports array.

Details

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

45/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 "Validate ACP discovery shape".

Validation steps

  1. Validate ACP discovery shape

    ACP discovery is missing transports array.

    ACP discovery is missing transports array.

    protocol.version must be a YYYY-MM-DD date string.

    protocol.supported_versions must be a non-empty array.

    capabilities.services must be a non-empty array.

  2. Validate ACP endpoint and transports

    transports is missing or empty.

  3. Validate ACP capabilities

    capabilities.services is missing or empty.

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate skill entries".

29 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

One or more Agent Skills entries have invalid required fields.

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

43/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 skill entries".

Validation steps

  1. Validate skill entries

    One or more Agent Skills entries have invalid required fields.

    Skill entry findings
    [
      {
        "url": "/llms.txt",
        "name": "deployhq-llms-txt",
        "type": "skill-md",
        "index": 3,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "digest"
        ],
        "warnings": [],
        "description": "Machine-readable site index following the llms.txt specification. Lists all public pages with descriptions for efficient content discovery.",
        "originClass": "same-origin",
        "resolvedUrl": "https://www.deployhq.com/llms.txt"
      }
    ]
  2. Verify advertised artifacts

    One or more advertised skill artifacts could not be fetched or failed raw-byte digest verification.

    Artifact verification failures
    [
      {
        "url": "https://www.deployhq.com/.well-known/agent-skills/cli/SKILL.md",
        "name": "deployhq-cli",
        "type": "skill-md",
        "index": 2,
        "content": {
          "reason": "[discarded fetched document data]",
          "discarded": true,
          "originalKeys": [
            "valid",
            "warnings",
            "failures",
            "security",
            "quality",
            "frontmatter"
          ],
          "originalType": "object"
        },
        "byteLength": 986,
        "statusCode": 200,
        "contentType": "text/plain; charset=utf-8",
        "originClass": "same-origin",
        "actualDigest": "sha256:ed4831206389d3733804e74cf33cbe3372262e9f96f6f0b2dd8065f5b4d865f8",
        "digestMatches": false,
        "advertisedDigest": "sha256:d9fa2181d4e4d7e23dfbf081f7e14ed6436222ca2f2d67478023f512a4c9c76b"
      }
    ]
  3. Validate skill content

    SKILL.md is missing YAML frontmatter.

    Skill content findings
    • SKILL.md is missing YAML frontmatter.
    • SKILL.md is missing YAML frontmatter.
    • SKILL.md is missing YAML frontmatter.
    • SKILL.md body lacks obvious workflow, input/output, example, or validation guidance.
    • {
        "truncated": true,
        "omittedCount": 2,
        "originalCount": 6
      }
  4. Review skill artifact security

    SKILL.md references external URLs; fetched content is an additional trust boundary (https://www.deployhq.com/support/getting-started, https://www.deployhq.com/llms.txt).

    Agent Skills security findings
    • SKILL.md references external URLs; fetched content is an additional trust boundary (https://www.deployhq.com/support/getting-started, https://www.deployhq.com/llms.txt).
    • SKILL.md references external URLs; fetched content is an additional trust boundary (https://github.com/deployhq/deployhq-mcp-server).
    • SKILL.md references shell or code-execution patterns that can modify systems, fetch remote code, or move data.
    • SKILL.md references external URLs; fetched content is an additional trust boundary (https://github.com/deployhq/deployhq-cli, https://deployhq.ai, https://deployhq.com/install/cli).

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

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

28 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

44/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. Discover A2A Agent Card

    The A2A Agent Card was found at a legacy or fallback path.

  2. Detect A2A card version

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

  3. Validate version-specific card shape

    Document does not match a supported A2A Agent Card shape.

    Missing required fields
    • skills[]
  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.

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