# earnrate (remote · mcp.earnrate.dev)

Which credit card earns the most at a merchant, from your cards or every card, and why.

- Trust score: 37/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `mcp.earnrate.dev`: 37/100 (this document), [markdown](https://verifymcp.io/servers/cwasley-earnrate/mcp.md), [page](https://verifymcp.io/servers/cwasley-earnrate/mcp)
- npm · `earnrate`: 82/100, [markdown](https://verifymcp.io/servers/cwasley-earnrate/earnrate.md), [page](https://verifymcp.io/servers/cwasley-earnrate/earnrate)

## Channel facts

- Endpoint: `https://mcp.earnrate.dev`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.2.14`

## 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-11-06.

- **Endpoint Security**: 92/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the earnrate MCP server?

earnrate is a hosted endpoint at https://mcp.earnrate.dev/, 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.

### Claude

```bash
claude mcp add --transport http cwasley-earnrate 'https://mcp.earnrate.dev/'
```

### Cursor

```json
{
  "mcpServers": {
    "cwasley-earnrate": {
      "url": "https://mcp.earnrate.dev/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cwasley-earnrate": {
      "type": "http",
      "url": "https://mcp.earnrate.dev/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cwasley-earnrate]
url = "https://mcp.earnrate.dev/"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add cwasley-earnrate --url 'https://mcp.earnrate.dev/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cwasley-earnrate:
    url: "https://mcp.earnrate.dev/"
```

### Netclaw

```json
{
  "McpServers": {
    "cwasley-earnrate": {
      "Transport": "http",
      "Url": "https://mcp.earnrate.dev/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cwasley-earnrate -t streamable-http -u 'https://mcp.earnrate.dev/'
```

### Other

```json
{
  "mcpServers": {
    "cwasley-earnrate": {
      "type": "http",
      "url": "https://mcp.earnrate.dev/"
    }
  }
}
```

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-11-06 (score 37, 0)

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

### 2026-11-03 (score 37, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-11-01 (score 32, −26)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-31 (score 58)

First indexed and scored.

## MCP tools (16)

### `best_card_for_purchase` (~632 tokens)

Best card for a purchase

Which card earns the most rewards for a purchase, and why. With no cards given and no saved wallet, it ranks every card earnrate knows (in `allCards`): a complete answer for anyone. With cards named in the conversation (`cards`) or a saved wallet, it picks the best of the user's own: `decision.cardId` is the pick and `decision.checkoutLabel` is how the card appears at checkout, with every usable card ranked with reasons, cards the merchant won't take, assumptions, warnings, and when a different point valuation would change the pick. Never needs or returns card numbers.

Input parameters:

- `amount` (number): Purchase amount in US dollars. Improves cap math.
- `cards` (array): Cards the user named in this conversation, to answer for just those cards without saving anything. Leave out to use the user's saved wallet if they have one; with neither, the answer covers every car…
- `category` (string): Only for a merchant earnrate may not know, and only if you're confident what kind of business it is: its spending category, e.g. grocery.supermarket for a supermarket, dining for a restaurant, gas fo…
- `channel` (string): How the purchase is made. Omit if unknown; the answer says what it assumed.
- `date` (string): Purchase date, YYYY-MM-DD. Defaults to today.
- `memberships` (array): Memberships the user has, such as amazon-prime, when they're named in the conversation rather than saved.
- `merchant` (string, required): Merchant name or web address as the user would say it or see it, e.g. "Whole Foods" or "delta.com".

Output parameters:

- `allCards`
- `assumptions` (array)
- `bonus`
- `decision`
- `excluded` (array)
- `merchant` (object)
- `notes` (array)
- `ranked` (array)
- `sensitivity` (string|null)
- `warnings` (array)

### `resolve_merchant` (~443 tokens)

Resolve a merchant

Shows how earnrate identifies a merchant: its spend category, likely MCC, which card networks it takes, confidence, and whether that came from curated data, Claude, or nowhere. Use it to explain or double-check a recommendation.

Input parameters:

- `category` (string): Only for a merchant earnrate may not know, and only if you're confident what kind of business it is: its spending category, e.g. grocery.supermarket for a supermarket, dining for a restaurant, gas fo…
- `channel` (string): How the purchase is made. Omit if unknown; the answer says what it assumed.
- `merchant` (string, required): Merchant name or web address as the user would say it or see it, e.g. "Whole Foods" or "delta.com".

Output parameters:

- `accepts`
- `ambiguity`
- `bookedVia` (array)
- `category` (string)
- `channel`
- `confidence` (string)
- `inference`
- `input` (string)
- `likelyMcc` (number|null)
- `merchantId` (string|null)
- `resolvedName` (string)
- `source` (string)

### `compare_welcome_offers` (~224 tokens)

Compare welcome offers

Ranks the public welcome (sign-up) offers on cards the user doesn't have by first-year value: the bonus at the user's point values minus the first year's annual fee. Use it when the user asks which new card to get or which has the best sign-up bonus. It covers only the cards earnrate knows, offers vary by person, and each offer's note gives the issuer's eligibility rules; pass those caveats on. It doesn't account for what a card would earn on the user's spending.

Input parameters:

- `business` (boolean): Business cards instead of personal ones.
- `cards` (array): Cards the user named in this conversation, to answer for just those cards without saving anything. Leave out to use the user's saved wallet if they have one; with neither, the answer covers every car…
- `includeHeld` (boolean): Include cards already in the wallet.
- `kind` (string): cash: cash back cards only. points: points and miles cards only.
- `noAnnualFee` (boolean): Only cards with no annual fee.

Output parameters:

- `notes` (array)
- `offers` (array)
- `withoutOffer` (array)

### `best_cards_for` (~594 tokens)

Best cards for a purchase

Ranks every card earnrate knows, not only the user's, for one purchase or category, each set up at its best (the right category pick, activated, cap unused), with its annual fee and what earning the rate takes. Use it for questions like "what's the best card for groceries?" or "which card should I get for Amazon?". It needs no wallet. For which of the user's own cards to use, call best_card_for_purchase instead. Mention the annual fee and any conditions alongside each card.

Input parameters:

- `amount` (number): Purchase amount in US dollars, if known.
- `business` (boolean): Business cards instead of personal ones.
- `category` (string): A spending category: dining (Restaurants), dining.fast_food (Fast food), grocery (Grocery), grocery.supermarket (Supermarkets), grocery.online (Online grocery and delivery), superstore (Superstores),…
- `channel` (string): How the purchase is made. Omit if unknown; the answer says what it assumed.
- `issuer` (string): Only this issuer's cards.
- `kind` (string): cash: cash back cards only. points: points and miles cards only.
- `memberships` (array): Memberships the user has, such as amazon-prime. Rates that need one they don't have are listed separately.
- `merchant` (string): Merchant name or web address as the user would say it or see it, e.g. "Whole Foods" or "delta.com".
- `noAnnualFee` (boolean): Only cards with no annual fee.
- `valuation` (string): flat (default): points at their cash-out value, about 1¢. points-heavy: Amex MR and Chase UR at 1.7¢, for people who transfer points to airlines and hotels.

Output parameters:

- `assumptions` (array)
- `excluded` (array)
- `merchant` (object)
- `ranked` (array)
- `warnings` (array)

### `simulate_spending` (~378 tokens)

Simulate a year of spending

Spends monthly amounts for a year across every card earnrate knows, and ranks single cards and two-card pairs by rewards minus annual fees. Spending is optional: without it, typical U.S. household amounts are used and the answer says so. With `cards` (named in the conversation) or compareToWallet (the saved wallet), it ranks the cards that would add the most to those cards instead. Use it for "which card fits my spending?" or "is it worth adding a card?". It leaves out welcome bonuses.

Input parameters:

- `business` (boolean): Business cards instead of personal ones.
- `cards` (array): Cards the user named in this conversation, to answer for just those cards without saving anything. Leave out to use the user's saved wallet if they have one; with neither, the answer covers every car…
- `compareToWallet` (boolean): Rank the cards that would add the most to the user's saved wallet.
- `issuer` (string): Only this issuer's cards.
- `kind` (string): cash: cash back cards only. points: points and miles cards only.
- `memberships` (array): Memberships the user has, such as amazon-prime. Rates that need one they don't have are listed separately.
- `noAnnualFee` (boolean): Only cards with no annual fee.
- `spending` (array): Monthly spending lines, each a category (grocery.supermarket, dining, gas, other) or a merchant (Amazon, Costco). Optional: leave out to use typical amounts, and don't press the user for numbers they…
- `valuation` (string): flat (default): points at their cash-out value, about 1¢. points-heavy: Amex MR and Chase UR at 1.7¢, for people who transfer points to airlines and hotels.

Output parameters:

- `additions` (array)
- `current`
- `notes` (array)
- `pairs` (array)
- `singles` (array)

### `cheat_sheet` (~215 tokens)

Cheat sheet

The card to use for each everyday kind of purchase right now: groceries, dining, gas, Amazon, Costco, travel, streaming, drugstores and everything else. With no cards given and no saved wallet, it picks from every card earnrate knows (`scope: all cards`, each row noting the card's fee and conditions). With cards named in the conversation or a saved wallet, it picks from the user's own cards, with caps, picks and activations as they are. For one specific store, call best_card_for_purchase instead. Pass on the notes.

Input parameters:

- `cards` (array): Cards the user named in this conversation, to answer for just those cards without saving anything. Leave out to use the user's saved wallet if they have one; with neither, the answer covers every car…
- `date` (string): Purchase date, YYYY-MM-DD. Defaults to today.
- `memberships` (array): Memberships the user has, such as amazon-prime, when they're named in the conversation rather than saved.

Output parameters:

- `date` (string)
- `notes` (array)
- `quarter` (string)
- `rows` (array)
- `scope` (string)

### `search_cards` (~108 tokens)

Search cards

Finds credit cards in earnrate's catalog by name or issuer, e.g. "sapphire", "amex gold" or "bofa". Returns each card's id (for add_card), network, annual fee, whether it's already in the wallet, and what it needs set up: category picks and their options, memberships, activations. Leave the query out to list every card. US cards only.

Input parameters:

- `query` (string): Card name or issuer, as the user said it.

Output parameters:

- `cards` (array)
- `exact` (boolean)

### `list_wallet` (~66 tokens)

List wallet

Lists the user's cards: checkout label, network, rewards currency and its value, spending caps with how much is left this period, chosen bonus categories (and whether they're current), welcome-bonus progress, which stores a store card works at, and when each card's data was last verified.

Output parameters:

- `cards` (array)
- `memberships` (array)

### `record_purchase` (~519 tokens)

Record a purchase

Records a purchase the user has already made, so spending caps and welcome-bonus progress stay accurate for future recommendations. It updates the user's saved wallet. Only call it after the purchase has happened, and only once per purchase: calling it twice counts the spend twice. Purchases with no cap and no open welcome bonus are acknowledged and nothing is written.

Input parameters:

- `amount` (number, required): Amount spent in US dollars.
- `cardId` (string, required): The card used, as a cardId from list_wallet or best_card_for_purchase.
- `category` (string): Only for a merchant earnrate may not know, and only if you're confident what kind of business it is: its spending category, e.g. grocery.supermarket for a supermarket, dining for a restaurant, gas fo…
- `channel` (string): How the purchase is made. Omit if unknown; the answer says what it assumed.
- `date` (string): Purchase date, YYYY-MM-DD. Defaults to today.
- `merchant` (string, required): Merchant name or web address as the user would say it or see it, e.g. "Whole Foods" or "delta.com".

Output parameters:

- `bonus`
- `booking`
- `message` (string)
- `recorded` (boolean)

### `add_card` (~281 tokens)

Add a card

Adds a card the user holds to their wallet by its id from search_cards, creating the wallet if there isn't one. The reply says what the card still needs (category picks, memberships, activations); ask the user about those. Stores only the card's product id and settings, never card numbers.

Input parameters:

- `activated` (array): Rule ids the user has activated with the issuer, such as rotating categories. Replaces the current list.
- `anniversary` (string): The account's anniversary as MM-DD, for cards whose cap resets on it.
- `bonus`: A welcome bonus the user is working toward, so purchases recorded on this card count toward it and answers can favor it. Ask when they opened the account; spending needed and the deadline default to…
- `cardId` (string, required): The card id from search_cards, e.g. chase-sapphire-preferred.
- `checkoutLabel` (string): How the card appears at checkout or in a browser wallet, e.g. "Amex Gold". Optional.
- `picks` (object): For cards where the cardholder picks bonus categories: choice id → option ids, from search_cards, e.g. {"five-percent": ["tv-internet-streaming", "fast-food"]}. Saved for the current period. Ask the…

Output parameters:

- `cardIds` (array)
- `created` (boolean)
- `memberships` (array)
- `message` (string)
- `notes` (array)

### `update_card` (~279 tokens)

Update a card

Changes settings on a card already in the wallet: its category picks for this period, checkout label, anniversary or activated categories. Picks for the current period are merged with the ones already saved. Use it when the user picks new categories, such as each quarter on U.S. Bank Cash+.

Input parameters:

- `activated` (array): Rule ids the user has activated with the issuer, such as rotating categories. Replaces the current list.
- `anniversary` (string): The account's anniversary as MM-DD, for cards whose cap resets on it.
- `bonus`: A welcome bonus the user is working toward, so purchases recorded on this card count toward it and answers can favor it. Ask when they opened the account; spending needed and the deadline default to…
- `cardId` (string, required): The card id from search_cards, e.g. chase-sapphire-preferred.
- `checkoutLabel` (string): How the card appears at checkout or in a browser wallet, e.g. "Amex Gold". Optional.
- `picks` (object): For cards where the cardholder picks bonus categories: choice id → option ids, from search_cards, e.g. {"five-percent": ["tv-internet-streaming", "fast-food"]}. Saved for the current period. Ask the…

Output parameters:

- `cardIds` (array)
- `created` (boolean)
- `memberships` (array)
- `message` (string)
- `notes` (array)

### `remove_card` (~63 tokens)

Remove a card

Removes a card from the wallet, with its tracked cap usage and bonus progress. Only when the user says they no longer have it or don't want it considered.

Input parameters:

- `cardId` (string, required): The card id from search_cards, e.g. chase-sapphire-preferred.

Output parameters:

- `cardIds` (array)
- `created` (boolean)
- `memberships` (array)
- `message` (string)
- `notes` (array)

### `set_memberships` (~124 tokens)

Set memberships

Sets the memberships that unlock some cards' rates, such as amazon-prime for Prime Visa's 5% or a Bank of America Preferred Rewards tier. Replaces the whole list, so include the ones to keep.

Input parameters:

- `memberships` (array, required): Every membership the user has. Known: amazon-prime, bank-of-america-account, bank-of-america-small-business-account, bofa-rewards-member, bofa-rewards-preferred-honors, bofa-rewards-preferred-plus, b…

Output parameters:

- `cardIds` (array)
- `created` (boolean)
- `memberships` (array)
- `message` (string)
- `notes` (array)

### `export_wallet` (~48 tokens)

Export the wallet

The saved wallet as a wallet.yaml file the earnrate command line and earnrate.dev can import: card ids, picks, activations, memberships, cap usage and bonus progress. Never card numbers.

Output parameters:

- `yaml` (string)

### `import_wallet` (~76 tokens)

Import a wallet

Replaces the saved wallet with a wallet.yaml from the earnrate command line or earnrate.dev, when the user pastes or attaches one. Wallet files only: never statements or card numbers. Confirm with the user first if they already have cards saved.

Input parameters:

- `yaml` (string, required): The wallet.yaml text, as the user gave it.

Output parameters:

- `cardIds` (array)
- `created` (boolean)
- `memberships` (array)
- `message` (string)
- `notes` (array)

### `delete_wallet` (~46 tokens)

Delete the wallet

Deletes the saved wallet now and for good, and signs out every app using it. Only when the user asks to delete it; confirm first, and offer export_wallet to keep a copy.

Output parameters:

- `deleted` (boolean)

## Diagnostics

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

## Score history

- 2026-11-06: 37
- 2026-11-05: 37
- 2026-11-04: 37
- 2026-11-03: 37
- 2026-11-02: 32
- 2026-11-01: 32
- 2026-10-31: 58

## Common questions

### What is the earnrate MCP server?

earnrate is an MCP server listed in the public MCP registry as io.github.cwasley/earnrate. Which credit card earns the most at a merchant, from your cards or every card, and why. This page covers its hosted endpoint (https://mcp.earnrate.dev).

### Is the earnrate MCP server safe to use?

earnrate scores 37 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 earnrate MCP server expose?

earnrate exposes 16 tools: best_card_for_purchase, resolve_merchant, compare_welcome_offers, best_cards_for, simulate_spending, and 11 more. Their descriptions and schemas cost roughly 4,096 tokens of context every time the server is loaded.

### Does the earnrate MCP server require authentication?

Yes. earnrate asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the earnrate MCP server still maintained?

earnrate is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the earnrate MCP server?

VerifyMCP ran 5 checks on earnrate, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about earnrate: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.earnrate.dev/
- Repository: https://github.com/cwasley/earnrate
- Website: https://earnrate.dev/
- Changelog RSS feed: https://verifymcp.io/servers/cwasley-earnrate/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cwasley-earnrate/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cwasley-earnrate/mcp.json
- HTML version of this page: https://verifymcp.io/servers/cwasley-earnrate/mcp