This page calls document.modelContext.registerTool() for two small tools the moment it loads. It exists so you can see what an audit looks like on a page with a live registration: submit https://webmcp-audit.com/demo on the landing page, or read the tools below.
search_docs: read-only search over this site's pages. Input: query (string, 2 to 120 chars), section (enum: audit, builder, spec).
start_audit: queues an audit for a URL, the same thing the landing form does. Input: url (string, format uri). Marked as not read-only.
Checking for document.modelContext in this browser...
The audit loads this page three times: without any flag (what a real visitor's browser exposes), with Chrome's WebMCP flag forced on, and with a capture hook that records the raw registration calls. Because this origin holds no origin-trial token, the deployment status comes back as dark: the tools register, but no real visitor's browser exposes them yet. That is exactly the check a naive "N tools found" audit misses.
Build your own registration with the Builder, then audit the page you put it on.
Paste the URL of this page into the audit form and watch the report arrive.
Go to the audit form