Notes from the build — what held, what broke, and what the work taught us about the agentic web.
The hard part wasn't registering tools — it was making independently built provider surfaces predictable enough for a consumer to reason about. The contract I pulled out, and why each rule earned its place. Ships as @zioladev/provider-tools.
A WebMCP tool may be local to one page, but a useful user task often is not. Here is what changed when one browser consumer had to preserve state and execute across four provider origins — discovery, timing, evidence, and clear action boundaries.
Read the field note →