{"version":"2.1.283","anchor":"pages-with-dynamic-mcp-connector-declarations-are-flagged-as","canonical_anchor":"pages-with-dynamic-mcp-connector-declarations-are-flagged-as","heading":"Pages that can request any connector are now flagged as unverified","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/pages-with-dynamic-mcp-connector-declarations-are-flagged-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Pages that can request any connector are now flagged as unverified\n\nWhen a page can ask viewers for any MCP connector, its permission changes say so and Claude is told to warn you those integrations are unverified\n\n**Unclear.** It is not clear where this instruction is given to Claude or whether page publishing is available to everyone.\n\n**What**\n\nA page can declare which MCP connectors it uses. A connector links Claude to an outside service that provides tools. When that declaration becomes dynamic, the page can ask each viewer for any connector by name while it runs, and the viewer approves each one on first use. In that case:\n\n- The list of permission changes shows \"mcp (any connector the viewer approves)\". Before, the only wording was \"mcp (more servers or tools)\".\n\n- Claude is instructed to tell you which connectors and tools the page calls, and that those integrations are unverified.\n\n**Why**\n\nThis stops Claude from implying, when a page is published, that connectors nobody has checked are verified.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}