Remote MCP (mcp.socket.dev) fails OAuth Dynamic Client Registration in Claude Desktop connectors
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 22/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- nodejs, typescript
- Domaine
- api, authentication
Piste de recherche
The failure is in the remote OAuth Dynamic Client Registration flow for https://mcp.socket.dev/, not in a named source file, so start by checking whether this repo contains the server code at all. Fetch /.well-known/oauth-authorization-server and confirm whether a registration_endpoint is advertised and accepts the redirect URI https://claude.ai/api/mcp/auth_callback. Done means Claude Desktop registers and completes sign-in, or the maintainers confirm the fix belongs in an external service.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Summary
Adding the Socket MCP server as a remote connector in Claude Desktop (https://mcp.socket.dev/) fails at the OAuth Dynamic Client Registration step. Claude can't register with Socket's authorization server, so the connector never authenticates.
Error
Couldn't register with Socket's sign-in service. You can try again, or add an OAuth Client ID in the connector settings. If this persists, share this reference with support: "ofid_03e64c60d9cf295d"
Earlier occurrence (2026-09-17): ofid_325a1efc5e21b2cd
Steps to reproduce
- In Claude, open Customize → Connectors.
- Select Add custom connector, enter
https://mcp.socket.dev/as the server URL (Team/Enterprise plan: added by an org owner via Organization settings → Connectors). - For OAuth Client, leave it on Register automatically (no Client ID supplied).
- Select Connect.
Expected: Socket authorization flow opens, the client registers and the connector connects.
Actual: The registration error above appears; the authorization screen never opens.
Other methods tried (also failing)
mcp-remotevia npx inclaude_desktop_config.json:
OAuth completes, but the redirect to{ "mcpServers": { "socket-mcp": { "command": "npx", "args": ["-y", "mcp-remote@latest", "https://mcp.socket.dev/"] } } }localhost:<port>fails because no server is listening to accept it.- HTTP transport with URL
https://mcp.socket.dev/: clicking Connect doesn't open the OAuth screen at all.
Environment
- Client: Claude Desktop (macOS), Claude Team/Enterprise organization
- Server: remote
https://mcp.socket.dev/ - Last reproduced: 2026-10-14
Context
Reported through Socket support (Zendesk #3814) on 2026-08-21. Support mentioned it split into three engineering tickets, two of which were closed; the remaining DCR failure is still reproducible. The local DXT extension with an API token was suggested as a workaround, but we'd like the remote OAuth connector working so it can be rolled out org-wide via Connectors.
Possibly worth checking: whether the authorization server's registration_endpoint (RFC 7591 Dynamic Client Registration) is advertised in /.well-known/oauth-authorization-server and accepts Claude's redirect URIs (https://claude.ai/api/mcp/auth_callback).
- Langage dominant
- TypeScript
- Étoiles
- 137
- Forks
- 45
- Merge moyen
- 12 j 16 h
- PR mergées (30 j)
- 5
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de SocketDev/socket-mcp
-
[fuzz] fuzz-js job failedOuverte
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
SocketDev/socket-mcp#227 ·
-
Difficulté 4/5 3-5 jours Accessibilité débutants 45/100
SocketDev/socket-mcp#186 · 1 commentaire ·
-
Remote MCP (mcp.socket.dev) rejects freshly-issued OAuth access tokens with 401 invalid_tokenOuverte
Difficulté 4/5 3-5 jours Accessibilité débutants 45/100
SocketDev/socket-mcp#185 · 6 commentaires ·
Toutes les issues de SocketDev/socket-mcp
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
vekexasia/pi-extensible-workflows#374 ·
Les mainteneurs répondent en général sous 2 jours
-
documentation good first issue
Difficulté 2/5 1-3 heures Accessibilité débutants 77/100
Les mainteneurs répondent en général sous 1 jour
-
help wanted linux
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
GiuseppeBellamacina/downtime#19 ·
Les mainteneurs répondent en général sous 1 jour
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
scaleway/ultraviolet#7089 ·
Les mainteneurs répondent en général sous 2 jours
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
Get-Concord-AI/concord-mcp#296 ·
Les mainteneurs répondent en général sous 1 jour