Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
  • 哪里不对？
#223 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
22/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
nodejs, typescript
领域
api, authentication

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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).

主要语言
TypeScript
星标
137
派生
45
平均合并
12 天 16 小时
30 天内合并 PR
5

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

SocketDev/socket-mcp 的其他 Issue

查看 SocketDev/socket-mcp 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。