{"version":"2.1.260","anchor":"mcp-manifest-validation-gains-a-first-party-server-name-coll","canonical_anchor":"mcp-manifest-validation-gains-a-first-party-server-name-coll","heading":"MCP manifest validation gains a first-party server name collision check","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/mcp-manifest-validation-gains-a-first-party-server-name-coll","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### MCP manifest validation gains a first-party server name collision check\n\nArtifact publish now catches local MCP server names colliding with first-party server names.\n\nArtifact publish's MCP host-server manifest validator now detects when a locally-configured server name collides with a first-party server name, rejecting the manifest and reporting it as its own telemetry reason, `first_party_server_collision`.\n\n- Area: Artifacts\n- Names: `first_party_server_collision`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}