Start with the live form
Enter a domain, URL, IP, email, or record and get a focused result without setup.
WebMCP · MCP · OpenAPI · llms.txt
Agent Readiness Checker
Run more than 35 bounded checks across discoverability, content, access policy, and capabilities. See a transparent score, confidence, evidence, and practical next steps.
–/100
The 0-100 score combines more than 35 bounded checks across four dimensions. Unknown checks are excluded from the score and lower confidence. Emerging features are labeled by maturity. DomScan does not execute discovered tools, and this is not an SEO ranking.
Readiness dimensions
Detailed checks
Recommended next steps
Evidence and limitations
Results reflect what DomScan could confirm at check time. Unknown checks are excluded from the 0-100 score and lower confidence. Emerging practices and draft features are labeled by maturity. The audit does not execute discovered tools and is not a certification.
Some WebMCP tools are registered only after scripts run, a user interacts, or a user signs in. A static website check may return Unknown even when those tools are available in a supported browser.
Protected resources, blocked requests, custom discovery paths, and temporary errors can also make a result inconclusive.
Not detected means this check did not confirm the signal. It does not prove that the signal is absent.
Interactive intelligence tool
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Review decision-ready signals
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Automate the winning workflow
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at amazing companies
What this tool helps you decide
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Service status
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
Free allowance
Sign Up for Free
Start with 10,000 monthly credits and upgrade only when usage grows.
Active
Example Request
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
WebMCP
Checks the page response for WebMCP declarations or registration signals that compatible browser agents may use while the page is open.
Remote MCP
Checks whether the website advertises or confirms a remote MCP connection for compatible clients.
OpenAPI
Checks for a discoverable and valid machine-readable description of the website's API.
llms.txt
Checks whether the website publishes an llms.txt guide that points agents to useful content and documentation.
Example Request
curl -G -H "X-API-Key: $DOMSCAN_API_KEY" --data-urlencode "url=https://example.com" https://domscan.net/v1/agent-readinessBuilt from the same API surface
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Frequently Asked Questions
What is agent readiness?
Agent readiness is a point-in-time view of how clearly a public website can be discovered, read, governed, and used by compatible agents. DomScan evaluates more than 35 bounded checks across four dimensions and reports evidence, confidence, and limitations. It is not a certification.
Does a strong result improve SEO?
No. Some checks overlap established technical SEO foundations, but the readiness score is not a search ranking and does not predict rankings. Use it alongside normal technical SEO and content quality work.
Why is a signal marked Unknown?
The signal could not be verified with the evidence available during the check. It may require a browser session, authentication, a custom discovery path, or another condition that the check could not confirm.
Does a signal marked Not detected mean the feature is unavailable?
No. It only means this check did not confirm the signal. Agents may still use regular page content, links, or tools exposed under conditions the check could not observe.