This page is for practitioners who want their browser tools to be reachable by AI agents without standing up a server. On this estate, WebMCP means that a published page registers the tool it carries, an agent discovers that registration in one machine-readable file, the agent calls the tool, and the artifact that comes back verifies through a public utility. Each step below draws one link in that loop, and the directory at the end lists every WebMCP surface here with a link you can follow.
A tool page publishes a registration for the kernel it carries. An agent that knows nothing about the site fetches one well-known file and finds that registration by name. The agent calls the tool with its arguments, the page runs it client-side, and the artifact that comes back carries a hash the agent can confirm with the public verify_execution_hash utility before it trusts the answer.
The registration and the discovery file are the contract; nothing about the loop depends on where the agent runs. The signed snapshot beside the discovery file lets a verifier confirm that the registrations it read today are the ones the estate published. Verification closes the loop: a tool that answers without a recomputable artifact is a claim, and this estate ships tools that ship evidence.
Fetch https://ainumbers.co/.well-known/webmcp.json and list the tools registered on the estate.
Registrations sit on real pages, and each page is a doorway an agent (or you) can open. The tool pages of the ChainGraph suite carry one kernel each. Three explainers and the field-notes guide walk the ideas behind the loop, and two demo guides carry working tools with nothing else attached. Every station below links to its page.
The doorway map doubles as the reading order. If you want the ideas first, the doorways explainer shows the three doors to a single tool, the workflow explainer strings tools together, and the Helm explainer covers the served twin of the browser surfaces. If you want your hands on a tool immediately, either demo guide runs one end to end in your browser.
Which pages on ainumbers.co register WebMCP tools, and what does each one carry?
A discovery file is only useful while it stays cheap to read, so every tool registration passes through a lint before it ships. The budget rule set bounds each tool name and description, and the check-webmcp-meta-budgets gate reports any registration that outgrows its budget. Declare the tool within budget, let the lint read it, then ship it into the discovery file.
The gate runs in report mode by default and as a down-only ratchet against a pinned baseline, so the estate can sweep old violations over time while the count never climbs back up. The budgets themselves follow a published community rule set for tool metadata, ported with attribution rather than copied bytes.
Check the WebMCP metadata budgets for the tool I just registered on my page.
Start here if you arrived from the MCP server page or sent someone here from it: that page covers the served MCP endpoint, and this page covers the browser side every WebMCP registration lives on. Each card below is one surface with a real link.
.well-known/webmcp.json holds every tool registration on the estate. This is the one file an agent fetches first.
.well-known/webmcp-signed.json is the signed twin of the discovery file, so a verifier can confirm the registrations it read are the ones published.
The ChainGraph suite carries one registered tool per page, each backed by a kernel whose artifact verifies.
The doorways explainer shows the three doors an agent can use to reach one kernel, with one published input run through all three.
The workflow explainer follows an agent calling several registered tools in sequence, with the receipts at each hop.
The Helm explainer covers the served deployment and how it mirrors the browser registrations.
The field-notes guide records what publishing WebMCP tools in production taught the maintainers.
For the server-side twin of this story, the MCP server page lists the served tools and the handshake; the two pages link to each other on purpose.
.well-known/webmcp.json and confirm every tool you saw on the pages above appears with its name and page.verify_execution_hash.