Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.317entry #295

Claude Code v2.1.317 ·

MCP legacy-key ownership checks can enforce grants behind a server switch

The check deciding which MCP servers may record an owner with a legacy key was reworked around a new enforcesGrants value

Group of 2 Nothing to try yet In Development
JSON All of v2.1.317
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
In DevelopmentKind: in v2.1.317,
In DevelopmentSection of the release

What

MCP servers are outside programs that give Claude extra tools. Claude Code has a check that decides whether an MCP server may record an owner using an older, legacy kind of key. That check was reworked:

  • The legacy-key owner setup now receives an enforcesGrants value. It is read from a server-controlled switch with a fallback of false, so it is treated as off unless the server turns it on. Before, the setup received only read and claim.
  • The ownership check now tracks claimedMayNotOwn, and it requires enforcesGrants, or a fallback check, before it records a refusal. Before, it used refusedLegacyKeys and a single check.
  • The helper that decides whether to deny now looks at the server's identity, not only its name.

Why

This changes which MCP servers are refused when they use legacy ownership keys. The stricter handling depends on a switch the server controls, so it may not apply to every account.

See this entry in the whole of v2.1.317 →

Feedback