Omni Analytics experienced a 3.3-hour outage where users encountered 403 "Invalid bearer token" errors when using MCP integrations through callbacks.omniapp.co (Claude, ChatGPT, etc.), affecting the EastUsa and Ireland regions. The issue was caused by a regression in OAuth token handling for MCP tool calls that was introduced in a recent deployment, preventing users from performing actions like listing models or running queries despite successful initial connections. The service was restored after deploying a patch to fix the authentication token handling.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
We have identified the source of the issue, are implementing a patch and monitoring results
We are currently investigating issues with users seeing 403 errors connecting to MCP clients
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with