# creditcards.best (remote · mcp.creditcards.best)

Search, compare and estimate rewards across US credit cards. Verified fees, APRs and bonuses.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `creditcards.best`: 68/100, [markdown](https://verifymcp.io/servers/best-creditcards-mcp/creditcards.md), [page](https://verifymcp.io/servers/best-creditcards-mcp/creditcards)
- remote · `mcp.creditcards.best`: 68/100 (this document), [markdown](https://verifymcp.io/servers/best-creditcards-mcp/mcp.md), [page](https://verifymcp.io/servers/best-creditcards-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.creditcards.best`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1118 tokens (~139/item across 8 items; 6 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http best-creditcards-mcp https://mcp.creditcards.best/
```

### Codex

```toml
[mcp_servers.best-creditcards-mcp]
url = "https://mcp.creditcards.best/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "best-creditcards-mcp": {
      "type": "remote",
      "url": "https://mcp.creditcards.best/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add best-creditcards-mcp --url https://mcp.creditcards.best/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  best-creditcards-mcp:
    url: "https://mcp.creditcards.best/"
```

### Other

```json
{
  "mcpServers": {
    "best-creditcards-mcp": {
      "type": "http",
      "url": "https://mcp.creditcards.best/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 65, 0)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 55% → 63%
- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 65)

First indexed and scored.

## MCP tools (6)

### `search_cards` (~391 tokens)

Search credit cards

Filter the US credit-card dataset by product type, rewards currency (program name or kind), issuer, annual fee, foreign-transaction fee, signup-bonus value, credit band, or curated category. Searches ONLY issuer-verified cards by default, because unverified stubs carry null for most filterable fields and a null is not a zero. Set verified:false for the stubs, or verified:null to search everything knowingly. Returns at most 25 summaries unless you raise `limit`; `total` is the full match count and `truncated` says whether you are seeing all of it. Rankings reflect fit, not placement.

Input parameters:

- `category` (string): Curated slug, e.g. 'best-cash-back-credit-cards'
- `creditBand` (string): Only cards a user with this credit band typically qualifies for
- `isBusiness` (boolean)
- `issuer` (string): Issuer name, partial match (e.g. 'Chase')
- `limit` (integer): Max cards to return (default 25). Check `truncated` before treating the list as complete.
- `maxAnnualFee` (number)
- `minSignupValueUsd` (number): Minimum estimated signup-bonus cash value
- `noForeignTransactionFee` (boolean)
- `productType` (array)
- `rewardsCurrency` (string): Program name, partial match, by its own name: 'AAdvantage' not 'American', 'SkyMiles' not 'Delta', 'Bonvoy', 'Avios'.
- `rewardsCurrencyType` (array): Kind of loyalty currency earned. Use this for airline or hotel cards; it is not a productType.
- `sort` (string)
- `verified`: Defaults to true (issuer-verified only). false = only the unverified stubs seeded from the open reference. null = the whole corpus, nulls and all.

### `get_card` (~65 tokens)

Get one card

Full detail for a single card by id (slug), including earn rates, credits, eligibility, sources and lastVerified. The apply link is our tracked redirect, not the issuer URL.

Input parameters:

- `id` (string, required): Card slug, e.g. 'chase-sapphire-preferred'

### `estimate_rewards` (~203 tokens)

Estimate annual rewards

Given an annual spending profile (USD per category, e.g. { dining: 6000, groceries: 8000, travel: 4000, other: 20000 }), estimate each card's net rewards value and rank them. Net value = rewards earned on spend + first-year signup bonus − annual fee. Statement credits are reported separately (max value if fully used), NOT folded into the headline, to avoid overstating premium 'coupon-book' cards. Returns a per-category breakdown and the assumptions used. All card facts come from the verified dataset; only point valuation is modeled.

Input parameters:

- `cardIds` (array): Restrict to these cards; default is all
- `creditBand` (string): Restrict to cards this band typically qualifies for
- `includeSignupBonus` (boolean): Include the signup bonus in year-1 value (default true)
- `limit` (integer)
- `spend` (object, required): Annual USD spend keyed by category label

### `check_eligibility` (~125 tokens)

Check likely eligibility

Given a user's credit band (and optionally income), return cards they would typically qualify for, surfacing issuer application rules (e.g. Chase 5/24) and any income floor. Only cards that publish a credit requirement can be answered; cards with no published requirement are counted in `unknownCount`, never listed as qualifying. This is a likelihood signal from published guidance, not an approval guarantee.

Input parameters:

- `cardIds` (array): Restrict to these cards; default is all verified cards
- `creditBand` (string, required)
- `incomeUsd` (number)

### `get_apply_link` (~51 tokens)

Get apply link

Return the apply link for a card. This is always a creditcards.best tracked redirect that records the referral and forwards to the issuer; the raw issuer URL is never returned.

Input parameters:

- `id` (string, required)

### `compare_cards` (~55 tokens)

Compare cards

Side-by-side detail for two or more cards by id: fees, foreign-transaction fee, signup bonus, earn rates, credits and eligibility. Apply links are tracked redirects.

Input parameters:

- `ids` (array, required): Card slugs to compare

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/best-creditcards-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 65
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 65

## Links

- Remote endpoint: https://mcp.creditcards.best/
- Website: https://creditcards.best/mcp-info
- Changelog RSS feed: https://verifymcp.io/servers/best-creditcards-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/best-creditcards-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/best-creditcards-mcp/mcp