Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Remote MCP (mcp.socket.dev) fails OAuth Dynamic Client Registration in Claude Desktop connectors

Abierto
#223 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
nodejs, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

  1. In Claude, open Customize → Connectors.
  2. 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).
  3. For OAuth Client, leave it on Register automatically (no Client ID supplied).
  4. 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-remote via npx in claude_desktop_config.json:
    {
      "mcpServers": {
        "socket-mcp": {
          "command": "npx",
          "args": ["-y", "mcp-remote@latest", "https://mcp.socket.dev/"]
        }
      }
    }
    
    OAuth completes, but the redirect to 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).

Lenguaje dominante
TypeScript
Estrellas
137
Forks
45
Merge medio
12 d 16 h
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de SocketDev/socket-mcp

Todos los issues de SocketDev/socket-mcp

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.