Magpie MCP server
io.github.magpiecapital/magpie-mcp·v0.1.1·7 starsAgent-native lending on Solana via x402: borrow against tokens, arm in-vault TP/SL, repay.
7 stars35 downloads/wk
Reviews
Write oneNobody has reviewed Magpie yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Magpie tools (26, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
magpie_arm_exitArm a self-owned in-vault exit (take-profit / stop-loss / trailing) on YOUR OWN active V4 loan. When the trigger fires, the collateral is auto-sold IN-VAULT: SOL (or USDC) accumulates inside the loan's per-loan proceeds vault and the loan stays Active — the proceeds only leave to your wallet via your own borrower-signed repay. Pick exactly one trigger: target (e.g. '2x' TP / '0.7x' SL), price_usd,
magpie_build_borrowBuild an UNSIGNED borrow transaction. Server runs the full anti-exploit gate eval (ban registry, TWAP, pool floor, cross-source price, RWA-only guard, etc.) and returns a partial-signed tx. Agent signs locally and submits to magpie.capital/api/v1/cosign-borrow. Set has_exit_arming=true to route the loan into the V4 in-vault exit pool so you can later arm self-owned TP/SL exits on it (via magpie_ar
magpie_build_depositBuild an UNSIGNED LP-deposit transaction (wraps SOL → wSOL → deposits into the main LendingPool → closes wSOL ATA). Agent signs and submits. Paid: 0.002 SOL.
magpie_build_liquidateBuild an unsigned liquidate-loan tx for a past-due active loan. The keeper (your wallet) receives keeper_reward_bps share of the seized collateral as bounty; the rest goes to the lender authority for pool recovery. Permissionless — any wallet can liquidate. Server pre-validates the loan exists, is active, and is past due. Paid: 0.003 SOL. Workflow: poll magpie_liquidatable to find candidates, then
magpie_build_repayBuild an unsigned repay tx for an existing loan. Paid: 0.002 SOL.
magpie_build_withdrawBuild an unsigned LP-withdraw tx for the requested shares. Server pre-validates the on-chain position and refuses chunks larger than max_safe_shares. Paid: 0.002 SOL.
magpie_cancel_exitwrite actionCancel an armed in-vault exit order on your own V4 loan. The loan stays Active and unaffected; only the pending auto-sell is removed. Signed with the configured payer keypair (payer==signer). FREE.
magpie_collateral_eligibleCatalog of every token currently approved as Magpie collateral. Mint, symbol, decimals, category. First-touch endpoint for new agent integrations. Free, 1h cache.
magpie_create_intentwrite actionPost a CONDITIONAL borrow intent. Bot watches the trigger condition (price_above / price_below / time_after / pool_liq_above) and builds the unsigned tx when matched. Single payment covers entire intent lifecycle. Paid: 0.01 SOL. Optional webhook_url — server POSTs an HMAC-SHA256-signed payload on match instead of forcing you to poll. The webhook_secret is returned ONCE in the response; persist it
magpie_credit_leaderboardTop wallets ranked by Magpie credit score (anonymized to Xxxx…Yyyy). Free, 60s cache.
magpie_credit_scoreMagpie credit score (300-850) + tier benefits for a wallet. Paid: 0.001 SOL per lookup.
magpie_get_intentPoll the status of a conditional borrow intent. When status='matched', the response includes partial_signed_tx_b64 ready to sign + submit. Paid: 0.0005 SOL per poll.
magpie_liquidatableActive loans at or past their on-chain due timestamp — the canonical liquidation-bot data feed. Sorted most-past-due-first. Use within_seconds for pre-positioning. Free, 8s cache.
magpie_list_exitsList the armed in-vault exit orders for a wallet — each order's loan, direction, trigger, distance-to-trigger, and status. Use to audit what's armed before modifying or cancelling. FREE.
magpie_loanFetch a single Magpie loan by its u64 ID. Free.
magpie_loan_by_pdaFetch a single Magpie loan by its on-chain loan PDA (account address). Returns the loan's program version, status, collateral, due timestamp, and (for V4) proceeds-vault context. FREE.
magpie_lp_stateRead a wallet's LP position in the main LendingPool — shares, deposited lamports, current value, yield earned, share-of-pool, plus pool context. Free, 10s cache.
magpie_modify_exitModify an existing armed in-vault exit order on your own V4 loan — change its trigger or execution params without cancelling and re-arming. Signed with the configured payer keypair (payer==signer). FREE.
magpie_pool_stateGet live on-chain Magpie LendingPool state — totalDeposits, totalBorrowed, totalShares, utilization, fees earned. Free, 15s cache.
magpie_poolsList the Magpie lending pools (program versions and their pool context) — V1 memecoin and V4 in-vault-exit lanes. FREE.
magpie_protocol_pulse24h protocol aggregates: active loans, active borrowers, borrows in last 1h + 24h, borrow volume in SOL, repays, liquidations. Pure aggregates, no per-wallet data. Free, 30s cache.
magpie_recent_activityAnonymized recent borrow/repay/liquidate events across the protocol. Wallets reduced to Xxxx…Yyyy. Useful as 'is this protocol active right now' signal. Free, 15s cache.
magpie_simulate_borrowPreview a loan WITHOUT submitting. Pure math from caller-supplied prices + the public tier constants. Use tier='all' to compare all three tiers. Free.
magpie_tiersMagpie loan tier constants — three fixed tiers (Express / Quick / Standard) with their LTV, duration, and fee parameters. Free, 1h cache.
magpie_token_riskPer-token risk profile from Magpie's internal risk engine — risk score (0-100), dimension breakdown (volatility, liquidity, concentration, volume, rug_pull), market data, max allowed LTV the program will enforce, operator flags. Useful pre-borrow collateral check. Paid: 0.001 SOL per lookup.
magpie_wallet_loansAll loans owned by a wallet. Optional ?status filter. Free, 8s cache.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 12 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Findings (1)
- mediumeval / new Function used
exec.evaldist/index.js: … Server runs the full anti-exploit gate eval (ban registry, TWAP, pool floor, cross-so…
How Magpie compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 65% of 4,460 AI and agents servers
- Tools
- 26
- the typical AI and agents server has 6
- Tools that change things
- 8%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 7
- more than 81% of 2,711 AI and agents servers
- Downloads a week
- 35
- more than 25% of 1,538 AI and agents servers with a package
What its tools let an agent do: 24 read · 2 change
Install Magpie in Claude Code, Cursor or VS Code
Runs npx -y @magpieloans/magpie-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add magpie-mcp -- npx -y @magpieloans/magpie-mcp
What the publisher says
From the Magpie repository's README, as published. We do not edit it. Read it on GitHub
magpie-x402
Solana lending protocol — liquidity without selling your bag.
Borrow SOL against your memecoins, tokenized stocks, and RWAs — and set take-profits and stops on that same collateral. Liquidity now, upside intact: collateral that can still sell itself.
x402 payment-required API endpoints for the Magpie Capital protocol. AI agents and other Solana protocols can pay-per-call for credit scores, token risk assessments, and protocol analytics — no API keys, no signups, just a Solana payment. Agents borrow programmatically: pay per call, get back an unsigned Solana transaction, sign and submit it yourself (the service holds zero keys).
Take-profit, stop-loss, ladders, trailing stops — they fire on-chain into your loan's vault, the loan stays open, and proceeds reach your wallet only when you repay. Auto-sell exits are V4 in-vault orders on supported collateral (memecoins + tokenized stocks/RWAs); they are auto-sell orders that fire on-chain through a slippage stack, not guaranteed fills.
AI agent
│
│ GET /api/v1/credit-score?wallet=…
▼
┌────────────────────┐
│ 402 Payment │
│ Required │ ← scheme, recipient, amount, nonce
└─────────┬──────────┘
│
│ Solana tx
▼ (transfer to MAGPIE_PAY_TO
┌────────────────────┐ + memo `magpie-x402:<nonce>`)
│ on-chain ↪ Solana │
└─────────┬──────────┘
│
│ retry GET with header X-Payment: <signature>
▼
┌────────────────────┐
│ Service verifies │ ← amount, recipient, mint, memo nonce,
│ payment on-chain │ nonce not previously consumed
└─────────┬──────────┘
│
▼
{ score, tier, … }What this is (and isn't)
- ✅ An open standard implementation. x402 is HTTP 402 Payment Required, designed for AI-agent-payable APIs.
- ✅ A revenue path for protocol data. Magpie's credit oracle, token risk scores, and analytics are useful to OTHER protocols and agents — this is how they pay for that access.
- ✅ Public-data-only. Every response field corresponds to data already verifiable on-chain via solscan.io or in the magpie-bot source.
- ❌ Not custodial. This service holds no keys, signs no transactions, cannot move any user funds. Even a full RCE on this host can't drain a user — see SECURITY.md.
Endpoints
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Magpie: common questions
- Is Magpie MCP server safe?
- Mostly: it is graded B (82/100). Read the Magpie safety report
- How do I install Magpie?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Magpie need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Magpie maintained?
- The last commit was 51 days ago (2026-09-14). The latest release is v0.1.1.
- What can I use instead of Magpie?
- Servers from other publishers that do the same job: Commonly MCP server, Agent-Native Slides MCP server and IWE (iwe.md) MCP server.
- How does Magpie compare with other AI and agents MCP servers?
- safety score 82/100 (higher than 65% of 4,460 AI and agents servers); tools 26 (the typical AI and agents server has 6); tools that change things 8% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Magpie
Same job from other publishers: the closest match first, then the best rated.
- CommonlyRead Commonly pods and post as a Commonly agent you create, with a token from your Commonly account.not reviewedEstablishedA
- Agent-Native SlidesAgent-Native Google Slides - generate and edit React presentationsnot reviewedEstablishedA
- IWE (iwe.md)Markdown knowledge base as agent memory. Runs against the notes directory it is started in.not reviewedEstablishedA
- Ts CoreAgent-native TypeScript framework for building MCP servers.not reviewedEstablishedA
- mcptoonMCP tools + agent skills in one zero-dependency CLI: 71,929 -> 581 tokens (-99.2%, measured).not reviewedEstablishedA