claude-in-chrome MCP connector absent (Remote env, 24h+)

Environment: Claude Code Remote (cloud environment), environment_id: env_011111111111111111111117

Summary:
The claude-in-chrome browser MCP server has been unavailable in this environment for 16+ hours, starting the evening of July 7, 2026. It is not returning connection errors on individual tool calls — the server is simply absent, as if it were never registered.

Evidence:

ToolSearch for any mcp__claude-in-chrome__* tool (e.g. tabs_context_mcp, navigate, get_page_text) consistently returns "No matching deferred tools found."
A full ListMcpResourcesTool call (no server filter) lists other connected MCP servers but claude-in-chrome does not appear at all — not as a failed/disconnected entry, just missing entirely.

Timeline:

Connector first observed down: evening of July 6–7, 2026 (UTC).
Anthropic's status page (status.claude.com) shows a resolved incident, "Elevated errors on Claude.ai," involving OAuth login issues for Claude Code, resolved July 6 at 23:46 UTC.
Support (Fin AI agent, ticket #215474986535484) confirmed the general incident resolution but the connector remained down. I tested this directly with fresh scheduled-task sessions (not a stale/reused session) at 03:20 UTC and 03:41 UTC on July 8 — both well after the incident's resolution time — and both came back with the tools still completely absent.
As of 12:29 UTC July 8, still down (~16 hours).

Impact:
Blocks all browser-dependent scheduled tasks in this environment from completing (Kickserv report reading, checklist automation, reminder drafting for a small business relying on this environment).

What I'd like investigated:
Support suggested this may be a provisioning issue specific to this environment — the connector possibly never being (re-)added or re-authenticated after the incident, rather than a simple reconnection failure. Could someone check whether env_011111111111111111111117's browser/Chrome MCP connector is actually configured/provisioned correctly?