Guides

Authentication

Sign in to the Bankrate Products MCP Server with your Bankrate account using OAuth.

Before you begin

Authentication is currently disabled in production

Requests to https://ai.bankrate.com/mcp/products currently succeed without signing in. This page describes how access works once authentication is turned on. Set up your client now so it keeps working when it is.

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.

Authentication flow

OAuth 2.1 authorization code with PKCE

Account

A Bankrate account

Client registration

A Client ID Metadata Document, or a client Bankrate registers for you

How sign-in works

Your MCP client runs these steps the first time it connects to https://ai.bankrate.com/mcp/products:

  1. The client sends a request without a token, and the server responds with 401 Unauthorized.
  2. The client reads the server's protected resource metadata to discover the authorization server, auth.bankrate.com.
  3. The client identifies itself with a Client ID Metadata Document, a URL that describes the client. Bankrate must have approved the client; see Other clients.
  4. Your browser opens to the Bankrate sign-in page. Sign in with your Bankrate account and approve access.
  5. The client receives an access token and sends it as a Bearer token in the Authorization header of every request. When the token expires, the client refreshes it or asks you to sign in again.

Connect your client

Claude Code and Codex sign in out of the box:

  • Claude Code: add the server, then run /mcp, select bankrate-products-mcp, and choose Authenticate.
  • Codex: add the server, then run codex mcp login bankrate-products-mcp.

See Quick Start for the commands to add the server.

Other clients

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.

Your client supports CIMD

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.

Your client doesn't support CIMD

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.

Present results

Rates and products returned by the server are provided by Bankrate. When you show them to users:

  • Credit Bankrate as the source of the rates and products.
  • Show the disclosure. Search responses include a disclosure field. Show it word for word alongside the offers or accounts.
  • Label sponsored offers. Mortgage and home equity offers with a 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.

Report a problem

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.

Troubleshooting