earnrate
REMOTE · MCP.EARNRATE.DEV · 2 COMPONENTS
Which credit card earns the most at a merchant, from your cards or every card, and why.
Available components
Last scanned (15 hours ago)
Scores higher than 26% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Finance and Payments
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
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. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Nov 26 +5
- HTTPS: unverified → pass ▲ security
- 1 Nov 26 −26
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: fail → pass ▲ security
- First check of Authorization: pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Oct 26 58
First indexed and scored.
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 6 Nov 2026 · Probed https://mcp.earnrate.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=earnrate.dev | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8028e5c5e0eed3270eb547cad077e5c2 |
| SANs: earnrate.dev, mcp.earnrate.dev, *.mcp.earnrate.dev | ||||||
| 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.earnrate.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| earnrate.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.earnrate.dev/.well-known/oauth-protected-resource", scope="wallet"
Bearer resource_metadata="https://mcp.earnrate.dev/.well-known/oauth-protected-resource", scope="wallet"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.earnrate.dev/.well-known/oauth-protected-resource", scope="wallet" |
Protected resource metadata
| Document | https://mcp.earnrate.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.earnrate.dev |
| Authorisation server | https://mcp.earnrate.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.earnrate.dev | Auth required | 401 | |
| http (plaintext) | http://mcp.earnrate.dev | HTTPS enforced | 301 | https://mcp.earnrate.dev/ |
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 →
add_card Add a card ~281
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| cardIds | array | yes | – |
| created | boolean | yes | – |
| memberships | array | yes | – |
| message | string | yes | – |
| notes | array | yes | – |
No examples provided.
best_card_for_purchase Best card for a purchase ~632
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Merchant name or web address as the user would say it or see it, e.g. "Whole Foods" or "delta.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| allCards | – | yes | – |
| assumptions | array | yes | – |
| bonus | – | yes | – |
| decision | – | yes | – |
| excluded | array | yes | – |
| merchant | object | yes | – |
| notes | array | yes | – |
| ranked | array | yes | – |
| sensitivity | string|null | yes | – |
| warnings | array | yes | – |
No examples provided.
best_cards_for Best cards for a purchase ~594
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| excluded | array | yes | – |
| merchant | object | yes | – |
| ranked | array | yes | – |
| warnings | array | yes | – |
No examples provided.
cheat_sheet Cheat sheet ~215
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| notes | array | yes | – |
| quarter | string | yes | – |
| rows | array | yes | – |
| scope | string | yes | – |
No examples provided.
compare_welcome_offers Compare welcome offers ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | array | yes | – |
| offers | array | yes | – |
| withoutOffer | array | yes | – |
No examples provided.
delete_wallet Delete the wallet ~46
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
No examples provided.
export_wallet Export the wallet ~48
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | – |
No examples provided.
import_wallet Import a wallet ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | The wallet.yaml text, as the user gave it. |
| Name | Type | Req | Description |
|---|---|---|---|
| cardIds | array | yes | – |
| created | boolean | yes | – |
| memberships | array | yes | – |
| message | string | yes | – |
| notes | array | yes | – |
No examples provided.
list_wallet List wallet ~66
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cards | array | yes | – |
| memberships | array | yes | – |
No examples provided.
record_purchase Record a purchase ~519
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount spent in US dollars. |
| cardId | string | yes | 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 | yes | Merchant name or web address as the user would say it or see it, e.g. "Whole Foods" or "delta.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| bonus | – | yes | – |
| booking | – | yes | – |
| message | string | yes | – |
| recorded | boolean | yes | – |
No examples provided.
remove_card Remove a card ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cardId | string | yes | The card id from search_cards, e.g. chase-sapphire-preferred. |
| Name | Type | Req | Description |
|---|---|---|---|
| cardIds | array | yes | – |
| created | boolean | yes | – |
| memberships | array | yes | – |
| message | string | yes | – |
| notes | array | yes | – |
No examples provided.
resolve_merchant Resolve a merchant ~443
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Merchant name or web address as the user would say it or see it, e.g. "Whole Foods" or "delta.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | yes | – |
| ambiguity | – | yes | – |
| bookedVia | array | yes | – |
| category | string | yes | – |
| channel | – | yes | – |
| confidence | string | yes | – |
| inference | – | yes | – |
| input | string | yes | – |
| likelyMcc | number|null | yes | – |
| merchantId | string|null | yes | – |
| resolvedName | string | yes | – |
| source | string | yes | – |
No examples provided.
search_cards Search cards ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Card name or issuer, as the user said it. |
| Name | Type | Req | Description |
|---|---|---|---|
| cards | array | yes | – |
| exact | boolean | yes | – |
No examples provided.
set_memberships Set memberships ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| memberships | array | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| cardIds | array | yes | – |
| created | boolean | yes | – |
| memberships | array | yes | – |
| message | string | yes | – |
| notes | array | yes | – |
No examples provided.
simulate_spending Simulate a year of spending ~378
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| additions | array | yes | – |
| current | – | yes | – |
| notes | array | yes | – |
| pairs | array | yes | – |
| singles | array | yes | – |
No examples provided.
update_card Update a card ~279
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+.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| cardIds | array | yes | – |
| created | boolean | yes | – |
| memberships | array | yes | – |
| message | string | yes | – |
| notes | array | yes | – |
No examples provided.
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.
remote · mcp.earnrate.dev
claude mcp add --transport http cwasley-earnrate 'https://mcp.earnrate.dev/'
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.