{"version":"2.1.238","anchor":"stricter-validation-of-cached-mcp-discovery-entries","canonical_anchor":"stricter-validation-of-cached-mcp-discovery-entries","heading":"Stricter validation of cached MCP discovery entries","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/stricter-validation-of-cached-mcp-discovery-entries","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Stricter validation of cached MCP discovery entries\n\nBad cached MCP discovery entries are now deleted and rediscovered rather than reused.\n\n**What**\n\nThe on-disk cache of discovered MCP servers now rejects more bad entries. An entry stored under a key belonging to a different server is deleted rather than used, and an entry that claims to support tools while listing none is no longer treated as fresh, forcing a rediscovery.\n\n**Details**\n\n- The failure threshold and maximum age are now computed at call time rather than fixed constants.\n- The cache directory name `mcp-discovery-cache` is unchanged.\n\n**Evidence**\n\n`discovery-cache: entry keyed for another server, deleting`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}