You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two defects in that flow make it fail for some servers.
1. Fallback metadata has no registration endpoint
What happens
When the server does not publish /.well-known/oauth-authorization-server, get_oauth_server_metadata builds default metadata as described by the MCP spec. The registration URL is passed as register_endpoint, but authlib's AuthorizationServerMetadata (RFC 8414) names it registration_endpoint. metadata.registration_endpoint is therefore None, and build_oauth_params without a client_id/client_secret calls async_client.post(None, ...):
TypeError: Invalid type for url. Expected str or httpx2.URL, got <class 'NoneType'>: None
What should happen
Dynamic client registration should be attempted at {server_url}/register, as the MCP 2025-03-26 fallback rules say.
Activity