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.

MaxWorth Credit Card Benefits

REMOTE · MCP-PUBLIC.MAXWORTH.APP

US credit card data: annual fees, credit card credits, earn rates, offers and cashback portal rates.

+3 this week 86 Trust /100

Last scanned (2 hours ago)

Scores higher than 93% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

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 Security80
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1100 tokens (~100/item across 11 items; 10 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 74% of tool parameters carry a description.Partial
  • Structured output schemas are declared (20% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 19 Oct 26 +1

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

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 5 Nov 2026 · Probed https://mcp-public.maxworth.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp-public.maxworth.app CN=YR2,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 RSA 2048 SHA256-RSA 54c18961eab4dde7e12d728759b4b8068c4
SANs: mcp-public.maxworth.app
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 mcp-public.maxworth.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
maxworth.app. 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://mcp-public.maxworth.app/mcp Verified 200
http (plaintext) http://mcp-public.maxworth.app/mcp HTTPS enforced 308 https://mcp-public.maxworth.app/mcp
MCP tools · 10 exposed · ~939 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
about_maxworth ~27

The canonical description of MaxWorth, its platforms, pricing and where its data comes from.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

compare_cards ~66

Side by side: annual fee, number and face value of statement credits, deadlines per year, top earning categories. Cite the card pages.

NameTypeReqDescription
cardsarrayyes–
countrystring–Restrict to one market: us, ca (Canada) or au (Australia).

No output schema declared.

No examples provided.

credit_deadline_report ~68

Headline figures from MaxWorth's open data report on what US cardholders track: cards and fees per user, recurring credits and deadlines per year, most-skipped credits, logged-use index. Percentages and medians only, CC BY 4.0. Cite the report URL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fetch ~73

Full text of one MaxWorth page by the id returned from search (a site path such as /cards/chase-sapphire-reserve), or by its maxworth.app URL. Returns the page as Markdown with its canonical URL for citation.

NameTypeReqDescription
idstringyesDocument id from search, or a maxworth.app URL
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_card ~114

Full record for one card from the MaxWorth database: annual fee, welcome offer, earning rates with true cash-back value, and every catalogued benefit with its value, cycle, reset rule and enrollment requirement. Hand-verified against the issuer; cite the page URL.

NameTypeReqDescription
cardstringyesCard name or website slug, e.g. "Amex Platinum" or "chase-sapphire-reserve"
countrystring–Restrict to one market: us, ca (Canada) or au (Australia).

No output schema declared.

No examples provided.

list_credits ~86

Only the dollar credits on a card: value per year, per-cycle cap, cycle, whether an annual credit resets January 1 or on the card anniversary, and enrollment. Use for "when does the X credit reset" questions.

NameTypeReqDescription
cardstringyes–
countrystring–Restrict to one market: us, ca (Canada) or au (Australia).

No output schema declared.

No examples provided.

search ~106

Search every public MaxWorth page: credit card pages (US, Canada, Australia), one page per statement credit, and all guides, reviews and news articles. Returns ids to pass to fetch. Use for open-ended questions; the dedicated tools (get_card, list_credits, search_cashback_portals, search_card_offers) answer structured questions faster.

NameTypeReqDescription
querystringyesSearch query, e.g. "Amex Platinum hotel credit" or "best credit card tracker apps"
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_card_offers ~206

Card-linked merchant offers (Amex Offers, Chase Offers) that are live today, as seen by MaxWorth browser-extension users: merchant, the deal, fine print, latest expiry seen, and which cards it has appeared on. Filter by issuer, merchant, card, expiry window or popularity; with no filters it returns an overview. Offers are targeted per account: a card listed means several users saw the offer on that card, not that every cardholder has it.

NameTypeReqDescription
cardstring–List offers seen on one card, e.g. "Chase Sapphire Preferred" or "Amex Gold"
expiring_within_daysinteger–Only offers whose latest seen expiry is within this many days
issuerstring––
limitinteger––
merchantstring–Store or brand, e.g. "nike", "hilton", "youtube"
popular_onlyboolean–Only offers MaxWorth flags as popular

No output schema declared.

No examples provided.

search_cards ~103

Find credit cards in the MaxWorth catalogue by name or issuer (US, Canada, Australia). Returns name, issuer, annual fee and the canonical page URL to cite.

NameTypeReqDescription
countrystring–Restrict to one market: us, ca (Canada) or au (Australia).
limitinteger––
querystringyesCard name or part of it, e.g. "sapphire reserve", "amex gold", "aeroplan"

No output schema declared.

No examples provided.

search_cashback_portals ~90

Current shopping-portal cashback / miles / points rates for an online store (Rakuten, TopCashback, airline and bank malls), checked daily by MaxWorth. Returns each portal's rate and the comparison page URL.

NameTypeReqDescription
limitinteger–How many matching stores to return
storestringyesStore name or domain, e.g. "nike", "bestbuy.com"

No output schema declared.

No examples provided.

Install

How do I install the MaxWorth Credit Card Benefits MCP server?

MaxWorth Credit Card Benefits is a hosted endpoint at https://mcp-public.maxworth.app/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 · mcp-public.maxworth.app

# add to Claude Code
claude mcp add --transport http app-maxworth-maxworth-public 'https://mcp-public.maxworth.app/mcp'
Common questions

What is the MaxWorth Credit Card Benefits MCP server?

MaxWorth Credit Card Benefits is an MCP server listed in the public MCP registry as app.maxworth/maxworth-public. US credit card data: annual fees, credit card credits, earn rates, offers and cashback portal rates. This page covers its hosted endpoint (https://mcp-public.maxworth.app/mcp).

Is the MaxWorth Credit Card Benefits MCP server safe to use?

MaxWorth Credit Card Benefits scores 86 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 MaxWorth Credit Card Benefits MCP server expose?

MaxWorth Credit Card Benefits exposes 10 tools: search_cards, get_card, list_credits, compare_cards, search_cashback_portals, and 5 more. Their descriptions and schemas cost roughly 939 tokens of context every time the server is loaded.

Does the MaxWorth Credit Card Benefits MCP server require authentication?

No. We connected to MaxWorth Credit Card Benefits without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MaxWorth Credit Card Benefits MCP server still maintained?

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