Copy PageLists the current customer's own active MCP connections.get https://api.banking.netevia.dev/api/mcp/connectionsHeadersacceptstringenumDefaults to application/jsonGenerated from available response content typesapplication/jsontext/jsontext/plainAllowed:application/jsontext/jsontext/plainResponse 200SuccessUpdated about 1 hour ago Registers a custom MCP client (RFC 7591 shape) for anything not on the curated vendor list. This used to be an anonymous endpoint (McpOAuthController.Register) - open, unauthenticated Dynamic Client Registration is what the RFC describes, but it turned out to be a phishing vector: an anonymous caller could mint a client under any client_name and HTTPS redirect_uri, then send a victim a same-domain connect/mcp/authorize link before the victim ever intended to connect anything. Requiring the caller's own bank session first means a client can now only ever be created by someone already authenticated as themselves - it costs the fully anonymous, self-registering client flow the RFC describes, but nothing today depends on that.Disconnects one of the current customer's own connections - revokes any tokens already issued for it. The client itself stays registered so the customer can reconnect through it later. Only ever affects the caller's own connection.Did this page help you?YesNo