API
Getting listed#
Register a tool when your page loads:
document.modelContext.registerTool({
name: 'search_flights',
description: 'Search flights between two airports.',
inputSchema: {
type: 'object',
properties: { from: { type: 'string' }, to: { type: 'string' } }
},
execute: async ({ from, to }) => searchFlights(from, to)
})Or mark up a form:
<form toolname="book_table" tooldescription="Book a table">
<input name="party" type="number" required>
</form>Then submit your site. We follow your links and sitemap to find tools on other pages. If tools only register somewhere we can't reach, like a page nothing links to, add that page when you submit.
What we check#
Nothing here is self-reported: we list only the tools we see a site register. We load each page in Chromium with a stand-in for document.modelContext (and Chrome's earlier navigator.modelContext) installed before your scripts run. Once the page settles, we record every tool still registered and every <form toolname>. We never run your tools.
Each check starts at your homepage and crawls up to 12 pages: pages where we found tools before, then links and sitemap entries, with apps, search, docs and pricing first. We follow robots.txt for every page we find on our own.
Listed sites are checked every 24 hours. A tool is removed only when the page it was on loads without it. A site drops off after 3 checks in a row find nothing, and comes back when tools do.
API#
Public JSON, no key, open to any origin.
Read the registry#
curl https://wmcp.ai/api/v1/sites?q=flights
curl https://wmcp.ai/api/v1/sites/render.com/api/v1/sites takes q, sort (popular, newest or tools), limit up to 100, and cursor from the last page's nextCursor. /api/v1/sites/:domain returns every tool with its input schema. Both are cached for up to five minutes.
Submit a site#
Start a check and poll it until its status is no longer running:
curl -X POST https://wmcp.ai/api/v1/scans \
-H 'content-type: application/json' \
-d '{"url": "yoursite.com"}'
curl https://wmcp.ai/api/v1/scans/<id>POST /api/v1/scans takes url and up to 3 extra pages, and answers 202 with the scan's id. The scan lists each page as it's checked. Checks are limited per address and per site; a 429 for a site being checked returns that scan to follow.
This site is agent-ready#
WebMCP Registry exposes its own WebMCP tools, and is listed here like any other site. Results are plain JSON. The reads are marked read-only and untrusted, since they carry listed sites' own text.
search_sitesvia document.modelContextSearch the registry of websites that expose WebMCP tools.get_sitevia document.modelContextGet one listed website and every WebMCP tool it exposes: each tool's name, description, input schema, annotations and the page it was found on.get_submissionvia document.modelContextCheck on a site sent with submit_site: whether the check is still running, each page loaded so far (up to 3 submitted pages plus the ones we find) and the tools found.submit_sitevia the form on /submitSubmit a website to the registry.
See them on wmcp.ai.
Badge#
Shows your verified tool count and updates with every check.
[](https://wmcp.ai/sites/yoursite.com)Our bot#
Checks come from Chromium with this user agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.0.0 Safari/537.36 WebMCPRegistryBot/1.0 (+https://wmcp.ai/api#bot)WebMCPRegistryBot/1.0 checks sites people ask for and re-checks listed sites daily, loading a few pages at a time and following robots.txt. To stop checks or remove your site, email hello@tomo.ai.
About#
Why this exists#
AI agents are starting to use the web for people: searching, booking, buying. Most sites make them click through pages built for humans. WebMCP lets a site tell agents exactly what it can do, as tools with names, descriptions and inputs.
WebMCP Registry is where those sites are found. Agents and developers can see which sites expose tools, what the tools do, and whether they still work.
The spec, browser support and guides are in Resources. How much of the popular web uses WebMCP so far is on Adoption.
Who runs it#
WebMCP Registry is built by the team behind Tomo, a personal AI in iMessage. We rely on sites being agent-ready, so we keep this index open and free for everyone.