KiasuMiles. Your cards. Your merchants. Your best answer.

KiasuMiles hero with the line Your cards. Your merchants. Your best answer beside a personalized card recommendation.

Built by Hosan

KiasuMiles is a hosted MCP service for the cashier moment: your agent sends the merchant and the user's current card stack, then gets the best card before the tap.

Hosted MCP endpoint

Connect your agent. Keep wallet data client-side.

The hosted server stores card rules and merchant data. Your client sends card IDs per request, and KiasuMiles does not store a wallet.

Streamable HTTP MCP endpoint https://kiasumiles.space/mcp
Read privacy policy View GitHub

The story

I built KiasuMiles because "roughly right" was costing real miles.

The spark was a repeated human moment: standing at checkout, knowing the right card probably exists, but not knowing it quickly enough to use it.

The moment

The ritual was small enough to ignore.

At the cashier, my wife would look at her wallet, look at me, and ask: "Which card?" I usually had an answer. "Usually" is where miles disappear quietly.

One confident tap can turn 4 mpd into base rate. You find out days later, if you bother checking the statement at all.

The build

The product became an MCP server.

The early build had local wallet setup and config paths. Useful, but too much ceremony for the checkout line.

Now the hosted endpoint keeps the rules current while clients pass the user's card IDs for each request.

The tap

The answer moved to the moment that matters.

Your wallet, your partner's wallet, your parents' cards, ranked for the merchant in front of you.

The whole product lives in the few seconds before the tap. That is the only window that matters.

From the build

The data can be right and the recommendation can still be wrong.

Category-level advice breaks when the merchant has specific rules. KiasuMiles combines merchant matching, card-rule caveats, and the user's current stack before ranking.

What changed

✓Wallet setup moved to the client as a list of card IDs.
✓Merchant logic handles exceptions instead of trusting category alone.
✓When card rules are time-sensitive, KiasuMiles shows the caveat instead of bluffing certainty.

60-second product film

Ask, rank, tap, move on.

A quick look at the kind of question an MCP-connected agent can answer in the moment.

The answer

Ask your agent. Get the card.

KiasuMiles starts with the cards supplied in the MCP request, then recommends the best usable card for the merchant in front of you.

9:41•••
What card at Sheng Siong?
Use UOB Visa Signature.
Next best
UOB PP Visa
Ranked from the cards sent with this request

Features

Built for the person at the counter.

✓

Stack-aware ranking

Pass card IDs in the MCP request and rank only those cards against the merchant.

✓

Merchant-aware logic

Looks beyond broad categories and handles merchant-specific caveats where the rules require it.

✓

No hosted wallet

The hosted service does not expose wallet configure or wallet read tools.

✓

Fresh central data

Card and merchant rules can be updated centrally without asking every user to reinstall.

✓

Honest caveats

Where a rule is time-sensitive or merchant-specific, the answer surfaces what needs to be true.

✓

MCP-ready

Exposes a hosted Streamable HTTP MCP endpoint at kiasumiles.space/mcp.

Examples

Real questions. Wallet-aware answers.

"What card at Sheng Siong?"
UOB Visa Signature
Next: UOB PP Visa
"Best card for Sinopec?"
UOB Visa Signature
Check cap
"Which card for Sushi Tei?"
UOB Preferred Platinum Visa
Medium confidence

Try it

Guess less. Tap better.

Connect your agent to the hosted MCP endpoint, pass the user's current card stack with each request, and let KiasuMiles answer before the tap.

Open MCP endpoint View on GitHub

Data version: 2026-06-10 · Cards: 49 · Merchants: 3317