MCP connector tools (list_connectors, search_mcp_registry) return empty despite active connections

Description

In a Claude Code session, the built-in MCP registry tools mcp__mcp-registry__list_connectors and mcp__mcp-registry__search_mcp_registry both return empty results ({"connectors":[]} / {"results":[]}), even though:

1. The session has multiple MCP connectors actively connected and working (Notion, Slack, Gmail-like email, Google Drive-like storage, Vercel, Chrome browser control) — their tools are present and callable in the session's tool list.
2. A user connected a new connector (Readwise) via the app's Settings → Connectors UI, saw a "Connected to Readwise." success toast, and repeated the OAuth flow multiple times — yet the connector never appeared in list_connectors output, in search_mcp_registry results for "readwise", nor as a callable tool in the session (confirmed via ToolSearch for "readwise", which returned no matches).
3. search_mcp_registry also returned zero results for common, presumably-cataloged connectors (e.g. "github", "linear", "asana", "jira", "figma", "salesforce"), suggesting the tool isn't returning registry data at all in this context rather than genuinely finding no matches.

Expected behavior

• list_connectors should reflect the connectors actually active in the session (or explain why it can't render).
• search_mcp_registry should return real catalog matches for well-known connector names.
• A connector newly authorized via Settings → Connectors should become available as callable tools in new sessions started after the connection completes (or the UI should indicate it isn't yet supported on the Claude Code surface).

Actual behavior

Both tools silently return empty results with no error, making it impossible for the assistant to tell whether a connector genuinely doesn't exist vs. the tool itself is non-functional in this context. This is worse than an explicit error, since it looks like "no connector exists" rather than "this lookup is broken."

Environment

• Surface: Claude Code (cowork/session context with MCP connector tools: mcp-registry, ccd_session, ccd_directory, plus Notion/Slack/Gmail/Drive/Vercel/Chrome connectors)
• Connector attempted: Readwise (shown as "Connected" in Settings → Connectors, but not reflected in session tools or registry search)

Repro steps

1. In a session with active MCP connectors, call mcp__mcp-registry__list_connectors with no filter → returns {"connectors":[],"note":"No installed connectors found — the card did not render. Offer to search the registry (search_mcp_registry)."} despite connectors being active.
2. Call mcp__mcp-registry__search_mcp_registry with keywords like ["github"], ["readwise"], ["linear"] → all return {"results":[]}.
3. Connect Readwise via Settings → Connectors in the app UI (toast confirms "Connected to Readwise."). Start a new session and check for Readwise tools via ToolSearch → no matches.