Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

creditcards.best

REMOTE · CREDITCARDS.BEST · 2 COMPONENTS · SCANNED SEP 20

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

0 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • 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 Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
Install

How do I install the creditcards.best MCP server?

creditcards.best is a hosted endpoint at https://creditcards.best/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 · creditcards.best

# add to Claude Code
claude mcp add --transport http best-creditcards-mcp 'https://creditcards.best/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "best-creditcards-mcp": {
      "url": "https://creditcards.best/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "best-creditcards-mcp": {
      "type": "http",
      "url": "https://creditcards.best/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.best-creditcards-mcp]
url = "https://creditcards.best/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "best-creditcards-mcp": {
      "type": "remote",
      "url": "https://creditcards.best/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add best-creditcards-mcp --url 'https://creditcards.best/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  best-creditcards-mcp:
    url: "https://creditcards.best/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "best-creditcards-mcp": {
      "Transport": "http",
      "Url": "https://creditcards.best/mcp"
    }
  }
}
# add to Vellum
assistant mcp add best-creditcards-mcp -t streamable-http -u 'https://creditcards.best/mcp'
// mcp.json
{
  "mcpServers": {
    "best-creditcards-mcp": {
      "type": "http",
      "url": "https://creditcards.best/mcp"
    }
  }
}

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

Changelog

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.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 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.

  • 23 Aug 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.

  • 11 Aug 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
  • 31 Jul 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
  • 30 Jul 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
  • 28 Jul 26 0
    • Schema quality: pass → fail functional
    • Tool coverage: 55% → 63% functional
    • Stability: unverified → 0.03 functional
  • 27 Jul 26 0

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://creditcards.best/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.creditcards.best CN=YR1,O=Let's Encrypt,C=US 23 Jul 2026 21 Oct 2026 RSA 2048 SHA256-RSA 59401d7fde837ef870d441ad85b817aae8f
SANs: *.creditcards.best, creditcards.best
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of creditcards.best. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
best. present 13966, 41279 8, 8 Verified
creditcards.best. 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
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://creditcards.best/mcp Verified 200
http (plaintext) http://creditcards.best/mcp HTTPS enforced 308 https://creditcards.best/mcp
MCP tools · 6 exposed · ~890 tokens

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 →

Tool Tokens
check_eligibility ~125

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.

NameTypeReqDescription
cardIdsarrayRestrict to these cards; default is all verified cards
creditBandstringyes
incomeUsdnumber

No output schema declared.

No examples provided.

compare_cards ~55

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.

NameTypeReqDescription
idsarrayyesCard slugs to compare

No output schema declared.

No examples provided.

estimate_rewards ~203

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.

NameTypeReqDescription
cardIdsarrayRestrict to these cards; default is all
creditBandstringRestrict to cards this band typically qualifies for
includeSignupBonusbooleanInclude the signup bonus in year-1 value (default true)
limitinteger
spendobjectyesAnnual USD spend keyed by category label

No output schema declared.

No examples provided.

get_apply_link ~51

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.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

get_card ~65

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.

NameTypeReqDescription
idstringyesCard slug, e.g. 'chase-sapphire-preferred'

No output schema declared.

No examples provided.

search_cards ~391

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.

NameTypeReqDescription
categorystringCurated slug, e.g. 'best-cash-back-credit-cards'
creditBandstringOnly cards a user with this credit band typically qualifies for
isBusinessboolean
issuerstringIssuer name, partial match (e.g. 'Chase')
limitintegerMax cards to return (default 25). Check `truncated` before treating the list as complete.
maxAnnualFeenumber
minSignupValueUsdnumberMinimum estimated signup-bonus cash value
noForeignTransactionFeeboolean
productTypearray
rewardsCurrencystringProgram name, partial match, by its own name: 'AAdvantage' not 'American', 'SkyMiles' not 'Delta', 'Bonvoy', 'Avios'.
rewardsCurrencyTypearrayKind of loyalty currency earned. Use this for airline or hotel cards; it is not a productType.
sortstring
verifiedDefaults to true (issuer-verified only). false = only the unverified stubs seeded from the open reference. null = the whole corpus, nulls and all.

No output schema declared.

No examples provided.

Common questions

What is the creditcards.best MCP server?

creditcards.best is an MCP server listed in the public MCP registry as best.creditcards/mcp. Search, compare and estimate rewards across US credit cards. Verified fees, APRs and bonuses. This page covers its hosted endpoint (https://creditcards.best/mcp).

Is the creditcards.best MCP server safe to use?

creditcards.best scores 81 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 creditcards.best MCP server expose?

creditcards.best exposes 6 tools: search_cards, get_card, estimate_rewards, check_eligibility, get_apply_link, compare_cards. Their descriptions and schemas cost roughly 890 tokens of context every time the server is loaded.

Does the creditcards.best MCP server require authentication?

No. We connected to creditcards.best without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the creditcards.best MCP server still maintained?

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