What
When a published page ships MCP capabilities, the publisher now resolves the server manifest and cross-checks it against the code, so name mismatches surface at publish time instead of failing silently for every viewer. It scans the page's scripts and matching sidecar files for callTool and watchTool calls, warns when the server name used in code was never declared, and separately warns when a server's registered name differs from the connector's display name, naming the display name the page should call instead.
Details
- The undeclared-server scan runs whenever an MCP capability manifest is part of the publish, with no flag or setting to gate it.
- Calls to an undeclared server would fail for every viewer of the page, which is why the check is a publish-time warning.
- The rename warning fires only when a registered name and a display name actually differ; a matching pair produces no output.
- Manifest resolution now returns the resolved list of servers explicitly rather than leaving it implicit for callers to reconstruct.
Evidence
the page calls callTool/watchTool with, rewrote mcp server
Strings lifted out of the shipped bundle, so the claim above can be checked against them.