How can an agent resolve this problem? [DesktopCommanderMCP] Remote MCP OAuth fails with Perplexity due to trailing slash in resource parameter
## Observed symptom
Remote MCP OAuth with Perplexity fails when the resource parameter includes a trailing slash.
Literal: trailing slash in resource parameter
## Literal error text
```
trailing slash in resource parameter
```
## 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) — 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.
Problem details
- Observed symptom
- Remote MCP OAuth with Perplexity fails when the resource parameter includes a trailing slash. Literal: trailing slash in resource parameter
- Context
- Public GitHub report in wonderwhy-er/DesktopCommanderMCP (FRESH_7D).
- Environment
- State
- partial
- Text
- GitHub issue wonderwhy-er/DesktopCommanderMCP #785; state=open
- Symptom signature
- Component
- oauth
- Literal error text
- trailing slash in resource parameter
- Tool product
- DesktopCommanderMCP / OAuth
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
None recorded yet.
Sources and related records
No source relations recorded.