Resolves the credential the way real tools do, then makes one authenticated request to creditkarma.com. Reports which source supplied the credential, whether creditkarma.com accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a creditkarma.com-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke — steps reports credential lookup, token validity, refresh and probe separately, and failed_step names the first that failed.

Store a Credit Karma session to enable automatic token refresh. Pass the full Cookie header from a signed-in creditkarma.com request (Chrome DevTools → Network → any creditkarma.com request → Request Headers → right-click the cookie header → Copy value). For most users the easier onboarding path is to install the ContextMint Bridge extension and sign into creditkarma.com — the MCP reads the cookies automatically.

Forget the Credit Karma session on this machine: delete the saved-session file (~/.creditkarma-mcp/session, or CK_SESSION_PATH) that ck_set_session and token refreshes write, and clear the credentials held in memory. Use when the user stops using this server or wants their stored login removed. Local only — Credit Karma is not contacted, synced transactions are kept, and a CK_COOKIES value set in the host config is not changed.

Sync Credit Karma transactions into the local SQLite database, then refresh account balances once (see ck_get_account_balances; a balance failure is reported in balances, never thrown; a call that pauses with more to fetch leaves balances to the call that finishes). Incremental by default (fetches since last sync + 30-day overlap for updates). There is no login flow: credentials are re-read from the saved session (ck_set_session), CK_COOKIES, or a signed-in creditkarma.com tab via the ContextMint Bridge extension; if none is usable it fails with an error saying how to sign back in. Bounded and resumable: when it pauses with more to fetch it returns another_run_needed:true and a note — run it again and it continues from where it stopped.

List transactions with optional filters. Paginated.

Return the N most recent transactions. Convenience shortcut for ck_list_transactions.

Group debit transactions by category and return totals.

Return top merchants by total debit spend.

Return per-account debit, credit, and net totals.

Current balance of every account: institution, type, last 4, current balance, available credit and credit limit (cards), and the as-of time. Reads the local database (filled by ck_sync_transactions); pass refresh:true to fetch live first. source "linked" = a linked bank, card, loan or investment account, live from the account aggregator (refreshed about daily). source "credit_report" = a card or loan from the credit report (2–5 weeks old, no last 4); one that duplicates a linked account is hidden unless include_matched:true. Liabilities are negative, matching transactions; available credit is limit minus balance. stale is true past 7 days (linked) or 35 days (credit report).

Execute a raw SQL SELECT query (CTEs via WITH ... SELECT are supported) against the transactions database. Non-SELECT statements (INSERT, UPDATE, DELETE, DROP, etc.) are rejected. Returns at most max_rows rows (default 500, max 5000); a larger result comes back with truncated: true, so prefer aggregates or LIMIT/OFFSET paging. A query running longer than 10 s is stopped. Only the first statement runs. Tables: transactions, accounts, categories, merchants, sync_state.