{"version":"2.1.247","anchor":"mcp-server-protocol-field-is-validated","canonical_anchor":"mcp-server-protocol-field-is-validated","heading":"MCP server protocol field is validated","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/mcp-server-protocol-field-is-validated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### MCP server protocol field is validated\n\nStored MCP server records now reject odd characters in the protocol field.\n\n**What**\n\nThe stored MCP server record's protocol field is now restricted to printable ASCII with the same length cap as its neighbouring fields, instead of accepting any string.\n\n**Evidence**\n\n`\/^[\\x20-\\x7e]+$\/`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}