MCP tool discovery now logs whether the cache was used, and servers with skills or channels deliberately skip it.
tengu_mcp_discovery_cache Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.221: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.221. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A new event records where a server's tools came from, distinguishing real cache misses from deliberate bypasses.
tengu_mcp_discovery_sourcereportscache_freshorcache_stalefor hits, and a normalized reason otherwise.- Reasons meaning "we connected anyway" collapse to
live. - Genuine misses report
miss_disabled,miss_expired,miss_corrupt,miss_strikeormiss_no_fingerprint. - Two mapped reasons are new opt-outs:
skills-capableandchannel-capableservers deliberately bypass the cache. - Gated on
tengu_mcp_discovery_cache, which falls back to enabled.
miss_no_fingerprint
Strings lifted out of the shipped bundle, so the claim above can be checked against them.