creditkarma-mcp

MCPattested
v3.1.4Claude CodeMITUpdated 3d agonpmGitHub

MCP server for Credit Karma — natural-language access to your transactions, spending, and accounts

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
818Downloads/wk
1GitHub stars
1Forks
3d agoLast update
Reads these credentials
  • CK_COOKIESAPI keyoptional

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorClaude Code
LicenseMIT
Version3.1.4
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 5ff2a67
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface8 tools · 1 privileged
Security scan✓ Cleanv2.2.3 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · 1 privileged
Statically extracted from the published packagev2.2.3 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

ck_set_sessionNo description published

This tool published no description. Forge does not invent one.

ck_list_transactionsNo description published

This tool published no description. Forge does not invent one.

ck_get_recent_transactionsNo description published

This tool published no description. Forge does not invent one.

ck_get_spending_by_categoryNo description published

This tool published no description. Forge does not invent one.

ck_get_spending_by_merchantNo description published

This tool published no description. Forge does not invent one.

ck_get_account_summaryNo description published

This tool published no description. Forge does not invent one.

ck_query_sqlprivilegedNo description published

This tool published no description. Forge does not invent one.

ck_sync_transactionsNo description published

This tool published no description. Forge does not invent one.

0 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for Credit Karma — natural-language access to your transactions, spending, and accounts

Keywords
mcpmodel-context-protocolclaudeaicredit-karmatransactionsspendingaccountsbudgetingpersonal-financesqlitegraphql
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in databases