{"version":"2.1.265","anchor":"new-mcp-manifest-publish-failure-reasons-opaque-mcp-server","canonical_anchor":"new-mcp-manifest-publish-failure-reasons-opaque-mcp-server","heading":"New MCP-manifest publish failure reasons: opaque_mcp_server_id and unknown_mcp_tool","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-mcp-manifest-publish-failure-reasons-opaque-mcp-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New MCP-manifest publish failure reasons: opaque_mcp_server_id and unknown_mcp_tool\n\nArtifact publish telemetry gains two new MCP failure reasons: opaque_mcp_server_id and unknown_mcp_tool\n\n**What**\n\nWhen artifact publishing checks an MCP (Model Context Protocol) server manifest and fails, it now records two additional, more specific failure reasons alongside the existing ones like `host_server_unavailable` and `unresolved_mcp_server`:\n\n- `opaque_mcp_server_id`\n\n- `unknown_mcp_tool`\n\n**Why**\n\nMore specific failure reasons make it easier to tell exactly why an artifact's MCP manifest was rejected, building on earlier additions to this same validation chain such as the first-party server name collision check.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}