Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Magpie MCP

by magpiecapitalversion 0.1.1i★ 7 (Stars for the whole repo)iRuns on your computerOfficial site ↗
Registry nameio.github.magpiecapital/magpie-mcp

How to install

What it does

Agent-native lending on Solana via x402: borrow against tokens, arm in-vault TP/SL, repay.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Crypto & blockchain

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity4/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score11/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Magpie MCP. Follow https://mcp.popnx.com/i/magpiecapital-magpie-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Magpie MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "magpie": { "command": "npx", "args": [ "-y", "@magpieloans/magpie-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Magpie MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "magpie": {
          "command": "npx",
          "args": [
            "-y",
            "@magpieloans/magpie-mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Magpie MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Magpie MCP or shows a Magpie MCP tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Magpie MCP yet

Magpie MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Magpie MCP

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Crypto & blockchain that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Magpie MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user magpie -- npx -y @magpieloans/magpie-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Magpie MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user magpie -- npx -y @magpieloans/magpie-mcp
  4. Type /mcp in Claude Code

    You should see Magpie MCP listed as connected

  5. Try it

    Use Magpie MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Magpie MCP or shows a Magpie MCP tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Magpie MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "magpie": { "command": "npx", "args": [ "-y", "@magpieloans/magpie-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Magpie MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Magpie MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Magpie MCP or shows a Magpie MCP tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Magpie MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "magpie": { "type": "stdio", "command": "npx", "args": [ "-y", "@magpieloans/magpie-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Magpie MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Magpie MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Magpie MCP or shows a Magpie MCP tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Magpie MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user magpie -- npx -y @magpieloans/magpie-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "magpie": {
      "command": "npx",
      "args": [
        "-y",
        "@magpieloans/magpie-mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "magpie": {
      "command": "npx",
      "args": [
        "-y",
        "@magpieloans/magpie-mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "magpie": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@magpieloans/magpie-mcp"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub starsi
7 (Stars for the whole repo)
This repo holds several MCP listings; its stars count once in rankings
Downloads per weeki
79/wk
Connection
Runs on your computer
Latest versioni
0.1.1
Published to registryi
Jun 24, 2026
Code last changedi
Sep 14, 2026
Maker
magpiecapital
Packages
npm: @magpieloans/magpie-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account magpiecapital, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @magpieloans/magpie-mcp@0.1.1

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/magpiecapital-magpie-mcp.svg)](https://mcp.popnx.com/en/servers/magpiecapital-magpie-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Crypto & blockchaini

  • More stars than 84% of the other 1759 servers in this category
  • Published to the registry more recently than 21% of the other 1759 servers in this category
  • Basic checks equal to or better than 99% of the other 1759 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Magpie MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.1.1) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: DexSQL, PayRam, DexPaprika, Alchemy MCP Server, X402 List MCP

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

DexSQL

SQL for Android APK and DEX files: classes, methods, strings, references and smali.

by LSPosedGrowing★ 320Updated 32 days ago

Runs on your computer✓ lsposed.org

PayRam

Install, configure, operate and integrate self-hosted PayRam crypto payment gateways.

by PayRamGrowing★ 158Updated 43 days ago

Runs in the cloud✓ service owner · payram.com

DexPaprika

DEX and on-chain data: liquidity pools, token prices, swaps, and trading volume.

by coinpaprikaGrowing★ 120Updated 6 days ago

Runs in the cloud✓ service owner · dexpaprika.com

X402 List MCP

Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.

by mcccsmEarly↓ 80/wk★ 18Updated 40 days ago

Computer or cloud✓ service owner · x402-list.com
Compared with similar ones
This one
Magpie MCP
DexSQLPayRamDexPaprikaAlchemy MCP ServerX402 List MCP
Runs whereInstalls on your computerInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/32/33/44/44/45/5
LicenseMITNOASSERTION–MITMITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

magpie-mcp

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.

MCP server exposing the Magpie Capital x402 API as native tools for Claude Desktop, Cursor, Windsurf, ChatGPT desktop, and any other MCP-aware agent host.

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.

Drop one config block into your host and your agent can query Magpie's protocol state, simulate borrows, fetch credit scores, build deposit/withdraw transactions, post conditional borrow intents, and arm self-owned in-vault take-profit / stop-loss exits on its own loans — all as first-class tool calls. No bespoke client code, no API keys.

A share of Magpie protocol fees accrues to a $MAGPIE holder-rewards pool, paid pro-rata in SOL (no staking, no lockup). 70% is the governance-ratified (MGP-001) target allocation; distributions run on a governance cadence. x402 call fees feed the same holder-rewards economics — agent adoption grows the fees that reward holders.

What it exposes

26 tools wrapping the x402 endpoints:

Free reads (work out of the box):

  • magpie_pool_state — live LendingPool account
  • magpie_protocol_pulse — 24h aggregates (active loans, volume, liquidations)
  • magpie_recent_activity — anonymized borrow/repay/liquidate stream
  • magpie_loan — single loan by ID
  • magpie_wallet_loans — all loans for a wallet
  • magpie_tiers — protocol tier constants
  • magpie_simulate_borrow — quote a loan without submitting
  • magpie_collateral_eligible — full collateral catalog
  • magpie_liquidatable — loans currently liquidatable
  • magpie_credit_leaderboard — top wallets by credit score
  • magpie_lp_state — depositor position + pool context
  • magpie_loan_by_pda — single loan by on-chain loan PDA
  • magpie_pools — Magpie lending pools (program-version lanes + context)
  • magpie_list_exits — armed in-vault exit orders for a wallet
  • magpie_modify_exit — change an armed exit's trigger / params
  • magpie_cancel_exit — cancel an armed exit (loan stays Active)

Paid (require a configured Solana keypair):

  • magpie_credit_score — 0.001 SOL
  • magpie_token_risk — 0.001 SOL (per-token risk profile)
  • magpie_build_borrow — 0.005 SOL (pass has_exit_arming: true to route into the V4 in-vault-exit lane)
  • magpie_build_repay — 0.002 SOL
  • magpie_build_deposit — 0.002 SOL
  • magpie_build_withdraw — 0.002 SOL
  • magpie_build_liquidate — 0.003 SOL (liquidate a past-due loan, receive keeper bounty)
  • magpie_create_intent — 0.01 SOL (conditional borrow)
  • magpie_get_intent — 0.0005 SOL (poll)
  • magpie_arm_exit — 0.001 SOL (arm a self-owned in-vault TP / SL / trailing exit)

When a paid tool fires, the server signs an x402 payment tx locally with your configured keypair and forwards the signature to magpie-x402. The keypair never leaves your machine.

Self-owned in-vault exits (V4)

Magpie's V4 lane lets an agent arm its own take-profit, stop-loss, and trailing exits on its own active loan — and the sell happens in-vault: when a trigger fires, the collateral is auto-sold and the proceeds (SOL by default, or USDC) accumulate inside that loan's per-loan proceeds vault while the loan stays Active. Proceeds only ever reach your wallet through your own borrower-signed repay. There's no fire-and-close, and nothing the protocol can do to move your funds out.

  • magpie_arm_exit (0.001 SOL) — arm a TP / SL / trailing exit on a V4 loan you own. Set direction (above = take-profit, the default; below = stop-loss) and exactly one trigger: target (e.g. "2x" / "0.7x"), price_usd, mc_usd (e.g. "5M", "1.2B"), or trailing_bps (stop-loss only). Optional slippage_bps, dest (sol | usdc), and slice for laddered exits.
  • magpie_modify_exit (free) — retune an armed order's trigger or params in place.
  • magpie_cancel_exit (free) — remove an armed order; the loan is untouched.
  • magpie_list_exits (free) — audit a wallet's armed orders, each with its distance-to-trigger.

Every exit call is authenticated with a dependency-free Ed25519 signed envelope built locally from your configured keypair. For magpie_arm_exit the envelope is signed by the same keypair that pays the 0.001 SOL x402 challenge, so the bot's payer == signer invariant holds and only the owner of a loan can arm exits on it. The bot enforces a 5-minute freshness window and nonce-uniqueness on every envelope.

To start a borrow that supports these exits, call magpie_build_borrow with has_exit_arming: true (routes into V4); leave it false for a plain memecoin (V1) borrow.

RWA / xStock collateral runs on the separate V3 lane, which is launch-gated — on the V3 launch, the same exit tooling will extend to RWA loans.

Install

Two paths. Both end at the same place.

Path A — npm (recommended once published)

No clone, no build, no absolute paths in your host config:

# Verify it runs once before wiring into your host:

npx -y @magpieloans/magpie-mcp --help

Then in your host config:

{

"mcpServers": { "magpie": { "command": "npx", "args": ["-y", "@magpieloans/magpie-mcp"], "env": { "SOLANA_RPC_URL": "https://api.mainnet-beta.solana.com", "MAGPIE_MCP_PAYER_KEYPAIR": "/path/to/payer-id.json" } } } }

Path B — from source

If the npm package isn't published yet, or you want to hack on the server:

git clone git@github.com:magpiecapital/magpie-x402.git

cd magpie-x402/mcp npm install npm run build

Built executable lands at mcp/dist/index.js. Use the absolute path in your host config below.

Configure your host

Pick the snippet for your host. The command + args shape changes between npm-install vs source-build; the env block is identical.

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{

"mcpServers": { "magpie": { "command": "node", "args": ["/ABS/PATH/TO/magpie-x402/mcp/dist/index.js"], "env": { "SOLANA_RPC_URL": "https://api.mainnet-beta.solana.com", "MAGPIE_MCP_PAYER_KEYPAIR": "/ABS/PATH/TO/payer-id.json" } } } }

Restart Claude Desktop. The Magpie tools appear in the tool picker.

Cursor

Edit ~/.cursor/mcp.json. Same shape as Claude Desktop above.

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json. Same shape.

ChatGPT desktop / any other MCP-aware host

Use the same shape — point the host at node /ABS/PATH/.../mcp/dist/index.js, pass env vars through the host's MCP config interface.

Free-only mode (no keypair)

Omit MAGPIE_MCP_PAYER_KEYPAIR and the read-only free tools still work. Paid tools — and the envelope-signed exit tools (magpie_arm_exit, magpie_modify_exit, magpie_cancel_exit, which need the keypair to sign the envelope even though modify/cancel cost nothing) — return a clear error explaining that no payer is configured. Useful for read-only research agents or as a no-friction first install.

Environment variables

VariableDefaultPurpose
MAGPIE_X402_BASE_URLhttps://x402.magpie.capitalOverride for self-hosted or testnet deployments
SOLANA_RPC_URLhttps://api.mainnet-beta.solana.comRPC used to send x402 payment txs. Public RPC rate-limits aggressively — use Helius/Triton/QuickNode for any real volume.
MAGPIE_MCP_PAYER_KEYPAIR_(unset)_Path to a Solana keypair JSON in the standard solana-keygen format. Enables paid tools.

Cost ceiling

The keypair you configure is the only place SOL can leave. Per-call costs are exact (the server doesn't ever pay more than the 402 challenge demands), but if you're paranoid about runaway tool-calls during agent experimentation, fund the payer wallet with a small float — say 0.05 SOL — and let it run dry rather than top it up unattended.

Security model

  • The MCP server reads but never modifies your keypair file. The keypair is loaded into memory once at startup; the signature for each paid call happens locally; only the resulting tx signature ever leaves your machine (sent to magpie-x402 in the X-Payment header).
  • The Magpie x402 service has no way to sign anything on your behalf. Even with a complete compromise of x402.magpie.capital, the worst case is that you pay for tool calls you didn't get useful results from. Your keypair is not exposed.
  • For high-stakes write paths (build-borrow, build-deposit, etc.) the server returns an *unsigned* tx. Your agent receives it as plain text; you decide whether to sign + submit it. The MCP server itself never signs anything besides x402 payment transfers.

Troubleshooting

Tool doesn't appear in host UI — restart the host after editing config. Most hosts only re-read the MCP config on launch.

402 error on a paid tool — MAGPIE_MCP_PAYER_KEYPAIR is unset or the file doesn't exist. Run solana-keygen new -o ~/.config/solana/magpie-mcp.json and point the env var at the result, then solana transfer … a small SOL float in.

`fetch failed` on x402.magpie.capital — check the URL is reachable from your machine. If you're behind a corporate proxy, set HTTPS_PROXY in the same env block.

RPC rate-limit during a paid call — switch SOLANA_RPC_URL to a paid Helius/Triton/QuickNode URL. The default api.mainnet-beta.solana.com will throttle under any sustained use.

For maintainers — publishing to npm

The package is set up for npm publish with no additional configuration. From mcp/:

# One-time per machine:

npm login --scope=@magpieloans

Each release:

1. Bump version in package.json (semver)

2. Publish — prepublishOnly rebuilds dist/ and chmod +x's the binary

npm publish

The package is scoped (@magpieloans/magpie-mcp) and publishConfig.access: "public" is set, so publish doesn't require any extra flags. The files field whitelists what ships — only dist/, README.md, LICENSE end up in the tarball (~9 KB).

Verify the contents before publish:

npm pack --dry-run

License

MIT.