anthropics / anthropics/claude-ai-mcp

Unable to Re-Authorize DXB Interact Brain MCP with Existing Account

Offen
#993 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
auth bug server-developer-report
Vorherrschende Sprache
Keine Sprachdaten
Sterne
471
Forks
77
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### MCP server URL

https://brain.dxbinteract.com/mcp

### Where does the issue occur?

When pressing the Connect button

### Transport used

streamable-http

### Client registration type

My server does not have auth

### SSE only: Does your server return the expected status code for POST requests?

Not applicable (my server does not use SSE)

### When did you last reproduce this?

2026-09-07 00.20 Dubai

### Browser and OS

Chrome

### Describe the issue

### Issue details

```shell
I installed the DXB Interact Brain MCP and successfully authorized it using my account. Everything worked perfectly at first.

However, after a few days, I can no longer authorize the MCP. It now requires me to use a new business email address.

Does this mean I need to create a completely new account in order to continue using the MCP? If so, this creates a problem because I will not be able to link my broker card to the new account, as it is already linked to my existing DXB Interact account.

Could you please advise what I need to do to restore access to the MCP using my existing account?

There was no information in the MCP connection or setup instructions indicating that I would need to switch to a different account or use a new business email address after the initial authorization.
```

### Expected behavior

I expected the MCP to continue authorizing with my existing DXB Interact account, using the same email address I successfully used during the initial setup.

I also expected to be able to reconnect or re-authorize the MCP without creating a new account, especially since my broker card is already linked to my existing account.

### Logs from your server

```shell

```

### Additional context

_No response_

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

No repository file, test, or implementation entry point is identified. Start by reproducing the failure from the MCP server URL with Chrome, the streamable-http transport, and the Connect button, then inspect the authorization flow and available logs. Done means restoring authorization with the existing account or documenting the confirmed account requirement and recovery path.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Bereich
api, authentication
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Aktiv
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.