Living with an API that changes: watch the spec, Chrome Status and the MCP changelog
The WebMCP API has already moved once: from navigator to document. It will change again before any stable release. Instead of finding out from a visitor, record what the sources said on the day the test suite passed and let a script compare. Changed? Run the test suite and read it before touching anything.
2What to watch: spec, Chrome Status, MCP and the SDK
3The recorded baseline and the comparison
4What to do when the watch says MUDOU
Goal: record the baseline from the day the test suite passed and watch the spec, Chrome Status and MCP, with the navigator → document case as an example.
01 · An API that has already changed
Dates read from primary sources on 10/19/2026. Click each milestone.
watch again
Click each block in the diagram to see what it does.
02 · What to watch and where
Public pages, no key and no cost.
1. Spec
The date at the top of the draft and the IDL names (registerTool, getTools, executeTool, toolchange).
Old name coming back or a new method showing up: time to reread.
Sourcewebmachinelearning.github.io/webmcp
2. Chrome Status
The status ("Proposed" on 10/19/2026) and the origin trial versions (149 to 156).
The trial ends at 156: note it in your calendar, along with the token.
SourcePublic Chrome Status JSON, entry 5117755740913664
3. MCP
The versioning page gives the current revision (2026-07-28) and the changelog says what changed.
The Registry is in preview, with a notice of changes and resets: don't depend on it.
4. Your SDK
The kit's server answers server/discover with the revisions it speaks (2026-07-28).
Package version always pinned; upgrading is a decision, with the battery first.
03 · The saved baseline
Generated with --gravar on the day the battery passed. This is what the watcher compares against.
Reads the sources now and compares. With no network, it exits with 3 and concludes nothing.
Terminal · watcher against the kit's baseline
cd ~/projetos/formacao-webmcp-expert-v72/kit
node scripts/vigiar.mjs; echo "saída: $?"
Example from the repository
vigia · base de 19/10/2026 (vigia/base.json)
igual spec_data 2026-10-16
igual spec_superficie document
igual spec_metodos registerTool getTools executeTool toolchange
igual chrome_status Proposed
igual chrome_origin_trial 149–156
igual mcp_versao_atual 2026-07-28
igual sdk_mcp_anuncia 2026-07-28
VIGIA: 7/7 iguais à base · nada a fazer
saída: 0
If you run it after 10/19/2026 and MUDOU shows up, the watcher is doing its job: run the battery and read the change.
vigia · base de 24/09/2026 (vigia/base-curso-antigo.json)
MUDOU spec_data 2026-09-17 → 2026-10-16
igual spec_superficie document
sem base spec_metodos registerTool getTools executeTool toolchange
sem base chrome_status Proposed
sem base chrome_origin_trial 149–156
sem base mcp_versao_atual 2026-07-28
sem base sdk_mcp_anuncia 2026-07-28
VIGIA: 1 mudança(s) em 2 · rode a bateria e releia o que mudou
saída: 1
The old course checked the spec on 09/24/2026, with the draft from 09/17/2026. The watcher flags the difference from today: that was what it was missing so it wouldn't fall behind.
05 · Compare with the old course's baseline
A baseline with only what the old course recorded (spec date and surface). The rest shows up as "sem base".
Terminal · base as of 09/24/2026
cd ~/projetos/formacao-webmcp-expert-v72/kit
node scripts/vigiar.mjs --base vigia/base-curso-antigo.json; echo "saída: $?"
06 · Practice
Watch, see a real change, and save your own baseline. Each exercise ends in a done when.
E1 · Watch against the kit's baseline
3 min
Run the watch. If MUDOU shows up, note what it says: that is the warning working.
Done when:node scripts/vigiar.mjs; echo "saída: $?" → VIGIA: 7/7 iguais à base · nada a fazer and saída: 0 as long as nothing has changed since 10/19/2026; with a change, MUDOU lines and saída: 1.
E2 · The change the old course missed
3 min
Run the watch against the 09/24/2026 baseline.
Done when: The output has MUDOU spec_data 2026-09-17 → 2026-10-16 and saída: 1.
E3 · Your baseline
10 min
After the battery passes on your project (lesson 4), save your baseline and mark the next watch and the end of the origin trial (Chrome 156) on your calendar.
Done when:node scripts/vigiar.mjs --base vigia/minha-base.json --gravar → base gravada em vigia/minha-base.json, and the calendar has both dates.
07 · Lesson quiz
The explanation appears after the answer.
Question 1 of 4
The watch came back with MUDOU spec_data. What is the right order?
Correct
A change in the source calls for proof (the battery) and reading. Re-freezing or re-saving the baseline without reading erases the warning; removing everything is overkill, since the fallback already protects the visitor.
Not this one
A change in the source calls for proof (the battery) and reading. Re-freezing or re-saving the baseline without reading erases the warning; removing everything is overkill, since the fallback already protects the visitor.Review: An API that has already changed
Question 2 of 4
Why does navigator.modelContext appear in this lesson?
Correct
The 10/16/2026 spec only has document.modelContext. The old name serves as an example of an API that changes; in Chromium 156 it does not exist (measured in the kit).
Not this one
The 10/16/2026 spec only has document.modelContext. The old name serves as an example of an API that changes; in Chromium 156 it does not exist (measured in the kit).Review: An API that has already changed
Question 3 of 4
The watch exited with 3 ("SEM CONCLUSÃO"). What does that mean?
Correct
Without reading the sources, the watch says nothing, and code 3 sets this apart from "same" (0) and "changed" (1).
Not this one
Without reading the sources, the watch says nothing, and code 3 sets this apart from "same" (0) and "changed" (1).Review: The saved baseline
Question 4 of 4
Why not depend on the MCP Registry in production today?
Correct
The Registry's own site says "currently in preview" and warns of breaking changes and resets. Publishing there can be useful; depending on it, no.
Not this one
The Registry's own site says "currently in preview" and warns of breaking changes and resets. Publishing there can be useful; depending on it, no.Review: What to watch and where
Quiz complete
You got {a} of {n} right. If you get them all right, the lesson is marked as completed.
Choose an option. The explanation appears after your attempt.
08 · In three sentences
ChangesThe API has already switched from navigator to document and will change again before any stable release.
BaselineSave what the sources said on the day the battery passed.
WatchIt changed: battery, reading, fix; only then are the baseline and the battery re-saved.