{"version":"2.1.251","anchor":"publishing-checks-mcp-server-names-against-what-the-page-act","canonical_anchor":"publishing-checks-mcp-server-names-against-what-the-page-act","heading":"Publishing checks MCP server names against what the page actually calls","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/publishing-checks-mcp-server-names-against-what-the-page-act","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Publishing checks MCP server names against what the page actually calls\n\nPublishing warns when your page calls an MCP server name it never declared.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The undeclared-server scan runs whenever an MCP capability manifest is part of the publish, with no flag or setting to gate it.\n- Calls to an undeclared server would fail for every viewer of the page, which is why the check is a publish-time warning.\n- The rename warning fires only when a registered name and a display name actually differ; a matching pair produces no output.\n- Manifest resolution now returns the resolved list of servers explicitly rather than leaving it implicit for callers to reconstruct.\n\n**Evidence**\n\n`the page calls callTool\/watchTool with`, `rewrote mcp server`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}