Docs for an inspectable WebMCP run.
webmcpify is a WebMCP agent skill for curated core coverage or route-by-route parity. These guides separate what the coding agent builds, what Chrome verifies, and what a client such as ChatGPT can actually see.
SOURCE-TRACEABLE, NOT A SCORECARDStart with the surface you need
Install and run the skill
Pick curated coverage or a route-by-route parity census, approve the manifest, then integrate and verify. INSTALL → Find Site tools in ChatGPT
Check the supported API subset, model, address-bar tool list, page lifetime and account availability in the right order. CLIENT → Read the actual skill contract
Inspect the manifest schema, phase references, vendored runtime and verification template. SOURCE ↗
Pick curated coverage or a route-by-route parity census, approve the manifest, then integrate and verify. INSTALL → Find Site tools in ChatGPT
Check the supported API subset, model, address-bar tool list, page lifetime and account availability in the right order. CLIENT → Read the actual skill contract
Inspect the manifest schema, phase references, vendored runtime and verification template. SOURCE ↗
Coverage is a named choice
| Target | Evidence | Best fit |
|---|---|---|
curated | A reviewed route-to-tool map for selected high-value actions, with written omission reasons. | A focused first integration and smaller active toolsets. |
parity | Every interactive element on every authenticated route maps to a tool or a written reason. | Auditable product-surface equivalence. |
A raw tool count cannot prove parity. No public source or measured client run establishes a universal safe per-page tool count, so client-capacity gaps remain explicit instead of becoming a compatibility claim.
The three proof layers
- Manifest proof: the route map, policy fingerprint, approvals, examples and expected UI deltas are persisted in the target repository.
- Chrome proof: a dedicated headed profile enumerates and executes each tool against the recorded secure verification origin.
- Client proof: the exact client/account shows its supported subset of the page's registrations. In ChatGPT this surface is called Site tools; it currently discovers top-level imperative tools, not declarative forms or iframe registrations.
Current source boundary
Last reviewed 2026-08-31. WebMCP is a moving proposal and client availability changes separately. Runtime claims are checked against the WebMCP draft, Chrome implementation guidance and a real Chrome run. ChatGPT API-subset and model/workspace claims are checked against the official OpenAI Site tools page.