{"version":"2.1.219","anchor":"mcp-config-warns-about-stray-whitespace-in-values","canonical_anchor":"mcp-config-warns-about-stray-whitespace-in-values","heading":"MCP config warns about stray whitespace in values","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/mcp-config-warns-about-stray-whitespace-in-values","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### MCP config warns about stray whitespace in values\n\nMCP config now warns when a value has stray leading or trailing whitespace instead of silently using it.\n\n**What**\n\nLoading 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.\n\n**Details**\n\n- the warning tells you to strip the whitespace rather than doing it for you\n- reserved-name rejections now carry a machine-readable `reserved_name` code alongside the existing message\n\n**Evidence**\n\n`Leading or trailing whitespace in:`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}