A dated changelog with a source for every line. Sources checked daily; last checked , last change .
Independent. This site is not affiliated with, endorsed by or sponsored by the W3C, the W3C Web Machine Learning Community Group, Google, Chrome, Microsoft or any browser vendor. WebMCP is a Community Group draft, not a W3C Standard. Always check the linked primary sources.
Current state
Spec status
"Draft Community Group Report, 13 November 2026". Not a W3C Standard and not on the Standards Track. Source: spec · verified 2026-11-17
API entry point
document.modelContext. The getter moved from Navigator to Document on 2026-05-27, so older posts that use navigator.modelContext are out of date. Source: commit c7b5c70 · verified 2026-11-17
Declarative (HTML form) API
Removed from the spec on 2026-10-08 "for now". Chrome's docs page (last updated 2026-10-07) still describes it. Sources: commit 14ae813, Chrome docs · verified 2026-11-17
Chrome origin trial
Started in Chrome 149; approved for M149 to M156, extended to M162 (record created 2026-09-28). Chrome Platform Status still says "Proposed", with TAG, security and privacy reviews "Pending". Chrome has not published a calendar end date in the sources we can read. Sources: Chrome Platform Status (JSON), Blink intent · verified 2026-11-17
Edge origin trial
Trial expiration date shown by Microsoft: March 30, 2027. Source: Edge origin trials · verified 2026-11-17
Chrome's docs name its example extensions (the Example Agentic Chrome Extension and the Model Context Tool Inspector) and say they are separate from Gemini in Chrome. The spec repo lists Brave's Leo AI chat as default-on. We have not confirmed any other consumer. Sources: Chrome docs, commit 56b8e7a · verified 2026-11-17
Latest spec commit
4c7ed44, 2026-11-13, "Update continuations explainer to match the implementation in Blink. (#381)". The repo has no tagged releases. Source: commit history · verified 2026-11-17
Lighthouse
Has WebMCP audits in an "agentic browsing" category since v13.2.0, on by default since v13.3.0. Latest release v13.6.0 (2026-10-27). Source: Lighthouse releases · verified 2026-11-17
Changelog
Newest first. Dates are UTC commit or page dates. Commit links point to the full commit. "What it breaks" is our plain-language reading of the change; where it is an inference the line says "likely" or "inference". Lighthouse release pages show only day and month, so the year is inferred from the release order. We publish nothing we cannot cite, and leave out changes we could not verify.
· Brave Leo AI chat: WebMCP support now default
Spec repo implementation-status update, "Update Leo AI chat WebMCP support from experimental to default (#383)".
Nothing. A status note, and the first non-Google consumer the repo lists as default-on (the repo's own claim, not independently tested).
· Cross-origin tool exposure needs a two-sided opt-in
"Document cross-origin tool exposure and two-sided opt-in in Section 6.3.4 (#326)". Lighthouse v13.6.0 shipped the same day; its WebMCP lines are smoke-test changes only.
Embedders that expect an iframe's tools to reach the parent without the iframe opting in (inference from the title).
· Declarative (HTML form) API removed from the spec
"Remove declarative API from the spec for now (#338)". Chrome's docs page (last updated 2026-10-07) still documents it.
Sites and checkers that rely on declarative form annotations now have no spec text to cite. Lighthouse's webmcp-form-coverage audit still exists in v13.6.0.
Chrome Platform Status extension stage created 2026-09-28: last desktop milestone 162. Reason given: "OT feedback has suggested improvements to the API, which we are implementing." The base trial was M149 to M156.
Nothing; trial tokens stay useful longer. No calendar end date is published in the sources we can read.
"webmcp-registered-tools: warn when exceeding recommended limit"; "webmcp-form-coverage: pass instead of n/a when all forms covered"; "webmcp: support document.modelContext.getTools in fixture". The release page shows "18 Sep"; the year is inferred.
Pages that register many tools now get a Lighthouse warning.
· Lighthouse 13.4.1: gatherers switch to document.modelContext
"webmcp: Refined WebMCP gatherers to check document.modelContext and removed snapshot mode". The release page shows "20 Jul"; the year is inferred.
Pages that only expose the old navigator.modelContext name are likely no longer detected by Lighthouse's WebMCP audits (the release says gatherers check the new name).
WebKit standards-positions issue #670 "WebMCP" closed as completed with the label position: oppose, plus concern labels such as security, privacy, API design and use cases.
Any plan that assumes Safari will implement WebMCP.
· Chrome approves an origin trial for M149 to M156; docs published
Blink-dev "Intent to Experiment: WebMCP" (posted 2026-05-15); reply on 2026-05-18: "LGTM to experiment from M149 to M156 inclusive." The estimated desktop ship was M157. Chrome's docs page shows "Published: May 18, 2026".
Nothing; the trial was later extended to M162 (see 2026-09-28). M157 was Chrome's May estimate, not a commitment.
Adds webmcp-form-coverage, webmcp-registered-tools, webmcp-schema-validity and an agentic browsing category. The release page shows "01 May"; the year is inferred.
Nothing; it is Google's first WebMCP audit tooling.
· Chrome opens an early preview; DevTrial on desktop 146
Chrome post, "Published: February 10, 2026": "WebMCP is available for prototyping to early preview program participants." Blink-dev "Ready for Developer Testing: WebMCP" (posted 2026-02-09, DevTrial on desktop 146); a Chrome engineer replied that it is "an early prototype for developer testing and not an intent to to ship."
Nothing. This is the earliest public Chrome milestone we found.
What the spec says, by feature, with the date it changed. "Chrome" is only filled where a Chrome source says so; we do not have a verified feature-by-Chrome-version matrix, and we say "not verified" rather than guess.
Feature
Spec status (2026-11-17)
Changed
Chrome / tools
Source
document.modelContext
Current entry point
2026-05-27
Lighthouse checks it since v13.4.1 (2026-07-20). Chrome version: not verified
Is it navigator.modelContext or document.modelContext?
The spec moved the getter to Document on 2026-05-27, and Lighthouse checks document.modelContext since v13.4.1. Many tutorials still show navigator.modelContext. See the entry.
Is the declarative (form) API gone?
It was removed from the spec on 2026-10-08 "for now". The spec repo says it is being explored; Chrome's docs page still describes it. Treat it as unstable. See the entry.
When does the Chrome origin trial end?
Chrome Platform Status shows the trial running to Chrome 162 after a 2026-09-28 extension. We could not find a calendar end date from Chrome. Edge's trial page says March 30, 2027.
Will Safari or Firefox ship it?
WebKit's recorded position is oppose (2026-06-11); Mozilla's is neutral (2026-08-05). Neither is a ship decision. Positions can change; check the issues linked in the table.
Who actually calls my tools?
Chrome's docs name its own example extensions, and say they are separate from Gemini in Chrome. The spec repo lists Brave's Leo AI chat as default-on. We have not confirmed other consumers, and we do not claim any.
Is it a W3C standard?
No. It is a Draft Community Group Report from the W3C Web Machine Learning Community Group. Community Group drafts are not on the W3C Standards Track.
Does Lighthouse test WebMCP?
Yes. Since v13.2.0 (2026-05-01) it has WebMCP audits in an agentic browsing category, on by default since v13.3.0. This site is not a checker and scans no sites.
How does this site stay accurate?
Each entry cites a primary source. Each line in the current-state box carries a "verified" date. If we cannot verify a claim, we leave it out. Spotted a mistake? Check the cited source first; corrections are published as new dated entries.