Sperax Crypto MCP Server

A MCP server for SperaxOS that supports Arbitrum One with USDs, SPA, Demeter, and other popular EVM-compatible networks. Exposed over MCP by the sperax crypto mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

• ✅ No claiming — Yield appears in your wallet automatically
• ✅ No staking — Just hold USDs in any wallet
• ✅ Composable — Use USDs in DeFi while earning yield
• ✅ Fully backed — 100%+ collateralized by stablecoins
• ✅ Transparent — All operations visible on-chain

Its toolset

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

• usds_get_info — Get USDs overview including supply, APR, and last rebase time
• usds_get_balance — Get USDs balance and rebase state for any address
• usds_get_rebase_state — Check if an address receives yield rebases
• usds_get_mint_params — Get current mint fees and parameters
• usds_get_yield_info — Get current yield metrics, APR, and distribution
• usds_get_collateral_ratio — Get protocol collateralization ratio
• usds_estimate_mint — Simulate minting USDs with specific collateral
• vault_get_status — Get Vault TVL, health status, utilization, and fees
• vault_get_collaterals — List all supported collaterals with current allocations
• vault_get_collateral_details — Get detailed info for specific collateral (USDC, USDT, DAI, FRAX)
• vault_get_strategies — List all active yield strategies and their performance
• vault_get_strategy_details — Get specific strategy allocation and APY

Configuration

You will need 2 environment variables: ARBITRUM_RPC_URL, CUSTOM_RPC_URL. 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+ - pnpm (recommended) or npm

Adding it to your client

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Sperax Crypto MCP's toolset — usds_get_info, usds_get_balance, usds_get_rebase_state and 11 more — is a fair guide to whether it matches your workflow. It is maintained by nirholas; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Sperax 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 sperax crypto mcp mcp server does with a few real requests.