MCP config now warns when a value has stray leading or trailing whitespace instead of silently using it.
What's wrong with this entry?
Loading MCP server entries now warns when a value has leading or trailing whitespace, naming the fields involved, because the values are used exactly as written.
- the warning tells you to strip the whitespace rather than doing it for you
- reserved-name rejections now carry a machine-readable
reserved_namecode alongside the existing message
Leading or trailing whitespace in:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.