{"version":"2.1.221","anchor":"managed-mcp-servers-carry-discover-support-and-a-cached-disc","canonical_anchor":"managed-mcp-servers-carry-discover-support-and-a-cached-disc","heading":"Managed MCP servers carry discover support and a cached discover response","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/managed-mcp-servers-carry-discover-support-and-a-cached-disc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Managed MCP servers carry discover support and a cached discover response\n\nManaged MCP server configs now carry discovery data and strip more server-supplied junk before writing to your config files.\n\n**What**\n\nServer configs fetched from claude.ai now map two new upstream fields onto the local config, and the sanitizer strips more server-supplied blobs before anything is written to disk.\n\n**Details**\n\n- `discover_support` and `cached_discover_response` map to `discoverSupport` and `cachedDiscoverResponse`.\n- Sanitization before writing config now removes `cachedInitResponse`, `cachedDiscoverResponse`, `discoverSupport`, `eligible` and `ineligibleReason`, on top of the existing `tools` and `discoveryCache` stripping, so these do not leak into user config files.\n\n**Evidence**\n\n`cachedDiscoverResponse`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}