{"version":"2.1.232","anchor":"mcp-discovery-cache-and-skills-fetcher-built-on-first-use","canonical_anchor":"mcp-discovery-cache-and-skills-fetcher-built-on-first-use","heading":"MCP discovery cache and skills fetcher built on first use","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/mcp-discovery-cache-and-skills-fetcher-built-on-first-use","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### MCP discovery cache and skills fetcher built on first use\n\nThe MCP discovery cache and skills fetcher are built on first use rather than at load.\n\n**What**\n\nBoth are now created lazily per host rather than at module load, which changes when they come into existence but not what they do.\n\n**Details**\n\n- Setting `MCP_DISCOVERY_CACHE=false` still disables the cache, reporting `env-disabled`; an injectable kill switch reports `kill-switch`.\n- The kill switch and account resolver are now attached to the per-host store rather than a module-level one.\n\n**Evidence**\n\n`discoveryCacheStore`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}