io.github.chrischall/creditkarma-mcp
NPM · CREDITKARMA-MCP
Credit Karma transactions for Claude — spending by category, merchant, and account summary
Available components
Last scanned (5 hours ago)
Scores higher than 94% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 9 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to chrischall/creditkarma-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1410 tokens (~128/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management85
- Stability check failed: the tool surface changed between 3.1.5 and 3.4.0: 0 tool removals, 3 breaking changes, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ck_query_sql" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Package version: 3.3.5 → 3.4.0 functional
- 25 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 24 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 21 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 3.3.4 → 3.3.5 functional
- 19 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 3.3.2 → 3.3.4 functional
- 17 Oct 26 +12
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/creditkarma-mcp@3.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | chrischall/creditkarma-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/chrischall/creditkarma-mcp/.github/workflows/release-please.yml@refs/heads/main |
| Rekor log index | 3691295182 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d04a35b6e5cf303dcdf8df7434738b9fdc2501ff87e9fcac8026af4068a276ea79ab4952a6dde605159205a79642d6cfafc5fc96827206b87303c1ec0 |
Background: How many MCP packages publish verified provenance →
Dependencies 9 packages
| Packages resolved | 9 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ck_forget_session ~100
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ck_get_account_balances ~217
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).
| Name | Type | Req | Description |
|---|---|---|---|
| include_matched | boolean | – | Also list credit-report rows that duplicate a linked account (each names it in matched_to). Default false. |
| refresh | boolean | – | Fetch balances live before reading. Default false (local data only). |
No output schema declared.
No examples provided.
ck_get_account_summary ~43
Return per-account debit, credit, and net totals.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | YYYY-MM-DD |
| start_date | string | – | YYYY-MM-DD |
No output schema declared.
No examples provided.
ck_get_recent_transactions ~50
Return the N most recent transactions. Convenience shortcut for ck_list_transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of transactions to return (default 25; a whole number from 1 to 500) |
No output schema declared.
No examples provided.
ck_get_spending_by_category ~54
Group debit transactions by category and return totals.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Partial account name filter |
| end_date | string | – | YYYY-MM-DD |
| start_date | string | – | YYYY-MM-DD |
No output schema declared.
No examples provided.
ck_get_spending_by_merchant ~74
Return top merchants by total debit spend.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Partial category name filter |
| end_date | string | – | YYYY-MM-DD |
| limit | integer | – | Default 25; a whole number from 1 to 500 |
| start_date | string | – | YYYY-MM-DD |
No output schema declared.
No examples provided.
ck_healthcheck Verify credentials and upstream reachability ~123
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ck_list_transactions ~221
List transactions with optional filters, newest first. Paginated. Reads the local database (filled by ck_sync_transactions). view "brief" answers one line per transaction instead of JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Partial account name match |
| category | string | – | Partial category name match |
| end_date | string | – | YYYY-MM-DD |
| limit | integer | – | Default 50; a whole number from 1 to 500 |
| max_amount | number | – | Maximum absolute amount |
| merchant | string | – | Partial merchant name match |
| min_amount | number | – | Minimum absolute amount |
| offset | integer | – | Default 0; a whole number, 0 or more |
| start_date | string | – | YYYY-MM-DD |
| status | string | – | e.g. posted, pending, cancelled |
| view | string | – | "full" (default) returns the JSON page; "brief" returns one line per transaction: merchant and signed amount — date (YYYY-MM-DD, or "no date") — status. |
No output schema declared.
No examples provided.
ck_query_sql ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_rows | integer | – | Most rows to return (default 500). Page larger results with LIMIT/OFFSET. |
| sql | string | yes | A SELECT SQL statement |
No output schema declared.
No examples provided.
ck_set_session ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cookies | string | yes | Full Cookie header from a signed-in creditkarma.com request (contains CKAT, CKTRKID, etc.) |
No output schema declared.
No examples provided.
ck_sync_transactions ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| force_full | boolean | – | If true, walk the whole history with no date cutoff. Starts from the beginning, except that it continues a full backfill paused by max_pages. Also the way to restart after a sync that failed or stopp… |
| max_pages | integer | – | Pages this call may fetch before pausing (a deep backfill is hundreds). Overrides CK_SYNC_MAX_PAGES. Omit both for an unbounded sync. |
No output schema declared.
No examples provided.
How do I install the io.github.chrischall/creditkarma-mcp server?
io.github.chrischall/creditkarma-mcp runs locally as an npm package, launched with npx -y creditkarma-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · creditkarma-mcp
claude mcp add chrischall-creditkarma-mcp -- npx -y creditkarma-mcp
What is the io.github.chrischall/creditkarma-mcp server?
io.github.chrischall/creditkarma-mcp is listed in the public MCP registry as io.github.chrischall/creditkarma-mcp. Credit Karma transactions for Claude, spending by category, merchant, and account summary. This page covers its npm package (creditkarma-mcp).
Is the io.github.chrischall/creditkarma-mcp server safe to use?
io.github.chrischall/creditkarma-mcp scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.chrischall/creditkarma-mcp server expose?
io.github.chrischall/creditkarma-mcp exposes 11 tools: ck_healthcheck, ck_set_session, ck_forget_session, ck_sync_transactions, ck_list_transactions, and 6 more. Their descriptions and schemas cost roughly 1,410 tokens of context every time the server is loaded.
Is the io.github.chrischall/creditkarma-mcp server still maintained?
io.github.chrischall/creditkarma-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.chrischall/creditkarma-mcp server under?
io.github.chrischall/creditkarma-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.