1. Find the gaps
See what we found in your page’s source, why it matters, and what to improve.
Start a checkWebMCP checks and starter code
Help AI agents
use your website.
Find common gaps in your public page. Get clear recommendations, starter code for supported fixes, and checks you can run again.
See starter code Automate checks with the SDK + CI toolkitRun from any Node project
npx @iswebmcp/developer-kit scan https://your-site.exampleYou review and apply the code. We don’t change or deploy your site.
No account needed
Check a public page
Public pages only. No sign-in, JavaScript execution, or browser cookies. We store the sanitized URL path and origin plus the outcome for 90 days. Do not paste signed or secret-bearing URLs. Privacy details
Site tools: graceful fallback active
2. Get starter code
Start with a search-tool adapter or an accessible search form. Connect it to your app.
Explore the two recipes3. Check your changes
Save a before-and-after report. Compare source findings from your terminal or CI.
Use the developer toolkitWebMCP is experimental. Source checks find potential issues; they do not execute your tools or prove that an AI agent can complete a task.
Same task · same app · two action surfaces
AI agents shouldn't have to guess where to click.
WebMCP lets a website expose actions like search, compare, and add to cart as typed tools. isWebMCP shows what changes—and checks whether the result can actually be verified.
Controlled comparison
What changes when the page exposes intent?
Synthetic headset task · find, compare, cart, then stop
The agent must operate the interface
Every step depends on discovering and interpreting UI state.
- 01Enter a maximum price
- 02Choose a minimum rating
- 03Enter minimum battery life
- 04Select noise canceling
- 05Apply the filters
- 06Inspect the result cards
- 07Select two eligible products
- 08Open the comparison
- 09Add the best match to the cart
- 10Inspect the cart to verify the result
Aurora Q45 selected
Same visible cart result through either path.
7/7
task checks pass
Checkout was not attempted. The safety boundary held.
01
The page names the action
An agent can discover “search products” instead of reverse-engineering fields, buttons, and result cards.
02
The schema checks the input
Price, rating, battery, and feature constraints arrive as typed fields instead of ambiguous prose.
03
The result can be verified
Stable product IDs and visible cart state make success testable while checkout stays out of bounds.
The report is the product
One URL. A ledger of what is known.
The source scan is intentionally conservative. It analyzes public source, maps candidate actions, and ranks next steps—while refusing to invent runtime proof it cannot observe.
- Every finding links back to exact, sanitized evidence.
- Unknown runtime quality stays unknown—not zero.
- Source, runtime, imported, measured, and inferred evidence never blur together.
Synthetic fixture · not a website observation
demo.iswebmcp.com/store
6
Source categories
Every input inspectable
0
Runtime trials
Not measured
3
Candidate actions
Fixture only
Action surface3 source candidates
SearchHuman UIInferred
CompareHuman UIInferred
AddHuman UIInferred
See the interaction patterns Explore the interaction model
Same task. Same app. Two paths.
The proof lab uses one synthetic catalog and one business-logic layer. Only the action surface changes.
Run the proof labBaseline
UI-only journey
Search → set filters → inspect → select → compare → add. Fully accessible and intentionally tool-free.
WebMCP
Structured journey
Search with constraints → compare stable IDs → update the same cart → verify visible state.
WebMCP Lift
Success, actions, elapsed time, retries, human intervention, and assertion coverage combine into a transparent −100 to +100 result.
Daily adoption desk
Track implementations, not mentions.
A dated evidence ledger of who implemented WebMCP, the tools they expose, the API surface they use, and what has—or has not—been verified.
Read today's adoption report9
Provider-engineered
72
Platform-inherited
28
Named tools
Presence ≠ readiness
Four states worth separating.
Present
A source hint or registered object exists.
Ready
Contracts are narrow, distinct, state-aware, and safe.
Successful
A representative journey reaches its observable postconditions.
Safe
The same journey respects authorization, confirmation, and data boundaries.
Learn + monitor
The field guide now lives beside the lab.
Build from source-linked explainers and how-tos, then follow meaningful WebMCP changes without mixing them up with broader MCP ecosystem news.
WebMCP vs. MCP: what runs in the browser, what runs elsewhere
A practical map of where browser-exposed WebMCP tools fit within the much broader Model Context Protocol ecosystem.
Read 7-minute guideIs your web app ready for WebMCP? Run a baseline audit first
Start with the workflows, semantics, and verification signals your application already exposes before deciding which actions deserve tools.
Read 8-minute guideLatest signal
MCP marks the Skills extension as published
Commit 24efd6e updates the official MCP repository documentation to reflect the Skills extension's published status and track continuing work in extension issues. SDK and client builders can now distinguish the published extension from its ongoing implementation work; this is broader MCP extension work, not a new MCP protocol version or a WebMCP browser change.
See source-linked updates