Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Beschreibung vom Entwickler (englisches Original)
Self-custodial crypto + DeFi MCP for AI agents. Ledger-signed. EVM, TRON, Solana, BTC, LTC.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
ETHEREUM_RPC_URL, ARBITRUM_RPC_URL, POLYGON_RPC_URL, BASE_RPC_URL, RPC_PROVIDER, RPC_API_KEY, ETHERSCAN_API_KEY, ONEINCH_API_KEY, WALLETCONNECT_PROJECT_ID, VAULTPILOT_DEMOAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"vaultpilot": {
"command": "npx",
"args": [
"-y",
"vaultpilot-mcp"
],
"env": {
"ETHEREUM_RPC_URL": "your-value",
"ARBITRUM_RPC_URL": "your-value",
"POLYGON_RPC_URL": "your-value",
"BASE_RPC_URL": "your-value",
"RPC_PROVIDER": "your-value",
"RPC_API_KEY": "your-value",
"ETHERSCAN_API_KEY": "your-value",
"ONEINCH_API_KEY": "your-value",
"WALLETCONNECT_PROJECT_ID": "your-value",
"VAULTPILOT_DEMO": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add vaultpilot --env ETHEREUM_RPC_URL=your-value --env ARBITRUM_RPC_URL=your-value --env POLYGON_RPC_URL=your-value --env BASE_RPC_URL=your-value --env RPC_PROVIDER=your-value --env RPC_API_KEY=your-value --env ETHERSCAN_API_KEY=your-value --env ONEINCH_API_KEY=your-value --env WALLETCONNECT_PROJECT_ID=your-value --env VAULTPILOT_DEMO=your-value -- npx -y vaultpilot-mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"vaultpilot": {
"command": "npx",
"args": [
"-y",
"vaultpilot-mcp"
],
"env": {
"ETHEREUM_RPC_URL": "your-value",
"ARBITRUM_RPC_URL": "your-value",
"POLYGON_RPC_URL": "your-value",
"BASE_RPC_URL": "your-value",
"RPC_PROVIDER": "your-value",
"RPC_API_KEY": "your-value",
"ETHERSCAN_API_KEY": "your-value",
"ONEINCH_API_KEY": "your-value",
"WALLETCONNECT_PROJECT_ID": "your-value",
"VAULTPILOT_DEMO": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"vaultpilot": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vaultpilot-mcp"
],
"env": {
"ETHEREUM_RPC_URL": "your-value",
"ARBITRUM_RPC_URL": "your-value",
"POLYGON_RPC_URL": "your-value",
"BASE_RPC_URL": "your-value",
"RPC_PROVIDER": "your-value",
"RPC_API_KEY": "your-value",
"ETHERSCAN_API_KEY": "your-value",
"ONEINCH_API_KEY": "your-value",
"WALLETCONNECT_PROJECT_ID": "your-value",
"VAULTPILOT_DEMO": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
ETHEREUM_RPC_URL envARBITRUM_RPC_URL envPOLYGON_RPC_URL envBASE_RPC_URL envRPC_PROVIDER envVAULTPILOT_DEMO envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto szhygulin bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: RPC_API_KEY, ETHERSCAN_API_KEY, ONEINCH_API_KEY, WALLETCONNECT_PROJECT_ID
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.14.4) kam vor 6 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Finance Toolkit, SolidInvoice, Korea Tax Calculator
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Self-custodial DeFi for AI agents. The agent proposes, you approve on your Ledger — designed for the threat model where the agent, MCP, and host can all be compromised. Only the device is trusted; private keys never leave it.
Read on-chain positions and prepare transactions across Ethereum, Arbitrum, Polygon, Base, Optimism, TRON, Solana, Bitcoin, and Litecoin. Supported protocols: Aave V3, Compound V3, Morpho Blue, Uniswap V3 (swap + LP verbs), Curve, Lido, EigenLayer, Rocket Pool, Safe (Gnosis) multisig on EVM, MarginFi, Kamino, Marinade, Jito on Solana, SunSwap on TRON, plus LiFi (EVM + EVM↔Solana + TRON + BTC swap/bridge) and Jupiter v6 (Solana swap), with 1inch as an optional EVM quote cross-check. EVM signs over WalletConnect → Ledger Live; TRON, Solana, Bitcoin and Litecoin sign over USB HID directly to the device (Ledger Live's WalletConnect bridge does not support those namespaces today). Works with Claude Code (CLI/terminal), Cursor, and any MCP-compatible client over stdio. Claude.ai chat (web + native desktop app) needs a hosted MCP endpoint — on the roadmap, not yet shipped.
Agents: read [AGENTS.md](./AGENTS.md). One-line prompt to paste into Claude Code / Cursor / any MCP-capable agent:
`
Install VaultPilot MCP from https://github.com/szhygulin/vaultpilot-mcp following AGENTS.md.
`
mtd / ytd / 30d / 7d / 1d), daily briefingprepare_custom_call escape hatch for arbitrary verified-contract calls. Solana sends use a per-wallet durable-nonce account so Ledger review doesn't race the ~60s blockhash window; every Solana prepare runs a simulateTransaction gate so program-level reverts fail at prepare time, not on broadcast.verify_tx_decode for second-LLM bytes-vs-intent cross-check, signed on-disk contacts/address-bookresolve_token registry, token balances, allowance enumeration, tx status, explain_tx post-hoc decode, compare_yields across lending + LST adapterswhale / defi-degen / stable-saver / staking-maxi) for first contact with no RPC keys / Ledger / config fileCompromise model: the AI agent, MCP server, and host computer can all be attacker-controlled. Only the Ledger is trusted. Every transaction is cryptographically bound across each layer so tampering — a swapped recipient, a rewritten swap route, a smuggled approval — is tamper-evident on the device screen before signing.
user-intent ──► agent ──► MCP server ──► WalletConnect / USB-HID ──► Ledger Live / host ──► Ledger device
Defense in depth: server-side prepare↔send fingerprint, independent 4byte.directory selector check, agent-side ABI decode + pre-sign hash recompute, on-device clear-sign or blind-sign-hash match, WalletConnect session-topic cross-check, previewToken/userDecision gate, and get_verification_artifact for second-LLM cross-verification on high-value flows. See [SECURITY.md](./SECURITY.md) for the full threat model, defenses table, residual risks, and verification recipes.
The MCP's own CHECKS PERFORMED directives can be silently omitted by a compromised server. Install the companion vaultpilot-security-skill so the agent enforces cryptographic-integrity invariants regardless of what the MCP says — bytes decode, dispatch-target allowlist, hash recompute, chain-must-be-explicit, bridge-recipient cross-check, approval-class surfacing, mandatory second-LLM on hard-trigger ops, set-level intent verification, durable-binding source-of-truth:
git clone https://github.com/szhygulin/vaultpilot-security-skill.git \
~/.claude/skills/vaultpilot-preflight
Restart Claude Code. The skill file's SHA-256 is pinned in the server source; on-disk tamper or plugin collision surfaces as integrity check FAILED.
/setup (optional)For chat-driven onboarding that detects current config and only collects keys you actually need, install the companion vaultpilot-setup-skill:
git clone https://github.com/szhygulin/vaultpilot-setup-skill.git \
~/.claude/skills/vaultpilot-setup
Restart, then type /setup.
EVM — Ethereum, Arbitrum, Polygon, Base, Optimism. Lido reads on Ethereum + Arbitrum, Lido writes Ethereum-only. EigenLayer + Morpho Blue + Rocket Pool Ethereum-only. Compound V3 + Aave V3 + Uniswap V3 + LiFi + Safe multisig span all five chains; per-protocol address coverage varies — readers short-circuit cleanly where a protocol isn't deployed.
TRON — TRX + canonical TRC-20 stablecoins (USDT, USDC, USDD, TUSD); Stake 2.0 freeze/unfreeze/withdraw-expire-unfreeze + voting-reward claims; SunSwap (same-chain TRX↔TRC-20 swaps); LiFi-routed TRON↔EVM bridging. No lending/LP (Aave/Compound/Morpho/Uniswap aren't deployed). Pair once per session via pair_ledger_tron.
Solana — SOL + SPL balances, MarginFi + Kamino lending, Marinade / Jito / native stake-account reads with SOL-equivalent valuation, Jupiter v6 quotes, Helius DAS NFT portfolio. Writes cover SOL/SPL transfers, MarginFi + Kamino supply/withdraw/borrow/repay, Jupiter swaps, Marinade stake + immediate-unstake, Jito stake-pool deposit, native SOL delegate/deactivate/withdraw, and LiFi-routed EVM↔Solana bridging. Per-wallet durable-nonce account (~0.00144 SOL rent, reclaimable) protects sends from blockhash expiry during Ledger review (prepare_solana_nonce_init / _close). SPL / MarginFi / Kamino / Jupiter / Jito blind-sign against a Message Hash — enable Allow blind signing in the Solana app's Settings; SOL native transfers clear-sign. Pair once per session via pair_ledger_solana.
Bitcoin + Litecoin — balance, UTXO, fee-estimate, and tx-history readers via Esplora (mempool.space / litecoinspace.org). Native segwit + taproot sends, BIP-125 RBF fee-bumps, multisig PSBT (combine / sign / finalize), BIP-137 message signing, LiFi-routed BTC→EVM/Solana swaps. Optional Bitcoin Core / Litecoin Core JSON-RPC unlocks forensic tools that Esplora cannot serve (chain tips, block stats, mempool summary) — see INSTALL.md §9 for setup. Pair once via pair_ledger_btc / pair_ledger_ltc.
Ledger Live's WalletConnect bridge does not honor the tron: namespace (verified 2026-04-14) or expose Solana accounts (verified 2026-04-23) or expose BTC/LTC namespaces, which is why those paths use USB HID. Readers short-circuit cleanly on chains where a protocol isn't deployed.
ROADMAP.md.
~190 tools across read / pair-Ledger / prepare / sign+send / verify / diagnostic categories. Highlights below; each tool has a Zod input schema and verbose description — query the MCP server's tools/list for the canonical surface.
Portfolio + positions (read-only):
get_portfolio_summary, get_portfolio_diff, get_pnl_summary, get_daily_briefing — cross-chain USD aggregation; optional tronAddress / solanaAddress fold those chains inget_lending_positions (Aave), get_compound_positions, get_morpho_positions, get_marginfi_positions, get_kamino_positions, get_curve_positions, get_safe_positions — per-protocol positions + health factorsget_lp_positions — Uniswap V3 LP + IL estimateget_staking_positions, get_staking_rewards, estimate_staking_yield — Lido + EigenLayer + Rocket Poolget_solana_staking_positions — Marinade + Jito + native stake-account enumeration with activation status and SOL-equivalent valuationget_tron_staking, list_tron_witnesses — TRON Stake 2.0 state + SR listget_nft_portfolio (EVM + Solana DAS), get_nft_collection, get_nft_history, get_nft_listings (EVM)get_btc_balance / _balances / _account_balance / _multisig_balance / _multisig_utxos / _tx_history / _fee_estimates, get_ltc_balance — BTC + LTC reads via Esploraget_compound_market_info — wallet-less Comet snapshotget_health_alerts, simulate_position_change — multi-protocol liquidation-risk toolingcompare_yields — rank lending APRs across Aave / Compound / Morpho / Marinade / Jito / Kamino-lend / MarginFiget_marginfi_diagnostics — banks the bundled SDK skipped, with root causeTokens, prices, history:
get_token_balance, get_token_price, get_token_metadata, get_token_allowances, get_coin_price — balances + DefiLlama prices on EVM/TRON/Solana; get_token_metadata detects EIP-1967 proxiesget_transaction_history — merged tx reader (external / ERC-20 / internal / Solana program_interaction) with 4byte-decoded methods + historical USDget_transaction_status — poll inclusion by hashexplain_tx — post-hoc decode of a historical txresolve_token, resolve_ens_name, reverse_resolve_ensForensic chain reads (require Bitcoin/Litecoin Core RPC):
get_btc_block_tip / _block_stats / _blocks_recent / _chain_tips / _mempool_summary, get_ltc_* equivalentsbuild_incident_report, get_market_incident_status — Compound/Aave pause + utilization scan and BTC/LTC chain-tip / mempool-anomaly bundleQuotes + security signals:
get_swap_quote (LiFi, EVM), get_solana_swap_quote (Jupiter v6)check_contract_security, check_permission_risks, get_protocol_risk_score, get_contract_abi, read_contractsimulate_transaction — EVM eth_call preview (Solana equivalent runs inside preview_solana_send)verify_tx_decode, get_verification_artifact, get_tx_verification — second-LLM cross-verification + 15-min-TTL handle re-emit (details)Diagnostics:
get_solana_setup_status — probe nonce + MarginFi account PDAsget_vaultpilot_config_status — local config diagnostic (RPC sources, key presence, paired-account counts, WC topic suffix, skill state). Booleans / counts only — no secret values.get_ledger_device_info, get_ledger_status, verify_ledger_attestation / _firmware / _live_codesign — device + session discovery, on-device attestation, firmware-version pinContacts + read-only sharing:
add_contact / `remNur der Anfang wird gezeigt; den Rest findest du im Repo