Remote MCP · Endpoint

MaxWorth Credit Card Benefits MCP server

No. MaxWorth Credit Card Benefits answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp-public.maxworth.app/mcp

The last check completed an MCP handshake.

Registry name
app.maxworth/maxworth-public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
58 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
US credit card data: annual fees, credit card credits, earn rates, offers and cashback portal rates.
Listing
From the official MCP registry (active).
Recent checks of MaxWorth Credit Card Benefits
CheckedResultHandshake
1 hour agoHandshake completed58 ms
1 day agoHandshake completed139 ms
1 day agoHandshake completed75 ms
3 days agoHandshake completed68 ms
6 days agoHandshake completed100 ms
8 days agoHandshake completed180 ms
11 days agoHandshake completed121 ms
13 days agoHandshake completed100 ms
15 days agoHandshake completed116 ms
17 days agoHandshake completed79 ms
19 days agoHandshake completed1.01 s
21 days agoHandshake completed132 ms
23 days agoHandshake completed75 ms
24 days agoHandshake completed153 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with MaxWorth Credit Card Benefits and makes no claim about it beyond what these checks measured.