Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Soldefi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
6
downloads a day
local
runs on your machine
268
downloads in 30d
What it does
MCP server for Solana DeFi risk intelligence, paid automatically via x402 micropayments (USDC on Solana or Base). Tools: rug/honeypot scan of any SPL token (mint/freeze-authority, Token-2022 transfer tax, holder concentration, and a live Jupiter buy->sell
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user soldefi-mcp '--' npx -y soldefi-mcp
# 2 — ask your agent for something these tools do
# scan_honeypot, analyze_pools, top_pools and 10 more
Soldefi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
THAll 3 servers
thomenz3 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Soldefi as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user soldefi-mcp '--' npx -y soldefi-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take SOLANA_PRIVATE_KEY (base58 or JSON-array secret key of a DEDICATED Solana wallet holding USDC (pays per call). Configure this and/or EVM_PRIVATE_KEY; the x402 layer settles on whic), EVM_PRIVATE_KEY (0x private key of a DEDICATED wallet holding USDC on Base (pays per call). Configure this and/or SOLANA_PRIVATE_KEY; the x402 layer settles on whichever rail th), SOLANA_RPC_URL (Optional Solana RPC override used to build the payment (e.g. a Helius URL). Only read when SOLANA_PRIVATE_KEY is set.), SOLDEFI_BASE_URL (Base URL of a soldefi Worker. Defaults to the hosted production API (https://soldefi.thomenz.me).), X402_NETWORK (Set to 'base-sepolia' to pay on testnet, which switches BOTH rails (Solana devnet + Base Sepolia). Any other value, including unset, pays on mainnet.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Rug & honeypot scan of a Solana SPL token by mint. On-chain: mint/freeze authority renounced?,
No parameter schema on file.
Deep liquidity-pool analysis for a Solana token across Raydium, Orca, Meteora and pumpswap. Per pool:
No parameter schema on file.
The real best Solana DEX pools: the same top-pools feed a free API returns, but wash-traded and
No parameter schema on file.
Assess how durable a Solana token
No parameter schema on file.
Trace who launched a Solana token: the mint
No parameter schema on file.
Simulate exiting a specific USD amount of a Solana token via a live Jupiter buy->sell round trip: whether
No parameter schema on file.
Answer
No parameter schema on file.
One paid call that bundles the honeypot/sellability scan, liquidity-durability (LP) check, deployer
No parameter schema on file.
Read a Solana wallet
No parameter schema on file.
Scan up to 10 Solana token mints in one paid call and get the full per-token honeypot verdict (0-100 risk
No parameter schema on file.
Re-check up to 10 Solana mints and get back ONLY what moved since you last looked: risk score rises/falls
No parameter schema on file.
Build a ready-to-sign Solana swap (Jupiter) with a rug check in front of it. Buying a token whose verdict
No parameter schema on file.
Free local base58 address-format validation of a single Solana mint. No payment required. Use it to
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Soldefi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.5.2 · scanned 13 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest8d241da8a9f8b36b16d0264339e9cb3fc69b5436ab2fbb7a5d13247e8f5534ac
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (13 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| scan_honeypot | no tags | |
| analyze_pools | no tags | |
| top_pools | no tags | |
| check_lp_status | no tags | |
| check_deployer | no tags | |
| can_i_sell | no tags | |
| check_exit_risk | no tags | |
| full_scan | no tags | |
| scan_wallet_risk | no tags | |
| scan_honeypot_batch | no tags | |
| check_changed | no tags | |
| build_guarded_swap | no tags | |
| validate_mint | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest8d241da8a9f8b36b
Scanned2026-10-13
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.5.2. Pin a release below and the command asks for exactly that one.
0.5.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Soldefi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.