{"version":"2.1.317","anchor":"mcp-status-livereply-docs-no-config-and-size-fallback","canonical_anchor":"mcp-status-livereply-docs-no-config-and-size-fallback","heading":"Oversized MCP status replies send a tool count instead of failing","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-status-livereply-docs-no-config-and-size-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Oversized MCP status replies send a tool count instead of failing\n\nWhen an mcp_status live reply would be too large, it drops tool lists and server details and sends a toolCount instead\n\n**Unclear.** Only the description is known to have changed, so it is not clear whether oversized replies already shrink in practice.\n\n**What**\n\nApps built on Claude Code can send an `mcp_status` request to ask about MCP servers, the outside programs that give Claude extra tools. A live reply that would be too large now shrinks instead of failing:\n\n- Each server's list of tools is replaced with `toolCount`, the number of tools.\n\n- `serverInfo` and `capabilities` are left out. When they are missing, that means unknown, not empty.\n\n- The request's description now also mentions `mcp_status_no_config_v1`.\n\nBefore, the reply included each server's configuration, and an oversized reply was an error.\n\n**Why**\n\nApps connected to many MCP servers with many tools should stop getting errors back from status checks. If you read these replies, treat a missing `serverInfo` or `capabilities` as unknown.\n\n- Area: MCP\n- Names: `mcp_status`, `liveReply`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}