Skip to content

Consider /.wk/mcp-registry-auth => /.wk/mcp/registry-authΒ #744

@jonathanhefner

Description

@jonathanhefner

(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:

- HTTP verification: File at `https://company.com/.well-known/mcp-registry-auth`

However, there is a desire to support /.well-known/mcp/server.json. For example, see modelcontextprotocol/modelcontextprotocol#1649.

So should we change /.well-known/mcp-registry-auth to /.well-known/mcp/registry-auth?

Metadata

Metadata

Assignees

No one assigned

    Labels

    go-live blockerThis issue is one we need to address prior to initial go-live

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions