KiasuMiles

"Which card do I use again?"

If you're in the miles game, you've asked this at least once - standing at the cashier, not quite sure if this is the 4 mpd card or the 1.2 mpd one.

KiasuMiles answers it over MCP. Point your agent at the hosted endpoint, send the cards you actually carry with each request, and get back the card that earns the most at the merchant in front of you.

Hosted MCP endpoint: https://kiasumiles.space/mcp

Why this exists

Miles guides tell you "Card X for dining, Card Y for online shopping". That works until your wallet has six cards and the merchant in front of you doesn't fit the chart.

KiasuMiles ranks against the cards you actually hold. The client passes your card IDs, KiasuMiles filters out everything else, factors in monthly caps, and returns one usable answer with the caveats attached. No second guessing at the counter.

The server keeps card rules and merchant data current. It never stores your wallet: card IDs are sent with each request, used once, and dropped.

Related MCP server: Award Flight Daily MCP Server

How to use it

Connect your MCP-capable agent to:

https://kiasumiles.space/mcp

Then talk to your agent in plain English.

First-time setup prompt

Copy and paste this:

Use KiasuMiles. First help me set up my card stack.
Ask me which banks I have cards with, show me the matching supported cards,
then remember my selected cards for future KiasuMiles lookups.

Your "card stack" just means the credit cards you actually carry.

Everyday prompts

After setup, ask checkout questions like:

What card should I use at NTUC FairPrice?

I'm paying for Grab in the app. Which card?

Booking Singapore Airlines online. Which card gets the most miles?

KiasuMiles returns the best card from your card stack, the miles per dollar, the cap, and any caveats you should know before paying.

If the agent forgets to ask for your cards

Paste this:

Before answering, use KiasuMiles properly:
ask me which cards I carry, map them to supported KiasuMiles cards,
then recommend only from my card stack.

Setting Up Your Cards

KiasuMiles does not keep a wallet on its server. Your agent or app keeps your card list and sends it with each question.

Use this prompt when setting up for the first time:

Use KiasuMiles to set up my card stack.
Ask me which banks I use first.
Then list supported cards for those banks only.
After I choose my cards, use that card stack for future KiasuMiles lookups.

If your agent forgets your cards, just run the setup prompt again.

You do not need to know card IDs. The agent should handle that mapping for you.

Amending Your Cards

Use plain English. Examples:

Add OCBC 90N to my KiasuMiles card stack.

Remove UOB PPV from my KiasuMiles card stack.

Replace Citi Rewards with DBS Woman's World in my KiasuMiles card stack.

Then continue asking normal checkout questions:

Now what card should I use at Cold Storage?

Checking Your Card Stack

If you are not sure what your agent currently remembers, ask:

Before using KiasuMiles, tell me what cards you currently have in my card stack.
If you are not sure, ask me to set it up again.

You can also ask whether your current stack has gaps:

Use KiasuMiles to review my current card stack.
Tell me what categories are weak and what card I should consider adding.

Hosted MCP Details

For agents and developers, KiasuMiles exposes these hosted MCP tools:

The hosted server deliberately has no wallet setup or wallet read tools. Wallet storage belongs in the agent, app, or user-controlled client.

Example lookup shape:

{
  "merchant": "NTUC FairPrice",
  "cards": ["uob_ppv", "citi_rewards_mc"],
  "channel": "mobile_contactless"
}

Responses include reason_summary, reason_codes, and gotchas, so the agent can explain why a card wins and warn about traps: wrong payment channel, partner-only bonuses, minimum spend you haven't hit.

The endpoint is rate limited per IP (30 requests a minute by default). Normal agent use never gets near it.

Try it

curl -i -X POST https://kiasumiles.space/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl-smoke","version":"1.0"}}}'

Supported agents

• Codex

• ChatGPT with MCP support

• Claude Code

• OpenClaw

• Hermes

• Anything else with Streamable HTTP MCP support

Codex plugin

The repo carries a local Codex plugin at plugins/kiasumiles and a repo marketplace at .agents/plugins/marketplace.json. The plugin bundles the MCP config, a skill for checkout recommendations, and display guidance so Codex doesn't surface card IDs, MCC codes, or raw technical fields at the user.

In Codex, add the repo marketplace, install KiasuMiles, then ask:

"What card should I use at NTUC FairPrice?"

For Maintainers

The hosted app reads card rules and merchant mappings from the configured production backend. The public package ships small demo CSVs for development and tests.

Environment variables (set in Vercel for hosted deployments):

• KIASUMILES_SUPABASE_URL

• KIASUMILES_SUPABASE_SERVICE_ROLE_KEY

• KIASUMILES_SUPABASE_CARDS_TABLE (optional, default card_rules)

• KIASUMILES_SUPABASE_MERCHANTS_TABLE (optional, default merchant_mcc)

• KIASUMILES_DATA_BACKEND (optional: auto or supabase)

• KIASUMILES_RATE_LIMIT_REQUESTS (optional, default 30; 0 disables)

• KIASUMILES_RATE_LIMIT_WINDOW_SECONDS (optional, default 60)

Backend selection:

• auto: Supabase when credentials are present, else bundled demo CSVs

• supabase: require Supabase, fail loudly if unreachable

The table schema lives at supabase/schema.sql. Both kiasumiles_data_version and /health report data_backend, so you can confirm whether production is reading from supabase or demo_csv.

Daily use

At checkout, in the car, mid-booking, ask your agent:

• "What card at NTUC FairPrice?"

• "Best card for Grab contactless?"

• "I'm at Shell. Which card?"

• "Booking flights on Singapore Airlines, which card?"

• "Which card at Shake Shack, paying online?"

KiasuMiles picks from your supplied stack and shows the earn rate and cap. If Amaze is in the stack, the combo math is already done.

Supported cards

50+ Singapore credit cards in the database. Recommendations only ever draw from the cards you supply in the request.

HSBC Revolution · UOB PPV · UOB Visa Signature · UOB PRVI Miles · UOB Lady's · KrisFlyer UOB · DBS Altitude · DBS yuu · DBS Woman's World · DBS Vantage · Citi Rewards · Citi PremierMiles · Citi Prestige · OCBC 90N · OCBC Rewards · OCBC VOYAGE · Maybank Horizon · Maybank World · Standard Chartered Journey · Standard Chartered Visa Infinite · BOC Elite Miles · Amex KrisFlyer · Amex KrisFlyer Ascend · Amex HighFlyer · Amaze combos · and more

Ask your agent to "show me all KiasuMiles cards" for the full list.

Data

Merchant MCC data comes from community reports and gets re-verified on a rolling basis. Card earn rates and caps come from published bank T&Cs. Results carry a confidence level, so if a merchant only has a few data points behind it, you'll know.

Feedback

If a recommendation looks wrong (wrong card, stale earn rate, missing merchant), message @kiasumilesbot on Telegram with the merchant name and the card that was suggested. Every report gets read.

Changelog

See CHANGELOG.md.

About

KiasuMiles is built by Hosan, founder of The AI Burrow, Singapore's applied AI collective for teams and builders who want to move past the hype and actually deploy.

• theaiburrow.xyz

• Telegram: t.me/theaiburrow

• Email: hello@theaiburrow.xyz

MIT License