How WebMCP Checker Works

A complete guide to using the audit tool and understanding your results.

1

Enter Your Website URL

Type any website URL — yours or a competitor's — in the checker input field. You don't need to include https://. Click "Run WebMCP Audit" or press Enter. The tool accepts domains like amazon.com or yoursite.com/shop.

2

AI Analyzes Your Site

The tool uses the Claude AI API to analyze your website across 8 technical dimensions critical for WebMCP compatibility. The analysis is based on publicly known information about the website's industry, typical technology stack, and common features. This takes 5–15 seconds.

3

Review Your Readiness Score (0–100)

Your WebMCP score appears with an animated ring showing your readiness at a glance. The score reflects how well your site's current structure, forms, and JavaScript patterns align with what WebMCP requires. Your verdict — Agent-Ready, Good Foundation, Needs Work, or Not Agent-Ready — summarizes the overall picture.

4

Examine the 8 Technical Checks

The Checks tab shows 8 specific dimensions, each marked Pass (✓), Fail (✗), or Warn (~) with a brief explanation specific to your website type. Review these to understand exactly where your site is strong and where it needs work before implementing WebMCP.

5

Follow the Prioritized Fix Recommendations

The Fix It tab lists 4 prioritized recommendations (High / Medium / Low) tailored to your specific website type and industry. High-priority items are quick wins that have the biggest impact on WebMCP readiness. Address these in order.

6

Copy the Implementation Code

The Code tab provides complete, copy-paste HTML and JavaScript code tailored to your site type. It includes both the Declarative API (form attributes) and Imperative API (navigator.modelContext.registerTool()) examples, ready to drop into your existing codebase.

7

Review Business Impact

The Impact tab shows a 5-dimension table comparing your current state vs. what you gain with WebMCP — across agent discoverability, conversion rate, AI traffic share, task completion rate, and developer effort. Use this to build a business case for implementing WebMCP.

8

Re-Audit After Implementation

After implementing changes, run the audit again to verify improvement. Also test in Chrome 146 Canary with the "WebMCP for testing" flag enabled at chrome://flags to see your tools actually working with real AI agents.

Understanding Your Score

75–100
✅ Agent-Ready
Strong foundations. Begin WebMCP implementation now — you're already 70-90% of the way there.
50–74
🔵 Good Foundation
Solid base with addressable gaps. Fix the High-priority items before starting WebMCP implementation.
25–49
⚠️ Needs Work
Significant structural improvements needed. Focus on HTML cleanup and semantic markup first.
0–24
❌ Not Agent-Ready
Fundamental issues to resolve. WebMCP implementation requires significant upfront work.

The 8 Audit Checks Explained

CheckWhat It TestsWhy It Matters for WebMCP
HTML Form QualityWhether forms have proper labels, semantic inputs, clear names and typesThe Declarative API relies on clean, well-structured HTML forms to register as tools
Semantic MarkupUse of appropriate HTML5 semantic elements (nav, main, article, form, button)Semantic structure helps agents understand page context and tool boundaries
JavaScript API ReadinessWhether the site's JS architecture can cleanly integrate navigator.modelContext callsTightly coupled SPAs need refactoring; clean service layers are WebMCP-ready
Tool Contract PotentialHow many clear, callable actions the site's features would translate to as toolsSites with high tool potential benefit most from WebMCP — more agent use cases
Form Action ClarityWhether form submission actions and outcomes are clear and unambiguousAgents need to understand what a form does before they can reliably call it as a tool
Structured Data / SchemaExisting schema.org or structured data implementationSites with structured data have already demonstrated they can think in machine-readable terms
Auth Flow CompatibilityWhether authentication flows would work within the browser session modelWebMCP uses browser sessions — complex custom auth flows may need adaptation
Agent-Discoverable ActionsWhether the site's key actions would be discoverable via a .well-known/webmcp manifestAutonomous agents (not user-present) need the manifest to discover what tools your site offers

Ready to Audit Your Website?

It takes 30 seconds. Enter your URL and get a complete WebMCP readiness report.

⚡ Run Free WebMCP Audit