Recon Crypto MCP Server

Safety first. Hardware-verified DeFi for AI agents — designed for when the AI can be compromised.

Remote serverstreamable-http

What is the Recon Crypto MCP MCP server?

Safety first. Hardware-verified DeFi for AI agents — designed for when the AI can be compromised. The recon crypto mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

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.

  • Portfolio — — cross-chain balances, DeFi position aggregation, USD totals, NFT collections (EVM + Solana via Helius DAS), wallet-level PnL (mtd / ytd / 30d / 7d / 1d), daily briefing
  • Positions — — Aave, Compound, Morpho, Uniswap V3 LP, Curve, MarginFi, Kamino, Safe (Gnosis) multisig; multi-protocol health-factor alerts; liquidation-risk simulation
  • Staking — — Lido (stake / unstake / stETH↔wstETH wrap) + EigenLayer + Rocket Pool (EVM); TRON Stake 2.0 (freeze / unfreeze / vote / claim); Solana (Marinade, Jito, native delegate/deactivate/withdraw)
  • Swaps + bridges — — LiFi (EVM + EVM↔Solana + TRON + BTC routes, optional 1inch cross-check), Jupiter v6 (Solana), direct Uniswap V3, Curve, SunSwap (TRON)
  • Utilities — — ENS resolution, symbol→contract resolve_token registry, token balances, allowance enumeration, tx status, explain_tx post-hoc decode, compare_yields across lending + LST adapters
  • Demo mode — — curated personas (whale / defi-degen / stable-saver / staking-maxi) for first contact with no RPC keys / Ledger / config file

Its toolset

Everything the assistant can do here goes through one of these:

  • get_lp_positions — Uniswap V3 LP + IL estimate
  • get_solana_staking_positions — Marinade + Jito + native stake-account enumeration with activation status and SOL-equivalent valuation
  • get_compound_market_info — wallet-less Comet snapshot
  • compare_yields — rank lending APRs across Aave / Compound / Morpho / Marinade / Jito / Kamino-lend / MarginFi
  • get_marginfi_diagnostics — banks the bundled SDK skipped, with root cause
  • get_transaction_history — merged tx reader (external / ERC-20 / internal / Solana program_interaction) with 4byte-decoded methods + historical USD
  • get_transaction_status — poll inclusion by hash
  • explain_tx — post-hoc decode of a historical tx
  • simulate_transaction — EVM eth_call preview (Solana equivalent runs inside preview_solana_send)
  • get_solana_setup_status — probe nonce + MarginFi account PDAs
  • get_vaultpilot_config_status — local config diagnostic (RPC sources, key presence, paired-account counts, WC topic suffix, skill state). Booleans / counts only — no secret values
  • prepare_uniswap_swap — direct V3 swap, same-chain, auto-picks fee tier across 100/500/3000/10000 bps. Use only when the user names Uniswap; otherwise prefer LiFi

Configuration

You will need 8 environment variables: ETHEREUM_RPC_URL, ARBITRUM_RPC_URL, POLYGON_RPC_URL, BASE_RPC_URL, SOLANA_RPC_URL, RPC_API_KEY, ETHERSCAN_API_KEY, ONEINCH_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js ≥ 18.17 - Zero-config reads: PublicNode (EVM) + Solana public mainnet — rate-limited but enough for first contact and light use. - Real use: custom RPC (Infura / Alchemy / Helius / QuickNode / Triton) via env vars or vaultpilot-mcp setup. - Optional keys (prompted on demand): Etherscan, 1inch (enables swap-quote comparison), WalletConnect project ID (required for EVM

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Recon Crypto MCP's toolset — get_lp_positions, get_solana_staking_positions, get_compound_market_info and 11 more — is a fair guide to whether it matches your workflow. It is maintained by szhygulin; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Recon Crypto MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the recon crypto mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
get_lp_positionsUniswap V3 LP + IL estimate
get_solana_staking_positionsMarinade + Jito + native stake-account enumeration with activation status and SOL-equivalent valuation
get_compound_market_infowallet-less Comet snapshot
compare_yieldsrank lending APRs across Aave / Compound / Morpho / Marinade / Jito / Kamino-lend / MarginFi
get_marginfi_diagnosticsbanks the bundled SDK skipped, with root cause
get_transaction_historymerged tx reader (external / ERC-20 / internal / Solana program_interaction) with 4byte-decoded methods + historical USD
get_transaction_statuspoll inclusion by hash
explain_txpost-hoc decode of a historical tx
simulate_transactionEVM eth_call preview (Solana equivalent runs inside preview_solana_send)
get_solana_setup_statusprobe nonce + MarginFi account PDAs
get_vaultpilot_config_statuslocal config diagnostic (RPC sources, key presence, paired-account counts, WC topic suffix, skill state). Booleans / counts only — no secret values.
prepare_uniswap_swapdirect V3 swap, same-chain, auto-picks fee tier across 100/500/3000/10000 bps. Use only when the user names Uniswap; otherwise prefer LiFi
prepare_custom_callescape hatch for arbitrary verified-contract calls (acknowledgeNonProtocolTarget: true gate; bypasses the canonical-dispatch allowlist by design)
prepare_tron_native + TRC-20 transfers, WithdrawBalance, Stake 2.0, vote, claim rewards, TRC-20 approve, LiFi swap, SunSwap swap (prepare_sunswap_swap)

How to install the Recon Crypto MCP MCP server

{
  "mcpServers": {
    "recon-crypto": {
      "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",
        "SOLANA_RPC_URL": "your-value",
        "RPC_API_KEY": "your-value",
        "ETHERSCAN_API_KEY": "your-value",
        "ONEINCH_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js ≥ 18.17 - Zero-config reads: PublicNode (EVM) + Solana public mainnet — rate-limited but enough for first contact and light use. - Real use: custom RPC (Infura / Alchemy / Helius / QuickNode / Triton) via env vars or vaultpilot-mcp setup. - Optional keys (prompted on demand): Etherscan, 1inch (enables swap-quote comparison), WalletConnect project ID (required for EVM
VariableDescriptionRequired
ETHEREUM_RPC_URLEndpoint or connection string the server talks to.Yes
ARBITRUM_RPC_URLEndpoint or connection string the server talks to.Yes
POLYGON_RPC_URLEndpoint or connection string the server talks to.Yes
BASE_RPC_URLEndpoint or connection string the server talks to.Yes
SOLANA_RPC_URLEndpoint or connection string the server talks to.Yes
RPC_API_KEYCredential the server authenticates with.Yes
ETHERSCAN_API_KEYCredential the server authenticates with.Yes
ONEINCH_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Recon Crypto MCP to get lp positions.
  • Use Recon Crypto MCP to get solana staking positions.
  • Use Recon Crypto MCP to get compound market info.

Frequently asked questions

It connects Recon Crypto MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (get_lp_positions, get_solana_staking_positions, get_compound_market_info, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Recon Crypto MCP directly.