{"version":"2.1.242","anchor":"malformed-mcp-capability-declarations-on-published-artifacts","canonical_anchor":"malformed-mcp-capability-declarations-on-published-artifacts","heading":"Malformed MCP capability declarations on published artifacts explain the fix","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/malformed-mcp-capability-declarations-on-published-artifacts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Malformed MCP capability declarations on published artifacts explain the fix\n\nBad MCP capability declarations on a published artifact now come with a diagnosis and a fix.\n\n**What**\n\nPublishing an artifact that declares MCP capabilities incorrectly now gets a specific diagnosis and remedy for each case instead of a generic rejection.\n\n**Details**\n\n- Covers: the declaration not being an object, no servers listed, no tools listed, a connector id used where a server name belongs, a tool name in the server slot, and a name that cannot be declared until it is renamed in claude.ai.\n\n**Evidence**\n\n` is a connector id, which no viewer can resolve`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}