Static pre-check · Fri, 28 Aug 2026 07:39:47 GMT
An AI agent would navigate Vorza's site nearly flawlessly with perfect accessibility and usability, facing no meaningful obstacles.
Watch a real agent use your site →
A live Claude Code run against vorza.dev, streamed step by step.
Measure this with real agents →
An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.
title is only 5 characters: 'Vorza'
Fix: Expand the <title> to 10–70 characters naming the product and what it does.
MCP endpoint advertised but no official-registry entry references this domain (0 result(s) for 'vorza')
Fix: Publish your server to the official MCP registry (registry.modelcontextprotocol.io) so agents can discover it by name.
1 API link(s), e.g. /api/openapi.json
Shows the current scan score and grade for this domain, straight from the latest static pre-check.
[](https://www.vorza.dev/score/vorza.dev)<a href="https://www.vorza.dev/score/vorza.dev"><img src="https://www.vorza.dev/api/badge/vorza.dev" alt="agent readiness score" /></a>https://www.vorza.dev
5 docs link(s), e.g. /docs
163 characters
og:title and og:description present
all 6 agent crawlers may fetch /
HTTP 200, 111 bytes
robots.txt has a Sitemap: line
444 URL(s) listed
2678 characters of text at /docs
HTTP 200 for / (agent UA)
https://www.vorza.dev/
1 valid block(s) (SoftwareApplication)
HTTP 200, 6893 bytes
HTTP 200, 1671 bytes
5 sampled link(s) all resolve
has headings and markdown links
Accept: text/markdown → text/markdown; charset=utf-8
both User-Agents got HTTP 200
10565 characters of text in the served HTML
ratio 0.0828 (10565 chars of 127530)
1 redirect(s)
HTTP 200, 2169 bytes
/docs → HTTP 200
404 with a JSON error body (code, message, next_action)
initialize ok — vorza 0.1.0, protocol 2025-06-18
all 14 parameter(s) typed and described
all 5 tools described
5 tool(s): scan_domain, get_score, get_leaderboard, get_skill …
1 scheme(s): none
11/11 operations described (100%)
HTTP 200, 22646 bytes of JSON
26 error response(s) with a schema
OpenAPI 3.1.0, 10 path(s)
HTTP 200, valid JSON
/api → HTTP 404 (no API at the conventional root)
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.