feat: send client_uri and logo_uri in OAuth client registration - #1877
Merged
Aaronontheweb merged 2 commits intoAug 11, 2026
Merged
Conversation
RFC 7591 dynamic client registration now advertises the Netclaw home page and logo so authorization servers can display a recognizable consent screen. client_uri points at netclaw.dev and logo_uri at the square Netclaw icon in the public brand repo.
Aaronontheweb
added
mcp
Aaronontheweb
removed
the
providers
Collaborator
Author
|
This change only impacts our client registration metadata with MCP servers |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
RFC 7591 dynamic client registration (
McpOAuthClientRegistrar) now includes two optional metadata fields in the registration request:client_uri—https://netclaw.devlogo_uri—https://raw.githubusercontent.com/netclaw-dev/netclaw-brand/dev/logo/netclaw-icon-purple.png(square PNG icon)Why
Authorization servers display these on the consent screen. Without them, Netclaw shows up as a bare
client_name: netclawwith no link or logo — indistinguishable from any other OAuth client. Providers that support RFC 7591 (e.g. TextForge) will now render a recognizable Netclaw identity.How
ClientUri/LogoUriconstants toMcpOAuthClientRegistrarclient_name/client_uri/logo_uriand assert themValidation
dotnet build— 0 warnings, 0 errorsMcpSdkOAuthFlowIntegrationTests— 23/23 passedimage/png)