Unconfigured MCP server initialization at build time

[slimslenderslacks]

When we build new MCP servers, the Docker image might build successfully, but then we initialize it, bind an MCP client, and extract the prompts, resources and tools. This step can fail if the server is not configured.

Here's an example:

https://github.com/docker/mcp-registry/actions/runs/16819089390/job/47642359771?pr=150

So the build works, but the system won't be able to initialize the server.