Bad MCP capability declarations on a published artifact now come with a diagnosis and a fix.
What's wrong with this entry?
Publishing an artifact that declares MCP capabilities incorrectly now gets a specific diagnosis and remedy for each case instead of a generic rejection.
- 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.
is a connector id, which no viewer can resolve
Strings lifted out of the shipped bundle, so the claim above can be checked against them.