Custom connector with apostrophe in its NAME never surfaces tools in chats (silent failure; settings unaffected)

**Repro (2 minutes):**

1. Add a custom connector with any working MCP server URL, named `Hello World test` → chats load and call its tools fine.
2. Remove it and re-add the **same URL** named `Guy's Hello test` (note the apostrophe) → chats can no longer find its tools at all — tool search returns only first-party connectors. No error shown anywhere.
3. Re-add apostrophe-free → works again immediately.

**Details:**

- Settings behaves normally throughout: the connector lists its tools, and "Refresh tool list" completes a full `initialize` / `notifications/initialized` / `tools/list` handshake (confirmed via server access logs, user-agent `Claude-User`). Only **chat-side tool discovery** is affected.
- Server is built on the official MCP SDK (`@modelcontextprotocol/sdk`), serving both streamable HTTP and legacy SSE transports. Same behaviour on both.
- Chat transcripts show the model running tool search repeatedly ("Searched available tools") and only ever receiving first-party connectors (Gmail/Calendar/Notion/Airtable) — the custom connector's tools never appear in the searchable set when the connector name contains an apostrophe.
- Tested with a single custom connector configured, all tools set to Always Allow, fresh chats, web claude.ai.

**Impact:**

My connector had carried an apostrophe name ("Guy's Recall Transcripts") for months and worked; it broke silently around 1 July 2026 with zero feedback anywhere in the product. This likely explains a share of the "connected but no tools" reports (e.g. #406, #472). It took a full evening of server-side access logging and A/B connector experiments to isolate the failure to one character in the display name.