Bad cached MCP discovery entries are now deleted and rediscovered rather than reused.
What's wrong with this entry?
The 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.
- The failure threshold and maximum age are now computed at call time rather than fixed constants.
- The cache directory name
mcp-discovery-cacheis unchanged.
discovery-cache: entry keyed for another server, deleting
Strings lifted out of the shipped bundle, so the claim above can be checked against them.