RightCard MCP (ai.rightcard/mcp)

RightCard MCP is an MCP server that helps agents choose which credit card to use at a store. It determines the appropriate card using RightCard’s bank-published, two-source-verified reward data, avoiding any need for bank login. Inputs are card ids and a store name, and the server returns an answer.

🛠️ Key Features

Uses RightCard bank-published, two-source-verified reward data
Requires card ids and a store name as inputs
No bank login, no account, and nothing stored
Returns an agent-friendly “which card should pay here” recommendation
Notes merchant-code caveats (e.g., Costco as a warehouse club)

🚀 Use Cases

Agent decision-making for credit-card selection per merchant
Automated payment routing based on verified rewards data

⚡ Developer Benefits

Integrates into MCP-based agent workflows
Avoids handling bank credentials
Uses reward data aligned with the RightCard iOS app

⚠️ Limitations

Merchant classifications can affect rewards posting (e.g., Costco vs. grocery bonuses)

RightCard MCP

The card-selection oracle for agents: which of your credit cards should pay here? Answers come from RightCard's bank-published, two-source-verified reward data — the same data the RightCard iOS app uses.

No bank login. No account. Nothing stored. You pass card ids and a store name; you get an answer.
Honest by construction: merchant-code caveats (Costco is a warehouse club, so the grocery bonus won't post), rotating quarters with activation flags, ties named, points valued per program.
Cash value by default; valuation: "points" for conservative travel values.

Use it

Hosted (stateless Streamable HTTP):

code

https://mcp.rightcard.ai/mcp

Local (stdio, nothing leaves your machine except a read of the public catalog):

code

npx rightcard-mcp

Claude Desktop / Claude Code / Cursor config:

json

{ "mcpServers": { "rightcard": { "command": "npx", "args": ["-y", "rightcard-mcp"] } } }

Tools

tool	what it answers
`best_card`	which of the given cards earns most at a store or category, today, with caveats
`lookup_merchant`	how a store is coded (category, merchant type, MCC-trap caveat)
`search_cards`	find card ids by name/issuer; verified first, unverified flagged
`card`	one card's verified rates, rotating windows, choose-your-category spec
`rotating_calendar`	live + upcoming rotating windows and permanent merchant benefits

Try: "I have the Amex Gold, Freedom Flex and Citi Double Cash. Which one at Costco?"

Parity with the app

src/engine.ts is a port of the iOS app's Swift engine. fixtures/engine_golden.json holds 3,100+ answers produced by the Swift code over the real catalog and merchant directory; npm test fails if the port disagrees on any of them. Offers (a user's personal bank offers) are deliberately not part of this server — they live on the phone.

Privacy

The hosted server logs request counts only. No identifiers, no cookies, no storage. Full policy: https://rightcard.ai/privacy

wallet	array	required	Card ids the person holds (from search_cards).
merchant	string	optional	Store name, e.g. 'Costco', 'Whole Foods', 'Uber'. Use this OR category.
category	string	optional	Spend category when there is no specific store.
valuation	string	optional	'cash' counts every point at 1¢ (default). 'points' values points per program at conservative travel values.
on	string	optional	Date (YYYY-MM-DD, UTC) for rotating windows; defaults to today.
chosen_categories	object	optional	For choose-your-category cards (Citi Custom Cash, BofA Customized, Venmo): card id → the categories the person set.

query	string	required
issuer	string	optional
limit	integer	optional

RightCard

RightCard MCP (ai.rightcard/mcp)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

best_card

lookup_merchant

search_cards

card

rotating_calendar

RightCard MCP

Use it

Tools

Parity with the app

Privacy

Install

Related servers