Authentication
Sign in to the Bankrate Products MCP Server with your Bankrate account using OAuth.
Sign in to the Bankrate Products MCP Server with your Bankrate account using OAuth.
The Bankrate Products MCP Server requires OAuth. You sign in once with your Bankrate account, and your MCP client handles tokens for you. With a supported client, you do not need to register an application, manage a client secret, or paste a token into your configuration.
OAuth 2.1 authorization code with PKCE
A Bankrate account
A Client ID Metadata Document, or a client Bankrate registers for you
Your MCP client runs these steps the first time it connects to https://ai.bankrate.com/mcp/products:
401 Unauthorized.auth.bankrate.com.Authorization header of every request. When the token expires, the client refreshes it or asks you to sign in again.Claude Code and Codex sign in out of the box:
/mcp, select bankrate-products-mcp, and choose Authenticate.codex mcp login bankrate-products-mcp.See Quick Start for the commands to add the server.
Other MCP clients need to be set up with Bankrate before they can sign in. Which setup you need depends on whether your client supports Client ID Metadata Documents (CIMD). Check your client's documentation for its OAuth support.
Contact your Bankrate representative with your client's name and its Client ID Metadata Document URL. Once Bankrate approves the client, add the server and sign in when your client prompts you.
Contact your Bankrate representative, and Bankrate will pre-register a client for you. Enter the client ID you receive in your client's OAuth settings, then sign in when your client prompts you.
If you are building your own client, implement the authorization flow in the MCP authorization specification, then follow the setup above.
Rates and products returned by the server are provided by Bankrate. When you show them to users:
disclosure field. Show it word for word alongside the offers or accounts.listingType of SPONSORED_RATE or SPONSORED_AD must be labelled Sponsored.AI clients receive these instructions in the tool descriptions and generally follow them. If you build your own interface on top of the server, apply them yourself.
Every search and rate history response includes a bankrateRequestId. Include it when you report a problem with a result so the Bankrate team can trace the request.