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 8, 2026, 4:08 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
35/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability17%Agent Easeof Use45%Security& Trust66%GEO, AIO, AEO33%SEO100%Performance84%Accessibility0%
  • AI Discoverability 17 out of 100
  • Agent Ease of Use 45 out of 100
  • Security & Trust 66 out of 100
  • GEO, AIO and AEO 33 out of 100
  • SEO 100 out of 100
  • Performance 84 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

【网康科技】下一代防火墙、上网行为管理<font>推荐</font>服务商 favicon

【网康科技】下一代防火墙、上网行为管理<font>推荐</font>服务商

网康科技作为国内新一代安全厂商,多年来一直致力于下一代防火墙(NGFW)、上网行为管理、智能流控(ITM)、广域网优化网关(WOG)等产品,产品覆盖网络安全、终端安全、网络优化,形成了完整的网络安全与管理解决方案。网康发布PDFP新型网络安全模型,率先推出“云管端下一代网络安全架构”,实现“云管端”智能协同、主动防御,有效应对未知威胁与APT攻击。

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
17
Priority fix600
Discoverability
15
Priority fix200
Content Readiness
4
Priority fix300
Bot Access Control
28
Priority fix100
Agent Ease of Use
45
Priority fix3132View details
API
44
Priority fix700
Auth
41
Priority fix600
MCP
42
Priority fix400
Skill Discovery
47
Priority fix622View details
Agent Commerce
45
Priority fix700
Google Agentic Browsing
50
Needs work110View details
GEO, AIO and AEO
33
Priority fix300
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable100
SEO
100
Strong800
SEO
100
Strong800
Security & Trust
66
Needs work1300
Security & Trust
66
Needs work1300
Performance
84
Mostly ready1200
Performance
84
Mostly ready1200
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 "Detect A2A card version".

52 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

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

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

48/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. Detect A2A card version

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

    A2A Agent Card version cannot be classified cleanly
  2. Validate version-specific card shape

    A2A Agent Card response is not valid JSON.

    A2A Agent Card shape is invalid for its version
  3. Validate HTTP delivery

    The card was parseable JSON but was not served with a JSON-compatible content type.

    A2A Agent Card HTTP delivery is not standards-aligned
  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.

    Advertised same-origin A2A endpoint did not answer a safe probe
Evidence log4 steps · 17 lines
Detect A2A card version [fail]! The discovered JSON document does not match a supported A2A Agent Card version family.INFODetect A2A card versionINFORead version indicators from the card detectionEvidence=[]FAILCompare detected A2A version family actual="unknown" expected="v0.1, v0.2, v0.3, or v1"FAILThe discovered JSON document does not match a supported A2A Agent Card version family.Validate version-specific card shape [fail]! A2A Agent Card response is not valid JSON.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=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[]FAILA2A Agent Card response is not valid JSON.Validate HTTP delivery [warning]! The card was parseable JSON but was not served with a JSON-compatible content type.INFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="text/html; charset=utf-8" expected="application/json or +json"INFOReview selected discovery path path="/.well-known/agent-card.json" pathClass="canonical-current"WARNThe card was parseable JSON but was not served with a JSON-compatible content type.Probe same-origin A2A endpoint [warning]! A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itSKIPSkipped endpoint probe reason="No valid A2A card was available to probe."WARNA2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.

AccessibilityAccessibilityBrowser audit

Accessibility audit

100 Fail

Check name

Accessibility audit

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Make sure the page can load in Chrome and run Accessibility checks.

Evidence
{
  "error": "Accessibility audit did not return a result."
}

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."
}

Sign in to see 47 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Email code

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

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

1 reports
Public score history report links
Scan dateScoreReadinessReport
35/100Level 2, Agent-LimitedCurrent report