{"version":"2.1.290","anchor":"mcp-tool-tiering-no-longer-reads-the-plugin-record","canonical_anchor":"mcp-tool-tiering-no-longer-reads-the-plugin-record","heading":"Plugin-provided MCP tools are ranked from their recorded plugin source","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-tool-tiering-no-longer-reads-the-plugin-record","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Plugin-provided MCP tools are ranked from their recorded plugin source\n\nClaude Code now ranks MCP tools using the plugin source stored on each tool instead of looking up the plugin's record\n\n**Unclear.** It is not clear whether any tool actually ends up in a different tier.\n\n**What**\n\nMCP (Model Context Protocol) is a standard way to connect outside tools to Claude Code. Claude Code places MCP tools into tiers based on which provider they come from. To find the provider, it now reads the plugin source stored on the tool itself.\n\nBefore, it waited to look up the plugin's record. If that lookup failed, it fell back to the 'prepend' tier.\n\n**Why**\n\nThis may change which tier some MCP tools end up in.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}