RightCard
REMOTE · MCP.RIGHTCARD.AI · 2 COMPONENTS · SCANNED SEP 24
Which of your credit cards to use at any store, from verified bank data. No bank login.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- 33% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 600 tokens (~85/item across 7 items; 5 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the RightCard MCP server?
RightCard is a hosted endpoint at https://mcp.rightcard.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.rightcard.ai
claude mcp add --transport http ai-rightcard-mcp 'https://mcp.rightcard.ai/mcp'
{
"mcpServers": {
"ai-rightcard-mcp": {
"url": "https://mcp.rightcard.ai/mcp"
}
}
} {
"servers": {
"ai-rightcard-mcp": {
"type": "http",
"url": "https://mcp.rightcard.ai/mcp"
}
}
} [mcp_servers.ai-rightcard-mcp] url = "https://mcp.rightcard.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-rightcard-mcp": {
"type": "remote",
"url": "https://mcp.rightcard.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-rightcard-mcp --url 'https://mcp.rightcard.ai/mcp' --transport streamable-http
mcp_servers:
ai-rightcard-mcp:
url: "https://mcp.rightcard.ai/mcp" {
"McpServers": {
"ai-rightcard-mcp": {
"Transport": "http",
"Url": "https://mcp.rightcard.ai/mcp"
}
}
} assistant mcp add ai-rightcard-mcp -t streamable-http -u 'https://mcp.rightcard.ai/mcp'
{
"mcpServers": {
"ai-rightcard-mcp": {
"type": "http",
"url": "https://mcp.rightcard.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://mcp.rightcard.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rightcard.ai | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 5fa93e3e71990e3f13eb7fbe243ebb60 |
| SANs: rightcard.ai, mcp.rightcard.ai, *.mcp.rightcard.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.rightcard.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| rightcard.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rightcard.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.rightcard.ai/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
best_card Best card for a store or category ~226
Which of the given cards earns the most at a store (merchant) or for a spend category, today. Returns the card, the honest rate, why, and caveats (merchant-code traps, activation, ties). Base rates + rotating bonuses + built-in card benefits only; a user's personal bank offers live on their phone and are not consulted here.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Spend category when there is no specific store. |
| chosen_categories | object | – | For choose-your-category cards (Citi Custom Cash, BofA Customized, Venmo): card id → the categories the person set. |
| merchant | string | – | Store name, e.g. 'Costco', 'Whole Foods', 'Uber'. Use this OR category. |
| on | string | – | Date (YYYY-MM-DD, UTC) for rotating windows; defaults to today. |
| valuation | string | – | 'cash' counts every point at 1¢ (default). 'points' values points per program at conservative travel values. |
| wallet | array | yes | Card ids the person holds (from search_cards). |
No output schema declared.
No examples provided.
card A card's verified rates ~52
Everything RightCard knows about one card: rates by category, base rate, currency, annual fee, verification status, live rotating windows, and the choose-your-category spec if it has one.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
lookup_merchant How a store is coded ~70
The store's reward category as RightCard's directory files it, its merchant type, and the merchant-code caveat when a category bonus usually will not post there (superstores like Walmart/Target, warehouse clubs like Costco/Sam's). Same ranking the app uses.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
rotating_calendar Rotating 5% windows ~53
Live and upcoming rotating-category windows (Freedom Flex, Discover it, Citi Dividend…) and permanent merchant benefits, from the same verified data as the app. Optionally filter by card id.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | – | – |
No output schema declared.
No examples provided.
search_cards Find card ids ~62
Search RightCard's catalog by card or issuer name to get the ids to pass into best_card. Verified cards first; unverified cards are flagged, never hidden.
| Name | Type | Req | Description |
|---|---|---|---|
| issuer | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
What is the RightCard MCP server?
RightCard is an MCP server listed in the public MCP registry as ai.rightcard/mcp. Which of your credit cards to use at any store, from verified bank data. No bank login. This page covers its hosted endpoint (https://mcp.rightcard.ai/mcp).
Is the RightCard MCP server safe to use?
RightCard scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RightCard MCP server expose?
RightCard exposes 5 tools: best_card, lookup_merchant, search_cards, card, rotating_calendar. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.
Does the RightCard MCP server require authentication?
No. We connected to RightCard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RightCard MCP server still maintained?
RightCard is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.