MCP Connect (OAuth 2.1)

One-click **Connect** for MCP clients (ChatGPT, Cursor, Claude Desktop): instead of pasting an X-API-Key, the client runs the OAuth 2.1 authorization-code + PKCE flow against FinRadar's own login and gets a short-lived token. Discovery follows RFC 9728 (protected-resource) + RFC 8414 (authorization-server); the resource is `/api/mcp`. ChatGPT uses its published HTTPS Client ID Metadata Document, which FinRadar accepts only from the exact trusted OpenAI URL and validates before authorization. Other clients can continue using the existing Dynamic Client Registration endpoint. Both auth methods work side-by-side (dual auth) — existing X-API-Key clients are unaffected. Select FinRadar's MCP server in your client and click Connect to use it. On the dedicated ChatGPT publication hostname, FinRadar exposes seven focused direct operations: institutional-manager lookup, institutional portfolio, company insider transactions, SEC filing search, beneficial-ownership filing search, as-stated company statements and company financial time series. ChatGPT invokes the selected operation directly; `search_tools` and `call_tool` are not exposed there. Existing clients on `api.finradar.ai`, including Codex, Claude and Cursor, keep the current startup catalogue with the company statement tool, financial time series, `search_tools` and `call_tool`. Search returns at most five matching full definitions from the same API-generated registry, and `call_tool` executes the selected definition. Both profiles use the same generated operations, authentication, permissions, API parameters, financial results and token costs.