Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release
What
When 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:
opaque_mcp_server_id
unknown_mcp_tool
Why
More 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.
