MCP servers need stable addresses that teams can bookmark, share in docs, and paste into agent configs — but stable URLs must not double as access credentials. This talk walks through building an MCP server where the URL is a resource address and credentials live in OAuth, PKCE, and human-approved grants. Using a production self-hosted MCP registry as the case study, we cover: Protected Resource Metadata for scope advertisement, Dynamic Client Registration for automatic agent enrollment, why token-in-URL sharing breaks down at team scale, how operators narrow requested scopes during grant review, and how connection revocation works without changing the URL. The audience will leave with concrete patterns for separating resource addressing from credential management in their own MCP servers.