AgentProbe
docs.rngneeds.com
55/ 100
1.3s·6/12 passed·4/18/2026

Access

Whether AI bots can actually reach your content

83
✓

AI Bot Access

Pass

All 3 tested AI bots receive full page content.

✓

JS Independence

Pass

Rich text content (4910 chars) and 8 heading(s) available without JavaScript.

▲

Performance

Partial

Response time: 993ms. 1 redirect(s).

Agent-Native

Support for agent-specific protocols and formats

0
✗

Markdown Support

Fail

No markdown content negotiation support detected.

✗

MCP Protocol

Fail

No MCP (Model Context Protocol) configuration found.

✗

Structured API

Fail

No structured API or OpenAPI specification detected.

Discovery

How easily AI agents can find and understand your site

75
✓

llms.txt

Pass

llms.txt found with proper title and links. llms-full.txt also available.

✓

robots.txt AI Bot Rules

Pass

robots.txt found. All 8 AI bots are allowed.

✓

XML Sitemap

Pass

sitemap.xml found. Contains 42 URLs.

✗

AI Manifest

Fail

No AI manifest files found (.well-known/ai-plugin.json or .well-known/mcp.json).

Metadata

Structured data and metadata quality

50
✗

Schema.org

Fail

No JSON-LD structured data found.

✓

HTML Metadata

Pass

All key HTML metadata present.

Recommendations

5 suggestions
1

Add a /.well-known/ai-plugin.json or mcp.json to declare AI capabilities.

2

Support content negotiation for text/markdown to serve agent-friendly content.

3

Consider implementing MCP (Model Context Protocol) for richer AI integration.

4

Expose an OpenAPI/Swagger spec so AI agents can discover your API endpoints.

5

Add JSON-LD structured data (Schema.org) to help AI understand your content.

Scan another URL