Every website that speaks agent, in one place. That's the bet behind WebMCP Directory, a new project from One Scales: a free, automatically-verified index of sites that expose tools to AI agents through WebMCP.
Why this exists
WebMCP is early. It's a proposal in front of the W3C Web Machine Learning Community Group, not a shipping browser feature — support today comes from browser extensions and agent runtimes that inject a navigator.modelContext shim, not from browsers themselves. That earliness is exactly why no canonical list of "who's doing this" exists yet.
WebMCP Directory is our attempt to be that list before someone else builds it. We did the same thing with LLMS.txt Directory for llms.txt adoption. WebMCP is one protocol later, same idea: index the surface area while it's still small enough to index.
What WebMCP actually is
MCP (Model Context Protocol) is for headless, backend automation — an agent talking server-to-server. WebMCP is the complement: it lets an agent operate the app a human is already looking at, in their browser, in their session.
That distinction matters for four reasons the directory's explainer leads with:
- Auth is already solved. The agent acts inside the user's existing session — no API keys to provision or rotate.
- Permissions are already scoped. The agent can do whatever the UI can do. Nothing more.
- Nothing new to host. Tools ship with the front end. They can't drift out of sync with a separate server.
- The user can watch. It happens in a visible tab, not an invisible server call.
Sites implement this by calling registerTool() against navigator.modelContext, naming tools after intents rather than routes — add_to_cart({ sku, quantity }) instead of an agent guessing which button says "Add to Cart."
How the directory verifies a listing
We don't take a site's word for it. Submission is four fields — URL, a short description, a category, an email that's never shown publicly — and then a Cloudflare Worker does the actual work: it fetches the page and scans for three signals — navigator.modelContext usage, registerTool call sites, and a /.well-known/mcp.json descriptor. Any hit publishes the listing immediately, along with whatever tool names it could read.
We're upfront that this is evidence, not proof. A miss goes to a review queue rather than an automatic rejection — some tools only register after sign-in, or get built at runtime inside a minified bundle where names aren't readable. When that happens, the listing says so rather than guessing.
Every listing that verifies gets a live badge — an embeddable <img> that renders the current tool count and simply stops rendering if the site stops verifying. It can't be faked with a screenshot, because it isn't one.
Who's already there
As of today, the directory holds 121 sites and 363 tools across 12 categories, and the list already includes recognizable names: monday.com, Reebok, Alo Yoga, Away, ZipRecruiter, NETGEAR, QuickNode, Render, Attio, Customer.io, Telnyx, Zuplo, Fever, Usercentrics, Forter, and Coinranking, among others.
To be clear about what that is and isn't: these are companies whose sites our Worker detected exposing WebMCP tools. It's not a partnership, an endorsement, or a case study — it's just evidence that this isn't a hypothetical protocol being adopted by hobby projects. It's being shipped by companies with a lot to lose if their agent-facing surface is broken.
Categories span the expected range — Developer Tools, Social & Communication, Productivity & Business, Travel, Education, Personal, Health & Fitness, and more — each with its own page and its own one-line definition of what belongs there.
The directory dogfoods itself
WebMCP Directory exposes four of its own WebMCP tools — search_webmcp_sites, get_webmcp_site, list_webmcp_categories, prepare_webmcp_submission — so an agent can search the directory the same way it would query any listing inside it. We're listed in our own Developer Tools category, same as everyone else.
What's next
Submission is free, takes a minute, and requires no account. If your site exposes tools through WebMCP, or you're building the integration now, you can add it directly: https://webmcpdirectory.onescales.com/submit
If you want to see who else is already there, browse by category or search the full index at https://webmcpdirectory.onescales.com/
