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 17, 2026, 2:42 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
51/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability37%Agent Easeof Use53%Security& Trust54%GEO, AIO, AEO59%SEO92%Performance94%Accessibility0%
  • AI Discoverability 37 out of 100
  • Agent Ease of Use 53 out of 100
  • Security & Trust 54 out of 100
  • GEO, AIO and AEO 59 out of 100
  • SEO 92 out of 100
  • Performance 94 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Pinggy - Simple Localhost Tunnels favicon

Pinggy - Simple Localhost Tunnels

Pinggy is the simplest way to bring your localhost projects online. It the the fastest way to create secure tunnels to localhost with a public url.

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
37
Priority fix1620View details
Discoverability
33
Priority fix500
Content Readiness
40
Priority fix1100
Bot Access Control
38
Priority fix020View details
Agent Ease of Use
53
Needs work124View details
API
67
Needs work100
Skill Discovery
46
Priority fix024View details
GEO, AIO and AEO
59
Needs work600
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong800
SEO
92
Strong800
Security & Trust
54
Needs work1000
Security & Trust
54
Needs work1000
Performance
94
Strong1500
Performance
94
Strong1500
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

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 "Fetch robots.txt".

100 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No robots.txt content was available to inspect for AI bot rules.

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

0/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 "Fetch robots.txt".

Validation steps

  1. Fetch robots.txt

    No robots.txt content was available to inspect for AI bot rules.

  2. Classify AI crawler rules

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

Evidence log2 steps · 10 lines
Fetch robots.txt [fail]! No robots.txt content was available to inspect for AI bot rules.INFOFetch robots.txtINFORequesting /robots.txt from the site originFAILCheck whether robots.txt content is available actual="no content" expected="content returned" length=0FAILNo robots.txt content was available to inspect for AI bot rules.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=0 unspecified=21

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate discovery index schema".

67 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.

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

33/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 discovery index schema".

Validation steps

  1. Discover Agent Skills index

    Agent Skills index was found only at the legacy /.well-known/skills/index.json path.

  2. Validate discovery index schema

    Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.

    Top-level issues
    • $schema must be https://schemas.agentskills.io/discovery/0.2.0/schema.json
    Invalid skills
    [
      {
        "url": "",
        "name": "pinggy",
        "type": "",
        "index": 0,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [],
        "description": "This skill should be used when the user asks to \"expose localhost\", \"share local server\", \"create a tunnel\", \"test webhooks locally\", \"use Pinggy\", \"access remote device\", \"forward a port\", \"set up ngrok alternative\", \"make localhost public\", \"persistent subdomain\", \"custom domain tunnel\", \"TCP tunnel\", \"UDP tunnel\", \"TLS tunnel\", or mentions Pinggy. Covers all Pinggy tunnel types, access methods, authentication, domains, SDKs, and advanced features.",
        "originClass": "same-origin",
        "resolvedUrl": "https://pinggy.io/.well-known/skills/index.json"
      }
    ]
  3. Validate skill entries

    One or more Agent Skills entries have invalid required fields.

    Skill entry findings
    [
      {
        "url": "",
        "name": "pinggy",
        "type": "",
        "index": 0,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [],
        "description": "This skill should be used when the user asks to \"expose localhost\", \"share local server\", \"create a tunnel\", \"test webhooks locally\", \"use Pinggy\", \"access remote device\", \"forward a port\", \"set up ngrok alternative\", \"make localhost public\", \"persistent subdomain\", \"custom domain tunnel\", \"TCP tunnel\", \"UDP tunnel\", \"TLS tunnel\", or mentions Pinggy. Covers all Pinggy tunnel types, access methods, authentication, domains, SDKs, and advanced features.",
        "originClass": "same-origin",
        "resolvedUrl": "https://pinggy.io/.well-known/skills/index.json"
      }
    ]
  4. Verify advertised artifacts

    No valid skill artifacts were available to verify.

  5. Validate skill content

    For skill-md artifacts, include valid YAML frontmatter with name and description followed by Markdown. For archives, include a safe root SKILL.md and no unsafe paths.

  6. Review skill artifact security

    Do not publish secrets or prompt-injection instructions in skill artifacts. Treat scripts, archives, and cross-origin artifacts as software supply-chain surfaces.

Evidence log6 steps · 24 lines
Discover Agent Skills index [warning]! Agent Skills index was found only at the legacy /.well-known/skills/index.json path.INFODiscover Agent Skills indexINFOTry Agent Skills index paths in priority order paths=["/.well-known/agent-skills/index.json","/.well-known/skills/index.json"]WARNAgent Skills index candidate was not usable path="/.well-known/agent-skills/index.json" url="https://pinggy.io/.well-known/agent-skills/index.json" statusCode=404PASSFetched Agent Skills index candidate path="/.well-known/skills/index.json" url="https://pinggy.io/.well-known/skills/index.json" statusCode=200 contentType="application/json" bytes=794 selected="selected"WARNAgent Skills index was found only at the legacy /.well-known/skills/index.json path.Validate discovery index schema [fail]! Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.INFOValidate discovery index schemaINFOParse Agent Skills index JSON validJson=true contentTypeCompatible=trueFAILCompare $schema URI expected="https://schemas.agentskills.io/discovery/0.2.0/schema.json"FAILCompare top-level schema issue count actual=1 expected=0FAILCompare unknown top-level field count actual=0 expected=0FAILAgent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.Validate skill entries [fail]! One or more Agent Skills entries have invalid required fields.INFOValidate skill entriesFAILCompare advertised skill count actual=1 expected="> 0"FAILCompare valid skill entry count actual=0 expected="same as advertised skill count"FAILInvalid skill entry skill={"index":0,"valid":false,"name":"pinggy","type":"","description":"This skill should be used when the user asks to \"expose localhost\", \"share local server\", \"create a tunnel\", \"test webhooks locally\", \"use Pinggy\", \"access remote device\", \"forward a port\", \"set up ngrok alternative\", \"make localhost public\", \"persistent subdomain\", \"custom domain tunnel\", \"TCP tunnel\", \"UDP tunnel\", \"TLS tunnel\", or mentions Pinggy. Covers all Pinggy tunnel types, access methods, authentication, domains, SDKs, and advanced features.","url":"","digest":"","resolvedUrl":"https://pinggy.io/.well-known/skills/index.json","originClass":"same-origin","missing":["type","url","digest"],"invalid":[],"warnings":[]}FAILOne or more Agent Skills entries have invalid required fields.Verify advertised artifacts [warning]! No valid skill artifacts were available to verify.INFOVerify advertised artifactsWARNCompare artifact fetch count actual=0 expected="> 0"WARNNo valid skill artifacts were available to verify.Validate skill content [warning]INFOValidate skill contentWARNAgent Skills step completed with warningsReview skill artifact security [warning]INFOReview skill artifact securityWARNCompare security finding count actual=0 expected=0WARNAgent Skills step completed with warnings

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

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