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
Nov 17, 2026, 12:25 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
80/100

OVERALL SCORE

Level 4, Mostly Ready

Good readiness for AI agents
AIDiscoverability77%Agent Easeof Use78%Security& Trust78%GEO, AIO, AEO61%SEO45%Performance100%Accessibility88%
  • AI Discoverability 77 out of 100
  • Agent Ease of Use 78 out of 100
  • Security & Trust 78 out of 100
  • GEO, AIO and AEO 61 out of 100
  • SEO 45 out of 100
  • Performance 100 out of 100
  • Accessibility 88 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

India Property Register: land records of every village and plot in India favicon

India Property Register: land records of every village and plot in India

Search 20 crore plots in 6,83,628 villages: ownership, maps, ownership changes, registrations, property tax, circle rates, bank auctions.

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
77
Mostly ready4211View details
Discoverability
82
Mostly ready900
Content Readiness
75
Mostly ready2711View details
Bot Access Control
75
Mostly ready600
Agent Ease of Use
78
Mostly ready5512View details
API
83
Mostly ready1112View details
Auth
76
Mostly ready1300
MCP
70
Needs work500
Skill Discovery
64
Needs work700
Agent Commerce
80
Mostly ready1500
Google Agentic Browsing
98
Strong400
GEO, AIO and AEO
61
Needs work900
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable300
SEO
45
Priority fix500
SEO
45
Priority fix500
Security & Trust
78
Mostly ready1810View details
Security & Trust
78
Mostly ready1810View details
Performance
100
Strong1900
Performance
100
Strong1900

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

60 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

Details

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

40/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Find enforcing CSP delivery".

Validation steps

  1. Find enforcing CSP delivery

    Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

    Enforcing Content-Security-Policy header is missing
Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="default-src 'self'; script-src 'self' 'unsafe-inline' https://checkout.razorpay.com https://cdnjs.cloudflare.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com; font-src 'self' data:; img-src 'self' data: https:; connect-src 'self' https://*.razorpay.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com; frame-src https://api.razorpay.com https://checkout.razorpay.com; frame-ancestors 'self'; base-uri '" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced."FAILOnly Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

45 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

Details

02

Why it matters

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Check name

Author attribution

Score

55/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

    Schema.org attribution is incomplete or relies only on publisher/fallback evidence.

    Schema.org author attribution is missing or incomplete
  2. Author identity quality

    No named author or publisher identity could be extracted.

    Author identity quality is incomplete
Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=1 namedContributors=0 authors=[] publishers=[{"role":"publisher","id":"https://indiapropertyregister.com/#org","sameAs":[],"format":"json-ld","mergedName":false}] formats=["json-ld"]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=1 authors=[] publishers=[{"role":"publisher","id":"https://indiapropertyregister.com/#org","sameAs":[],"format":"json-ld","mergedName":false}]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[{"role":"publisher","id":"https://indiapropertyregister.com/#org","sameAs":[],"format":"json-ld","mergedName":false}]FAILNo named contributor identity could be extracted

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate API catalog targets".

27 Fail

Needs attention

API Catalog

Failed check
01

Issue

API catalog target https://indiapropertyregister.com/commerce.md (service-doc) returned HTTP 403 instead of a 2xx/3xx response.

Details

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

73/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog failed at "Validate API catalog targets".

Validation steps

  1. Check API catalog HEAD Link header

    HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".

    API catalog HEAD Link discovery is incomplete
  2. Validate API catalog media type

    The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.

    API catalog media type is not application/linkset+json
  3. Validate API catalog targets

    API catalog target https://indiapropertyregister.com/commerce.md (service-doc) returned HTTP 403 instead of a 2xx/3xx response.

    API catalog targets are unreachable or media types mismatch
Evidence log3 steps · 26 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="application/linkset+json; charset=utf-8"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [warning]! The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.INFOValidate API catalog media typeWARNCompare API catalog media type actual="application/linkset+json; charset=utf-8" expected="application/linkset+json"WARNCompare RFC 9727 profile parameter actual=false expected=trueWARNThe API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter. status="warning"Validate API catalog targets [fail]! API catalog target https://indiapropertyregister.com/commerce.md (service-doc) returned HTTP 403 instead of a 2xx/3xx response.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsPASSAPI catalog target is reachable rel="service-desc" href="https://indiapropertyregister.com/api/v1/openapi.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/vnd.oai.openapi+json"PASSAPI catalog target is reachable rel="service-doc" href="https://indiapropertyregister.com/api/docs" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://indiapropertyregister.com/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"PASSAPI catalog target is reachable rel="status" href="https://indiapropertyregister.com/healthz" statusCode=200 contentType="text/plain; charset=UTF-8" advertisedType="text/plain"PASSAPI catalog target is reachable rel="service-desc" href="https://indiapropertyregister.com/.well-known/mcp/server-card.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"PASSAPI catalog target is reachable rel="service-doc" href="https://indiapropertyregister.com/api#mcp" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="service-doc" href="https://indiapropertyregister.com/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"PASSAPI catalog target is reachable rel="status" href="https://indiapropertyregister.com/healthz" statusCode=200 contentType="text/plain; charset=UTF-8" advertisedType="text/plain"PASSAPI catalog target is reachable rel="service-desc" href="https://indiapropertyregister.com/.well-known/agent-card.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"PASSAPI catalog target is reachable rel="service-doc" href="https://indiapropertyregister.com/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"PASSAPI catalog target is reachable rel="service-desc" href="https://indiapropertyregister.com/.well-known/ucp" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"FAILAPI catalog target failed validation rel="service-doc" href="https://indiapropertyregister.com/commerce.md" statusCode=403 contentType="text/html; charset=UTF-8" advertisedType="text/markdown" typeMatches=falsePASSAPI catalog target is reachable rel="service-desc" href="https://indiapropertyregister.com/.well-known/acp.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"FAILAPI catalog target failed validation rel="service-doc" href="https://indiapropertyregister.com/commerce.md" statusCode=403 contentType="text/html; charset=UTF-8" advertisedType="text/markdown" typeMatches=falseFAILCompare API catalog target failure count actual=4 expected=0FAILAPI catalog target https://indiapropertyregister.com/commerce.md (service-doc) returned HTTP 403 instead of a 2xx/3xx response.

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