We operate Passkey, a hosted MCP security gateway (v2n2x). Users connect remote MCP servers through Passkey, which brokers OAuth and holds tokens in a KMS-encrypted vault with per-connection least-privilege scoping and a consent prompt on every exchange. Connecting Vercel MCP (https://mcp.vercel.com) is blocked at vercel.com/oauth/authorize with "redirect URIs are not approved" — our gateway redirect isn't on the Vercel MCP OAuth client allowlist.
Please allowlist our redirect URI (or issue us an approved MCP client_id): - redirect_uri: https://gateway-prod.v2n2x.com/gateway/oauth/callback - flow: authorization_code + PKCE (S256), public client (token_endpoint_auth_method: none) - scope: openid offline_access · resource: https://mcp.vercel.com/ Passkey already connects many remote MCP providers (GitHub, Atlassian, Linear, Supabase, etc.) via standard OAuth/DCR; Vercel's approved-client allowlist is the only blocker. Happy to complete any client security review. Thank you!