<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>WebMCP changelog (independent)</title>
  <subtitle>Dated WebMCP spec, Chrome, Lighthouse and browser-position changes. Not affiliated with the W3C, Google or Chrome.</subtitle>
  <id>tag:webmcp-changelog,2026:feed</id>
  <updated>2026-11-17T00:00:00Z</updated>
  <link rel="self" type="application/atom+xml" href="https://webmcpchangelog.com/feed.xml"/>
  <link rel="alternate" type="text/html" href="https://webmcpchangelog.com/"/>
  <entry>
    <title>Brave Leo AI chat: WebMCP support now default</title>
    <id>tag:webmcp-changelog,2026:e24-1112</id>
    <updated>2026-11-12T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e24-1112"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/56b8e7a74a312c4298858f8211388a536b835339"/>
    <summary>Spec repo implementation-status update (#383). What it breaks: nothing; the first non-Google consumer the repo lists as default-on (the repo's own claim, not independently tested).</summary>
  </entry>
  <entry>
    <title>getTools() traversable scope described</title>
    <id>tag:webmcp-changelog,2026:e23-1111</id>
    <updated>2026-11-11T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e23-1111"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/0c3e712f1743638a299cd8e1a4777ceeaec3cbc8"/>
    <summary>Spec commit "Describe the traversable scope of getTools() (#382)". What it breaks: agents that assume getTools() returns tools from every frame (inference).</summary>
  </entry>
  <entry>
    <title>toolactivated event fires after execute</title>
    <id>tag:webmcp-changelog,2026:e22-1109</id>
    <updated>2026-11-09T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e22-1109"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/f2f2ae2294ede134bf90f9c7b35ab3e163e27379"/>
    <summary>Spec commit "Fire toolactivated event after invoking execute (#371)". What it breaks: nothing existing; code with its own activation signal may double-count (inference).</summary>
  </entry>
  <entry>
    <title>outputSchema added to tools</title>
    <id>tag:webmcp-changelog,2026:e21-1102</id>
    <updated>2026-11-02T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e21-1102"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/6cd745ac8a186122bd3f4aeaeb1d6cfa820251d2"/>
    <summary>Spec commit "Add outputSchema to ModelContextTool and RegisteredTool (#254)". What it breaks: nothing; additive. Validators need to know the new field.</summary>
  </entry>
  <entry>
    <title>Cross-origin tool exposure needs a two-sided opt-in</title>
    <id>tag:webmcp-changelog,2026:e20-1027</id>
    <updated>2026-10-27T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e20-1027"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/6838130ef3e930c8e1a9f98375c13d9133d61aba"/>
    <summary>Spec commit documenting cross-origin tool exposure and two-sided opt-in in Section 6.3.4 (#326). What it breaks: embedders that expect an iframe's tools to reach the parent without the iframe opting in (inference).</summary>
  </entry>
  <entry>
    <title>Declarative (HTML form) API removed from the spec</title>
    <id>tag:webmcp-changelog,2026:e19-1008</id>
    <updated>2026-10-08T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e19-1008"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/14ae813cc4e9fe0d39313f4b1ee5b231746731ad"/>
    <summary>Spec commit "Remove declarative API from the spec for now (#338)". Chrome's docs page (last updated 2026-10-07) still documents it. What it breaks: sites and checkers relying on declarative form annotations have no spec text to cite; Lighthouse's webmcp-form-coverage audit still exists.</summary>
  </entry>
  <entry>
    <title>Chrome origin trial extended from M156 to M162</title>
    <id>tag:webmcp-changelog,2026:e18-0928</id>
    <updated>2026-09-28T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e18-0928"/>
    <link rel="related" href="https://chromestatus.com/api/v0/features/5117755740913664"/>
    <summary>Chrome Platform Status shows an extension stage created 2026-09-28 with last desktop milestone 162. What it breaks: nothing; no calendar end date is published in the sources we can read.</summary>
  </entry>
  <entry>
    <title>Lighthouse 13.5.0: tool-count warning, getTools() fixture</title>
    <id>tag:webmcp-changelog,2026:e17-0918</id>
    <updated>2026-09-18T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e17-0918"/>
    <link rel="related" href="https://github.com/GoogleChrome/lighthouse/releases/tag/v13.5.0"/>
    <summary>Adds a warning when too many tools are registered. What it breaks: pages that register many tools now get a Lighthouse warning. (Release page shows 18 Sep; year inferred.)</summary>
  </entry>
  <entry>
    <title>debugging member added to ToolAnnotations</title>
    <id>tag:webmcp-changelog,2026:e16-0917</id>
    <updated>2026-09-17T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e16-0917"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/8a82bb7896ebee9c4155fe2aed59012ffcae78c2"/>
    <summary>Spec commit "Add debugging member to ToolAnnotations (#253)". What it breaks: nothing; additive annotation.</summary>
  </entry>
  <entry>
    <title>executeTool() input type widened from object to any</title>
    <id>tag:webmcp-changelog,2026:e15-0910</id>
    <updated>2026-09-10T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e15-0910"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/97da8f515427594c856307e3476c0a0db9698fbb"/>
    <summary>Spec commit (#251). What it breaks: TypeScript typings, and agents that assumed the input is always an object (inference).</summary>
  </entry>
  <entry>
    <title>Spec examples updated to the current modelContext API; local-dev flag documented</title>
    <id>tag:webmcp-changelog,2026:e14-0904</id>
    <updated>2026-09-04T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e14-0904"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/16861c67947e1c675eed65e05950ae80bacb11fe"/>
    <summary>Spec commits #284 and #280. What it breaks: tutorials copied from older examples (navigator.modelContext, provideContext) are now out of date.</summary>
  </entry>
  <entry>
    <title>Lighthouse 13.4.1: gatherers switch to document.modelContext</title>
    <id>tag:webmcp-changelog,2026:e13-0720</id>
    <updated>2026-07-20T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e13-0720"/>
    <link rel="related" href="https://github.com/GoogleChrome/lighthouse/releases/tag/v13.4.1"/>
    <summary>WebMCP gatherers now check document.modelContext. What it breaks: pages that only expose the old navigator.modelContext name are likely no longer detected. (Release page shows 20 Jul; year inferred.)</summary>
  </entry>
  <entry>
    <title>WebKit position: oppose</title>
    <id>tag:webmcp-changelog,2026:e12-0611b</id>
    <updated>2026-06-11T13:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e12-0611b"/>
    <link rel="related" href="https://github.com/WebKit/standards-positions/issues/670"/>
    <summary>WebKit standards-positions issue 670 closed with the label "position: oppose". What it breaks: any plan that assumes Safari will implement WebMCP.</summary>
  </entry>
  <entry>
    <title>ModelContextClient removed from the spec</title>
    <id>tag:webmcp-changelog,2026:e11-0611a</id>
    <updated>2026-06-11T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e11-0611a"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/067a1c90b5364b02742ef6ce40e5cf5a6497b445"/>
    <summary>Spec commit "Remove ModelContextClient for now (#205)". What it breaks: tool code written against a ModelContextClient parameter (likely).</summary>
  </entry>
  <entry>
    <title>Chrome blog: sign up for the WebMCP origin trial</title>
    <id>tag:webmcp-changelog,2026:e10-0609</id>
    <updated>2026-06-09T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e10-0609"/>
    <link rel="related" href="https://developer.chrome.com/blog/ai-webmcp-origin-trial"/>
    <summary>Chrome blog, published June 9, 2026: "In Chrome 149, you can sign up for the WebMCP origin trial." What it breaks: nothing; no end date is named.</summary>
  </entry>
  <entry>
    <title>registerTool() now returns a promise</title>
    <id>tag:webmcp-changelog,2026:e09-0608</id>
    <updated>2026-06-08T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e09-0608"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/ec37ec4878e08a166f1460ac40b1ca4ab8096d14"/>
    <summary>Spec commit "Make registerTool() return a promise (#200)"; on 2026-06-17 the promise rejects when the signal is aborted (#202). What it breaks: code that treats registerTool() as synchronous; errors now surface as rejections (inference).</summary>
  </entry>
  <entry>
    <title>modelContext getter moved from Navigator to Document</title>
    <id>tag:webmcp-changelog,2026:e08-0527</id>
    <updated>2026-05-27T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e08-0527"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/c7b5c7023f6e6a1c7a2495946136eb19b3109ae6"/>
    <summary>Spec commit "Move the modelContext getter to Document (#184)". What it breaks: every snippet that calls navigator.modelContext; the spec name is now document.modelContext.</summary>
  </entry>
  <entry>
    <title>Chrome approves an origin trial for M149 to M156; docs published</title>
    <id>tag:webmcp-changelog,2026:e07-0518</id>
    <updated>2026-05-18T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e07-0518"/>
    <link rel="related" href="https://groups.google.com/a/chromium.org/g/blink-dev/c/gmYffo5WOE8"/>
    <summary>Blink-dev: "LGTM to experiment from M149 to M156 inclusive." Estimated desktop ship was M157. What it breaks: nothing; later extended to M162.</summary>
  </entry>
  <entry>
    <title>Lighthouse 13.3.0: agentic browsing category on by default</title>
    <id>tag:webmcp-changelog,2026:e06-0507</id>
    <updated>2026-05-07T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e06-0507"/>
    <link rel="related" href="https://github.com/GoogleChrome/lighthouse/releases/tag/v13.3.0"/>
    <summary>Agentic browsing category added to the default config. What it breaks: every Lighthouse run now includes a WebMCP section. (Release page shows 07 May; year inferred.)</summary>
  </entry>
  <entry>
    <title>Lighthouse 13.2.0: first WebMCP audits</title>
    <id>tag:webmcp-changelog,2026:e05-0501</id>
    <updated>2026-05-01T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e05-0501"/>
    <link rel="related" href="https://github.com/GoogleChrome/lighthouse/releases/tag/v13.2.0"/>
    <summary>Adds webmcp-form-coverage, webmcp-registered-tools and webmcp-schema-validity audits. What it breaks: nothing; Google's first WebMCP audit tooling. (Release page shows 01 May; year inferred.)</summary>
  </entry>
  <entry>
    <title>MCP tool-name rules codified; tool title added</title>
    <id>tag:webmcp-changelog,2026:e04-0409</id>
    <updated>2026-04-09T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e04-0409"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/138091043124a5662333b5863b482fe969de1718"/>
    <summary>Spec commit (#152). What it breaks: tools whose names do not meet the MCP name requirements.</summary>
  </entry>
  <entry>
    <title>registerTool() takes an optional AbortSignal</title>
    <id>tag:webmcp-changelog,2026:e03-0326</id>
    <updated>2026-03-26T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e03-0326"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/6708e3399871458c07ed4cddc04057dec2549955"/>
    <summary>Spec commit (#147); the next day unregisterTool() was removed from the explainer (#156). What it breaks: explainer-era tutorials that use unregisterTool() (inference).</summary>
  </entry>
  <entry>
    <title>provideContext() and clearContext() removed</title>
    <id>tag:webmcp-changelog,2026:e02-0305</id>
    <updated>2026-03-05T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e02-0305"/>
    <link rel="related" href="https://github.com/webmachinelearning/webmcp/commit/fe84c677c381f1f526af6e015f25d34684b0b45c"/>
    <summary>Spec commit (#132). What it breaks: any page using provideContext() or clearContext(); tutorials from before March 2026 still show them.</summary>
  </entry>
  <entry>
    <title>Chrome opens an early preview; DevTrial on desktop 146</title>
    <id>tag:webmcp-changelog,2026:e01-0210</id>
    <updated>2026-02-10T12:00:00Z</updated>
    <link rel="alternate" href="https://webmcpchangelog.com/#e01-0210"/>
    <link rel="related" href="https://developer.chrome.com/blog/webmcp-epp"/>
    <summary>Chrome post, February 10, 2026: "WebMCP is available for prototyping to early preview program participants." What it breaks: nothing; the earliest public Chrome milestone we found.</summary>
  </entry>
</feed>
