Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
earnrate is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
822
downloads a day
local
or remote
2k
downloads in 30d
What it does
Picks the credit card in your wallet that earns the most at a merchant, and says why.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user earnrate-mcp '--' npx -y earnrate mcp
# 2 — ask your agent for something these tools do
# best_card_for_purchase, resolve_merchant, list_wallet and 15 more
Remote: OAuth sign-in · Package: API key.
earnrate costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CWAll 1 server
cwasley1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user earnrate-mcp '--' npx -y earnrate mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://mcp.earnrate.dev: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http earnrate-mcp https://mcp.earnrate.devFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take EARNRATE_WALLET (Path to your wallet file. Default: ~/.earnrate/wallet.yaml), EARNRATE_LLM (Set to on to let Claude classify merchants earnrate doesn't know. Off by default.), EARNRATE_LLM_MODEL (The Claude model for merchant lookups, when EARNRATE_LLM is on.), EARNRATE_LLM_MAX_CALLS (Most Claude merchant lookups per session, when EARNRATE_LLM is on.), EARNRATE_MERCHANT_CACHE (Where Claude's merchant answers are saved. Default: ~/.earnrate/merchant-cache.json), ANTHROPIC_API_KEY (Your own Anthropic key, used only when EARNRATE_LLM is on.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Picks the card in the user's wallet that earns the most rewards for a purchase, and explains why. Call it before paying. decision.cardId is the pick and decision.checkoutLabel is how the card appears at checkout. Also returns every usable card ranked with reasons, cards the merchant won't…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| merchant | string | yes | — |
| amount | number | no | Purchase amount in US dollars. Improves cap math. |
| channel | string | no | — |
| date | yes | — | |
| category | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| merchant | string | yes | — |
| channel | string | no | — |
| category | string | no | — |
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.
No parameter schema on file.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | — |
| noAnnualFee | boolean | no | Only cards with no annual fee. |
| business | boolean | no | Business cards instead of personal ones. |
| includeHeld | boolean | no | Include cards already in the wallet. |
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 wallet file. Only call it after the purchase has happened, and only once per purchase: calling it twice counts the spend twice. Purchases with…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cardId | string | yes | — |
| merchant | string | yes | — |
| amount | number | yes | Amount spent in US dollars. |
| channel | string | no | — |
| date | yes | — | |
| category | string | no | — |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install earnrate or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 0.2.8 · scanned 2 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings0 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest8e9d56f5a3d5589d4ee6e3b3676e91c41b6671b03d6704e3e609b3d52c805204
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (18 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| export_wallet | no tags | |
| import_wallet | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| delete_wallet | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| switch_wallet | state-write | state-write: declares readOnlyHint: false |
| best_card_for_purchase | no tags | |
| resolve_merchant | no tags | |
| compare_welcome_offers | no tags | |
| best_cards_for | no tags | |
| simulate_spending | no tags | |
| cheat_sheet | no tags | |
| search_cards | no tags | |
| list_wallet | no tags | |
| record_purchase | state-write | state-write: declares readOnlyHint: false |
| add_card | state-write | state-write: declares readOnlyHint: false |
| update_card | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| remove_card | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| set_memberships | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| set_point_values | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest8e9d56f5a3d5589d
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.8. Pin a release below and the command asks for exactly that one.
0.2.8
2 Nov 2026
latestNo release note was published with this version.
0.2.7
2 Nov 2026
No release note was published with this version.
0.2.5
1 Nov 2026
No release note was published with this version.
0.2.3
1 Nov 2026
No release note was published with this version.
0.2.1
31 Oct 2026
No release note was published with this version.
0.1.4
31 Oct 2026
No release note was published with this version.
0.1.2
30 Oct 2026
No release note was published with this version.
0.1.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish earnrate can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.