{"version":"2.1.281","anchor":"claudeai-mcp-connectors-cached-discover-responses-are-vali","canonical_anchor":"claudeai-mcp-connectors-cached-discover-responses-are-vali","heading":"claude.ai MCP connectors: cached discover responses are validated","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/claudeai-mcp-connectors-cached-discover-responses-are-vali","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### claude.ai MCP connectors: cached discover responses are validated\n\nclaude.ai MCP connectors now check a cached discover response and ignore it unless it passes three checks\n\n**What**\n\nMCP connectors link Claude Code to outside services set up through claude.ai. When a connector comes with a saved copy of its discover response (`cached_discover_response`), Claude Code now checks that copy before using it. A discover response is the reply a service gives when asked what it offers. The saved copy must:\n\n- pass schema validation, meaning it has the expected shape\n\n- list the supported protocol version\n\n- be declared publicly cacheable, meaning the service allows the copy to be reused\n\nIf any check fails, the saved copy is ignored and the connection goes ahead as if there were no saved copy.\n\n**Why**\n\nA malformed, incompatible or non-reusable saved response is no longer trusted. Instead, the connector connects normally."}