Companies / Omni Analytics / incidents

Omni Analytics: 403 errors connecting to MCP clients

Impact: minorStatus: resolvedStarted Resolved (3.2 h)3 updatesSource: stspg.io (opens in new tab)

Affected components: IrelandEastUsa

Timeline of updates

  1. investigating

    We are currently investigating issues with users seeing 403 errors connecting to MCP clients

  2. monitoring

    We have identified the source of the issue, are implementing a patch and monitoring results

  3. resolved

    The fix has fully deployed now seeing service return to normal What happened: A change we shipped to the MCP OAuth flow yesterday introduced a regression in how authentication tokens were handled by MCP tool calls. The OAuth handshake itself succeeded, so connecting to the MCP server worked, but invoking specific tools (like listing models or running queries) returned a “403 Invalid bearer token” error. Who this affected: Customers using MCP integrations that connect through callbacks.omniapp.co (Claude, ChatGPT, etc). Direct connections from CLI clients are not affected.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Omni Analytics profile · Recent Omni Analytics incidents · Markdown · JSON