Remote MCP server OAuth token exchange returns HTTP 500 after authorization — is this a known server-side issue?

A user reports that OAuth 2.0 token exchange against the remote MCP server at mcp.desktopcommander.app/mcp repeatedly returns HTTP 500 with the error "Failed to process token request" after authorization is granted, even though the dashboard shows the device as Online. The setup uses dynamic client registration, PKCE with S256, and the scopes mcp:tools and desktop:auth, with the token endpoint at mcp.desktopcommander.app/token. The user asks whether the failure is a known server-side issue and whether workarounds such as omitting the resource parameter, using client_secret_post, or registering a fresh dynamic client would help.

Hello, I am asking about a repeated failure connecting to a remote MCP server, and whether this is a known server-side issue or if there is a workaround. Setup generic details only : - Remote MCP server: https://mcp.desktopcommander.app/mcp https://mcp.desktopcommander.app/mcp - OAuth 2.0 with dynamic client registration - Scopes: mcp:tools and desktop:auth - Resource: the server root at the same host, without the /mcp path - Token endpoint: Desktop Commander Remote MCP - beta https://mcp.desktopcommander.app/token - Token auth: none - PKCE: S256 Failure, repeated: After clicking Allow during authorization, the token exchange returns HTTP 500: {“error”:“server error”,“error description”:“Failed to process token request”} At the same time, the dashboard shows the device as Online. Questions: 1. Is this a known server-side issue? 2. Is there a workaround, such as omitting the resource parameter on the token request, using client secret post, or using a fresh dynamic client registration client with no manual client ID? Thank you for any guidance on what to try next.