{"version":"2.1.281","anchor":"cached-mcp-server-status-now-also-exposed-as-a-list-of-facts","canonical_anchor":"cached-mcp-server-status-now-also-exposed-as-a-list-of-facts","heading":"Cached MCP server status now also exposed as a list of facts","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cached-mcp-server-status-now-also-exposed-as-a-list-of-facts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cached MCP server status now also exposed as a list of facts\n\nThe status text for a cached MCP server is unchanged but is now also provided as a separate list of facts\n\n**Unclear.** The finding does not say where the separate list of facts is used.\n\n**What**\n\nAn MCP server is an outside tool provider that Claude Code connects to. For one served from cache, the status text stays the same: \"cached\", \"connects on first use\", and sometimes a tool count. That text is now built from a list, and the list is also passed along separately as `facts`.\n\n**Why**\n\nWhat you see does not change.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}