MCP.Market

Creditsync MCP server

by calademos·io.github.calademos/creditsync·v1.20.1

Track credit card benefits, welcome offers, loyalty points, and money deadlines. No bank login.

C55/100grade C
What users say
No reviews yet
Be the first
Safety scan
C55/100

full report

Adoption
New

27 downloads/wk

Reviews

Write one

Nobody has reviewed Creditsync yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Creditsync tools (34, 13 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_external_card

    Add a card that is NOT in the CreditSync catalog for application eligibility tracking (Chase 5/24, Amex 2/90). Use this for cards the user holds that CreditSync does not track benefits for (e.g., store cards, non-premium cards). Business cards are automatically excluded from Chase 5/24 count but still tracked for reference. Always set is_business correctly — it affects eligibility calculations.

  • add_reward

    Track a standalone reward NOT tied to a card — gift cards, travel vouchers, airline credits, coupons, retention offers. Use this for items the user received outside the card benefit system (e.g., AA flight credit from a cancellation, hotel gift card from a retention call). Do NOT use this for benefits that come from a card (free nights, statement credits) — those are already tracked via list_benef

  • archive_benefit

    Archive (soft delete) a benefit. Sets status to 'discontinued'. Historical periods and usage data are preserved. The benefit stops appearing in active views. Use update_benefit with status='active' to restore.

  • archive_card

    Deactivate a credit card (soft delete). Benefits and usage history are preserved but the card stops appearing in active views. Use card_id from list_cards.

  • bulk_import_cards

    Import multiple credit cards in one call. Accepts natural language names (fuzzy matched against catalog) or exact card_template_ids. Returns per-card results: created, already_exists, ambiguous (with candidates), or failed. IMPORTANT: Use dry_run=true for first-time imports to confirm matches before committing. Household member profiles (owner names) must exist before import — create them first if

  • create_benefitwrite action

    Add a new benefit to a card. Generates periods automatically based on schedule_type. For mid-year additions or perks not yet in the catalog. Returns 409 if a benefit with the same name already exists on the card (catalog-backed or custom). Pass force=true to override and create a duplicate intentionally.

  • create_cardwrite action

    Add a new credit card to the household portfolio. Accepts a card name (fuzzy match) or exact card_template_id from search_catalog. If multiple cards match the name, returns candidates to choose from — call again with the confirmed card_template_id. Supports full metadata on creation (last_four, original_open_date, is_business, etc.) so no follow-up update_card call is needed.

  • create_welcome_offerwrite action

    Record a welcome offer on a card. Tracks bonus amount, spend requirement, deadline, and progress. The agent must explicitly set status to 'earned' after confirming the bonus posted — no auto-earn.

  • delete_retention_offerwrite action

    Delete a retention offer entry from a card's history. Use the event_id from log_retention_offer's response or from get_card's retention_history. For correcting mistakes, removing smoke-test data, etc.

  • get_524_status

    Compute Chase 5/24 eligibility. Returns current count, slots available, which cards count (including external cards not tracked in CreditSync), when the next slot opens, and data quality warnings.

  • get_action_items

    Get prioritized action items ranked by value at risk. 6 item types emitted: benefit_expiring, at_risk_this_period (pattern-backed leakage signal — Phase 8 D), unused_prior_period, fee_renewal (with recommended_action, retention_leverage, historical_offers), negative_roi, welcome_offer_at_risk. Filter via action_types — accepts both category names (expiring, renewal_approaching) and specific respon

  • get_benefit

    Get detailed information about a specific benefit including all historical periods.

  • get_best_card

    Given a spend category, return the best card in the user's portfolio ranked by effective value per dollar spent. Uses stored CPP valuations by default. Accept cpp_override to adjust valuations for specific redemptions.

  • get_calendar_events

    Get benefit deadlines, credit resets, fee renewals, and expiry windows as structured calendar-ready event objects. Use this to intelligently create, skip, or customize calendar reminders based on the user's actual schedule.

  • get_card

    Get a single card's complete picture: all benefits with current period status, captured vs annual fee ROI, renewal timeline, and total value at risk. Use card_id from list_cards.

  • get_dashboard

    Get dashboard metrics: benefits expiring in 30 days, captured this month, total available, and net ROI value (captured vs annual fees).

  • get_earn_rates

    Get earning rates for a specific card. Returns all bonus categories with multipliers, currencies, caps, channel requirements, and CPP-based dollar value per dollar spent.

  • get_transfer_partnerswrite action

    Get all transfer partners for a loyalty currency with transfer ratios. Returns the static partner map — no active bonus data. Use to check if a specific airline/hotel program is reachable from a bank currency.

  • list_benefits

    List all tracked credit card benefits with current period status, amounts, and expiry dates. This includes statement credits, free night certificates, companion certs, lounge passes, and all other card-linked benefits. For standalone items NOT tied to a card (gift cards, vouchers, travel credits), use list_rewards instead. Filter by status (unused/partial/used), card nickname, or expiring within N

  • list_cards

    List all credit cards with issuer (co-brand/marketing label), issuing_bank (actual bank that issues the card — use for application rule logic), annual fee, renewal month, owner, last 4 digits, and benefit count. Note: issuer and issuing_bank can differ for co-branded cards (e.g., Hilton Aspire has issuer=Hilton, issuing_bank=Amex). Use last_four to match cards against external sources (statements,

  • list_programs

    List tracked loyalty programs with balances, CPP valuations, staleness, and transfer partner counts. Use has_balance to cut payload ~80% by excluding zero-balance programs.

  • list_rewards

    List standalone rewards NOT tied to a card — gift cards, travel vouchers, airline credits, coupons, and other items the user added manually. These are separate from card-linked benefits (use list_benefits for free night certificates, companion certs, statement credits, and other benefits that come from a card). Filter by type or status.

  • list_welcome_offers

    List all welcome offers with spend progress, deadline urgency, and bonus valuations. Filter by status, owner, deadline window, or origin (signup vs retention). Each returned offer includes `origin` and `source_event_id` — retention-origin offers link back to the CardEvent retention_offer row that spawned them.

  • log_retention_offer

    Log a retention offer interaction on a card. Builds historical dataset for retention strategy. Prefer structured fields (offer_type, offer_value_dollars/offer_points+offer_currency, outcome) over the legacy accepted boolean — they feed priority scoring and retention analytics. When the offer comes with a spend requirement (e.g., '10K MR after $5K spend in 3 months'), pass spend_requirement + spend

  • mark_benefit_used

    Mark a benefit period as used, partially used, or unused. Use the period_id from list_benefits or get_benefit. If status is omitted, defaults to 'used' (the 90% use case).

  • remove_external_cardwrite action

    Remove an external card from 5/24 tracking. Use when a card is closed or was added by mistake. Only affects external cards — CreditSync-tracked cards are managed via archive_card.

  • remove_rewardwrite action

    Delete a reward permanently. Use when the reward was added by mistake or is no longer relevant.

  • search_catalog

    Search the CreditSync card catalog by issuer or card name. Returns matching templates with IDs, fees, and benefit counts. Use this to find card_template_id for create_card.

  • update_balancewrite action

    Update a loyalty program balance. Supports absolute set or relative delta. Auto-creates the program if it doesn't exist (requires display_name on first call).

  • update_benefitwrite action

    Update a benefit's details. Audit-logged. Amount changes affect future periods only. Use status 'discontinued' to archive a removed perk.

  • update_cardwrite action

    Update card metadata: nickname, notes, original open date, product change history, business flag, 5/24 status, last four digits. All changes are audit-logged. Notes are appended with timestamp, never replaced.

  • update_retention_offerwrite action

    Patch a previously-logged retention offer event in place. event_id and date are immutable; everything else (offer text, scalars, outcome, notes) can be updated. Use this to fix missing offer_currency, clarify offer text, or update outcome if the call was re-escalated. Validation runs on the merged state — e.g., you can't update offer_type to 'points_bonus' without ensuring offer_currency is set. C

  • update_rewardwrite action

    Update a reward's details or mark it as used. Set status to 'used' when the reward has been redeemed.

  • update_welcome_offerwrite action

    Update spend progress or status on a welcome offer. Supports absolute spend or delta. Set status to 'earned' only after confirming the bonus actually posted.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

1 low
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenanceno repository listed3/15
  • Maintainer identityno repository or website to verify2/10

Findings (1)

  • lowNo source repository listedmaint.no-repo
Overall 55/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Creditsync compares

Against every graded Finance MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
55/100
higher than 14% of 1,761 Finance servers
Tools
34
the typical Finance server has 8
Tools that change things
38%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
27
more than 15% of 421 Finance servers with a package

What its tools let an agent do: 16 read · 5 create · 8 change · 5 delete

Install Creditsync in Claude Code, Cursor or VS Code

Runs npx -y @creditsync-pro/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add creditsync -- npx -y @creditsync-pro/mcp
Add to Cursor

Creditsync: common questions

Is Creditsync MCP server safe?
With care: it is graded C, so read the findings first (55/100). Read the Creditsync safety report
How do I install Creditsync?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Creditsync need an API key?
Yes. The registry entry asks for CREDITSYNC_API_KEY.
Is Creditsync maintained?
The latest release is v1.20.1.
What can I use instead of Creditsync?
Servers from other publishers that do the same job: T-Bank MCP server, Khipu MCP server and BankMCP™ MCP server.
How does Creditsync compare with other Finance MCP servers?
safety score 55/100 (higher than 14% of 1,761 Finance servers); tools 34 (the typical Finance server has 8); tools that change things 38% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Creditsync

Same job from other publishers: the closest match first, then the best rated.

  • T-Bank MCP
    T-Bank (Т-Банк) mobile banking: accounts, cards, transfers, bill pay, grocery, tickets, travel
    A
  • Khipu
    MCP server for Khipu — Chilean instant bank-transfer payments (complements Transbank cards)
    B
  • BankMCP™
    Read-only MCP server for your own bank accounts via Enable Banking. Self-hosted, one user.
    A
  • Beancount.io
    Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.
    A
  • E Arveldaja
    Estonian e-arveldaja (RIK e-Financials) accounting — invoices, bank import, reports.
    B