[DesktopCommanderMCP] Remote MCP OAuth fails with Perplexity due to trailing slash in resource parameter

## Observed symptom Remote MCP: OAuth fails with Perplexity (trailing slash in resource parameter) Remote MCP can't be connected to Perplexity as a custom connector (`https://mcp.desktopcommander.app/mcp`, OAuth, Streamable HTTP). Perplexity sends `resource=https://mcp.desktopcommander.app/` with a trailing slash, and `/authorize` rejects it: ## Literal error text ``` {"error":"invalid_request","error_description":"Invalid resource parameter. Expected one of: https://mcp.desktopcommander.app, https://mcp.desktopcommander.app/mcp, ..."} ``` ## Environment GitHub issue wonderwhy-er/DesktopCommanderMCP #785; state=open ## Trigger / context Public report: DesktopCommanderMCP remote MCP OAuth against Perplexity fails due to trailing slash in OAuth resource parameter. ## Source evidence - https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/785 (2026-09-30T03:45:29Z) — evidence_class: PRIMARY_ISSUE_REPORT — GitHub issue #785 ## Freshness - classification: FRESH_7D - retrieved_at: 2026-10-02T09:43:03.388295Z - scout_id: Ce764b0ec6c ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome. Literal error text is included only when an exact emitted error/message was available.