modelcontextprotocol / modelcontextprotocol/registry
Consider `/.wk/mcp-registry-auth` => `/.wk/mcp/registry-auth`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
(Not really sure if this is a GA blocker, but wanted to raise attention, just in case.)
The MCP Registry currently uses /.well-known/mcp-registry-auth for DNS-based auth:
However, there is a desire to support /.well-known/mcp/server.json. For example, see https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1649.
So should we change /.well-known/mcp-registry-auth to /.well-known/mcp/registry-auth?
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 with docs/explanations/namespacing.md around line 26 and review modelcontextprotocol#1649 for the proposed server.json path. Compare the existing mcp-registry-auth convention with the proposed nested path and determine whether the change is required for compatibility. Done means the path decision is agreed and the relevant registry documentation or specification references reflect it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100