Trust Center

We’re making an update to the authentication process for the Harmonize MCP connector. This change will allow MCP users to authenticate using their Harmonize credentials, providing a single login across Harmonize 3.0 and MCP.

What to expect

If you already have access to Harmonize 3.0:
You do not need to create a new account or accept another invitation. After the release, you will simply reconnect your MCP connector using your existing Harmonize credentials.

If you do not currently have access to Harmonize 3.0:
You will receive an email invitation to join Harmonize after the release. Please accept the invitation and complete your account setup. Your Harmonize account will provide access to both Harmonize 3.0 and the MCP connector.

After the release

All MCP users will need to:

1. Disconnect your existing MCP connection.
2. Reconnect to Harmonize MCP.
3. Enter your Organization ID and Harmonize credentials when prompted.
4. Once authenticated, you can resume using MCP as usual.

Maintenance Window

The release is scheduled for Wednesday, September 23 at 6:30 AM ET. You may experience up to approximately 30 minutes of service interruption while the authentication changes are deployed.

Once the release is complete, we will notify you that the new authentication flow is available and send Harmonize invitations to any MCP users who do not already have an active Harmonize account.

We have released an upgrade to the Harmonize MCP, and here are the highlights:

Card BIN lookups (new). Ask about any BIN ("who issues 401135?") and get the issuing bank, brand, credit vs. debit, consumer vs. business, and country. It can also list the BINs a given bank issues. Daily limits apply, and it accepts BINs only; never card numbers.
Card-present vs. card-not-present, finally usable. These splits now draw on a much better source: volume that used to show as "unknown channel" is now largely attributed correctly.

Safer comparisons. Month-over-month and year-over-year answers use exact calendar months, show the correct currency, and when something can't be compared, the assistant says so instead of guessing. A typo in a merchant name gets "did you mean…?" instead of a misleading $0.00.

Auth0 has fully deprecated and removed the legacy enabled_clients array from Connection objects in the Management API. This field previously controlled which applications could use a given identity connection (e.g., a social or enterprise login). The deprecation reached end-of-life on July 13, 2026, and the change is now live any remaining reliance on the old field will fail or produce errors rather than warnings.

What changed:
Managing which applications are enabled for a connection now requires the dedicated connection-to-client endpoints instead of passing enabled_clients directly on connection GET/PATCH calls:
View: GET /api/v2/connections/{id}/clients
Update: PATCH /api/v2/connections/{id}/clients

Impact on our production environment:
No impact to customer logins. This is an infrastructure/configuration-management change affecting how we administer connections, not authentication itself.

Supabase is a Backend-as-a-Service (BaaS) platform that provides managed PostgreSQL databases, user authentication, object storage, real-time data synchronization, and backend APIs. It is used to securely store and manage application data, authenticate users, and support application functionality.

Vercel is a cloud application deployment and hosting platform used to build, deploy, and deliver web applications through a globally distributed content delivery network (CDN). It provides automated deployments, serverless compute, and edge infrastructure to ensure high availability, performance, and scalability of customer-facing applications.