Is your website ready for AI agents?

What the checker looks at

• WebMCP tools: forms with toolname attributes and tools registered in JavaScript.
• Safety hints: whether tools say which actions are read-only and which need the visitor’s approval.
• Data for agents: WordPress REST API, WooCommerce Store API, structured data, llms.txt and sitemap.
• Forms: whether every field has a label an agent can read.
• Safety basics: HTTPS, and whether the public API lists your user accounts.

The most common fixes

• Offer your most-asked actions as tools first: search, product or service details, and contact.
• Mark sensitive tools (cart, booking, sending forms) so agents ask the visitor before using them.
• Label every form field, and add JSON-LD structured data for your business and products.
• Keep the public API limited to what customers need, and hide user lists.

What does the WebMCP checker look for?

It loads the page you enter and up to 8 of its own scripts, and looks for WebMCP tools: forms with toolname attributes (the declarative API) and tools registered with modelContext.registerTool (the imperative API). It also checks HTTPS, the WordPress REST API and WooCommerce Store API, structured data, form labels, llms.txt and the sitemap. It uses fixed rules, not AI.

What is WebMCP?

WebMCP (Web Model Context Protocol) is a proposed web standard that lets a website offer named tools, such as “search products”, to AI agents running in the browser. The agent calls the tool and gets clean data back, instead of reading the screen and clicking. As of October 2026 it runs in Chrome as an origin trial.

My site has no WebMCP tools. Is that bad?

Not yet. Very few websites have WebMCP today, because the standard is new. The report shows what you already have that tools could use, and what to add first, so you can be early.

Why didn’t it find my tools?

Tools that only load after login, on another page, or from a script on a different domain are not visible from outside. Enter the exact page where your tools live, such as your shop page. Code that builds tool names at runtime may show as “name set at runtime”.

Does the checker change anything on my site?

No. It only reads public pages and public API indexes, the same way a browser does. It never submits forms, calls your tools or logs in.

What happens with my email and website?

We email you a code to confirm your address, then your report. Your email, website and result go to our team and CRM so an engineer can help, and we may occasionally email you about your website; you can unsubscribe at any time. We do not share your details with anyone else.