Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.248 Home All releases olderv2.1.247 v2.1.250newer
Claude Code v2.1.248

A classification scheme for why a connector tool is unavailable

Under the hood
Useful2 Signal2
MCP

Unavailable connector tools are now sorted into eleven specific reasons.

What

New helpers sort an unavailable MCP-backed tool into one of eleven reasons: blocked by policy, blocked by the org, denied, disabled, not configured, reconnecting, needs authentication, disconnected, authentication just completed, not offered, or withdrawn. Two predicates separate permanent blockage from states that may clear on their own.

Details
  • Per-server tool permission entries set to "blocked" are detected as their own case.
  • Authentication-related tools are recognised by the suffix of their name.
  • Which surfaces display these reasons is decided elsewhere in the build.
Evidence

"complete_authentication"

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.248 →