Discovering auth for remote MCP servers should support RFC-9728
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Currently the auto-discovery (recently moved into a dedicated discovery.go) only supports kinda of a home grown mechanism that GETs the protected resource and parses www-authenticate. Modern MCP servers should support RFC-9728 though - we should enhance our discovery.go to first try the standardized method and fall back to our detection as a fallback.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in discovery.go and trace the existing auto-discovery flow that requests the protected resource and parses WWW-Authenticate. Read the RFC-9728 discovery requirements alongside this flow, then verify that the standardized method is attempted first and the existing detection remains the fallback; done means both paths work through the project's relevant checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, backend-api-design, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100