# Omni Analytics: 403 errors connecting to MCP clients

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2026-05-14 09:32 UTC · Resolved: 2026-05-14 12:46 UTC · Duration: 3.2 h
- Updates: 3 · Affected components: Ireland, EastUsa
- [Vendor status page: https://stspg.io/hbp2h81cp7nj](https://stspg.io/hbp2h81cp7nj)
- [Company: Omni Analytics](https://rewindex.com/company/omni-analytics.md)

## Timeline of updates

- **investigating** 2026-05-14 09:32 UTC: We are currently investigating issues with users seeing 403 errors connecting to MCP clients
- **monitoring** 2026-05-14 10:15 UTC: We have identified the source of the issue, are implementing a patch and monitoring results
- **resolved** 2026-05-14 12:46 UTC: 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.


---
Canonical: https://rewindex.com/company/omni-analytics/incidents/g57m1vfv7c9w · Markdown: https://rewindex.com/company/omni-analytics/incidents/g57m1vfv7c9w.md · JSON: https://rewindex.com/api/v1/companies/omni-analytics/incidents/g57m1vfv7c9w · Generated 2026-10-18T09:40:47.379Z