Mpp32 Mcp Server

MPP32

The payment layer for AI agents

[npm version] [npm downloads] [License: MIT] [Website]

One install. Pay any x402 endpoint on Solana from your agent. Browse a federated index of thousands of machine payable APIs without setting up a single provider account.

What works today

The MCP server ships signers for Solana, Base, and Tempo out of the box. When a paid call returns a 402, the server picks the rail that matches the key you configured and settles the payment in one round trip. MPP32_SOLANA_PRIVATE_KEY pays x402 on Solana; MPP32_PRIVATE_KEY (0x-prefixed EVM key) pays x402 on Base and Tempo pathUSD challenges.

Free Tier: 10 calls/day, no wallet required

Every agent session gets 10 free Intelligence Oracle calls per day — no wallet, no USDC, no payment setup. Just set MPP32_AGENT_KEY (free, instant, no signup at mpp32.org/agent-console) and start calling get_solana_token_intelligence. Free tier resets at midnight UTC.

This lets you test your full MCP integration end-to-end before committing any crypto. Build working prototypes, evaluate the data quality, and ship to production — the free tier covers typical development and light usage indefinitely.

After free tier: $0.008/query paid via x402 (USDC on Solana). M32 holders save up to 40%.

Quick anonymous test (no keys at all)

The try_solana_token_intelligence_free tool returns the same payload with zero configuration — just install and call. Rate-limited to 10/minute per IP. Good for a quick taste, but the 10/day free tier with an agent key is better for real work.

Why this beats running your own integrations

Most agent stacks stop at "the model can call a function." That works until the function costs money. The moment your agent needs premium data, a paid model, a trading signal, or a token analytics call, you are back to building accounts, storing API keys, watching budgets, and writing custom 402 handlers for every provider.

MPP32 replaces all of that with one MCP server. Your agent asks for a service by name. The server finds it in a federated catalog of thousands of machine payable APIs, negotiates the cheapest protocol, signs payment from a key on your own machine, and returns the data. You write zero billing code. You manage zero provider accounts. Your agent gets faster, cheaper, and reaches services other agents cannot touch.

What your agent can do once this is installed

• Browse a live catalog of over 4,500 paid and free APIs across categories like token intelligence, market data, web search, image generation, embeddings, DeFi analytics, wallet scoring, on chain queries, and trading signals.
• Pay any provider in the catalog using whichever protocol fits, with settlement that lands in seconds.
• Run real time Solana token intelligence with alpha scoring, rug risk, whale flow, and 24 hour pump probability.
• Query live PIVX DAO governance data: active proposals, masternode voting tallies, budget allocation, and network deflation metrics — all free, no payment key needed.
• Track every call, every dollar settled, and every protocol used from a dashboard at mpp32.org.
• Get an automatic 20 percent or 40 percent discount on native services for holding M32 once your wallet is verified.
• Access M32-gated exclusive APIs: Whale Tracker (1M M32), Token Comparison (2.5M M32), and Portfolio Scanner (5M M32) — free for holders, unavailable to non-holders.

Install

npx -y mpp32-mcp-server@latest

Claude Desktop, Claude Code, Cursor, Windsurf

Drop this into the MCP servers section of your client config.

{  "mcpServers": {    "mpp32": {      "command": "npx",      "args": ["-y", "mpp32-mcp-server@latest"],      "env": {        "MPP32_AGENT_KEY": "mpp32_agent_…",        "MPP32_SOLANA_PRIVATE_KEY": "<your base58 Solana secret key>"      }    }  }}

Config file locations:

• Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
• Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
• Cursor: ~/.cursor/mcp.json
• Windsurf: ~/.codeium/windsurf/mcp_config.json

Fully quit and reopen the client after editing. The MCP child process inherits env vars from this file at launch.

Get an MPP32_AGENT_KEY at mpp32.org/agent-console. No signup, no email, just click Create Agent Session and the form returns a key plus this exact config snippet ready to copy. With an agent key every call is attributed to your dashboard so you can see spend, success rate, and protocol breakdown. Without it the server still works but you only see native services and the calls stay anonymous.

MPP32_SOLANA_PRIVATE_KEY is only needed for paid services. Free services in the catalog work without any payment key.

What format does MPP32_SOLANA_PRIVATE_KEY take?

A base58 encoded 64 byte Solana secret key. The same string that Phantom shows under export private key (not the seed phrase). If you have a keypair.json (the 64 byte array Solana CLI uses), convert it once with:

node -e "console.log(require('bs58').encode(Buffer.from(JSON.parse(require('fs').readFileSync('keypair.json')))))"

Then paste the resulting string into the env block. Treat it like a password. It can spend any USDC and SOL in the wallet.

Fund the wallet with both USDC and SOL

x402 settles the payment in USDC, but Solana itself charges a tiny native SOL fee on every transaction. A USDC only wallet will fail with insufficient funds for rent even though the USDC balance is plentiful. About 0.001 SOL covers many calls.

Tip: call the get_mpp32_diagnostics tool from inside Claude. It probes the API, reports which env vars actually reached the MCP process, and prints Ready to pay: YES once everything is wired.

Configuration

Private keys stay on your machine. They sign payments locally and never travel to MPP32 servers. Provide either or both for paid calls. If both are present and a challenge advertises both networks, EVM is preferred unless MPP32_PREFERRED_NETWORK is set; if only one key is configured, that network wins automatically.

Tools your agent will see

list_mpp32_services

Browse the federated catalog. Returns native, curated free, x402 bazaar, and MCP registry entries with pricing, supported protocols, and a clear flag on every row that tells the agent whether it can actually call the service through this MCP or whether the entry is for discovery only.

{ "category": "token-scanner", "q": "solana", "source": "native" }

call_mpp32_endpoint

Call any HTTP callable service in the catalog. Free services return immediately. Paid services return a 402 challenge that this tool signs and retries automatically when a payment key is configured.

{  "slug": "mpp32-intelligence",  "method": "POST",  "body": { "token": "SOL" }}

Under the hood:

1. Send the request to /api/agent/execute.
2. If the service is free, hand the response back.
3. If the service is paid, read the 402 challenge.
4. Pick the protocol your wallet can satisfy.
5. Sign the transaction locally.
6. Retry with the receipt attached.
7. Return the data with the settled amount, the protocol used, and the on chain settlement signature.

No payment logic in your code. No per provider keys to juggle.

get_mpp32_diagnostics

Reports the MCP server version, which env vars actually reached the child process, the API URL it will hit, and a live API reachability probe. Prints Ready to pay: YES only when an agent key plus at least one signing key are detected and the API is reachable. Call this first if anything misbehaves. Also available as debug_mpp32.

get_solana_token_intelligence

Real time analysis of any Solana token. Pulls live data from DexScreener, Jupiter, and CoinGecko and merges it into one report. Returns an alpha score from 0 to 100, rug risk, whale activity, smart money signals, 24 hour pump probability, projected ROI ranges, and full market data. Costs $0.008 per call, paid automatically through x402 when a Solana key is set.

{ "token": "BONK" }

M32 holders get tiered discounts (20 percent at 250k, 40 percent at 1M) once SIWS wallet signature verification ships. The discount path is gated off in production until then so it cannot be claimed by spoofing a wallet header. M32 holders also get exclusive access to three token-gated APIs: Whale Tracker (1M M32), Token Comparison (2.5M M32), and Portfolio Scanner (5M M32) — these are live now and require passing your wallet address via the X-Wallet-Address header.

get_m32_whale_tracker

M32-gated whale analysis for any Solana token. Returns top 20 holders, concentration risk, holder distribution, and buy/sell pressure. Requires the caller to hold 1,000,000+ M32 tokens (balance verified on-chain). Free for qualifying holders.

{ "token": "<mint-address>", "walletAddress": "<your-solana-wallet>" }

compare_tokens_m32

M32-gated head-to-head intelligence comparison of two Solana tokens. Returns side-by-side alpha scores, rug risk, whale activity, volume, liquidity, and a winner verdict. Requires 2,500,000+ M32 tokens.

{ "tokenA": "<mint-A>", "tokenB": "<mint-B>", "walletAddress": "<your-solana-wallet>" }

scan_portfolio_m32

M32-gated full wallet portfolio scan. Discovers all SPL tokens in a wallet, runs intelligence on top holdings, and returns per-token analysis with aggregate risk metrics. Requires 5,000,000+ M32 tokens.

{ "wallet": "<wallet-to-scan>", "walletAddress": "<your-solana-wallet>" }

get_pivx_dao_intelligence

Real-time PIVX DAO governance intelligence. Returns active budget proposals with masternode voting tallies, budget allocation status, network deflation metrics, and masternode network health. PIVX is a fully community-governed cryptocurrency where Masternode owners vote on budget proposals every ~30 days. Data sourced live from pivx.org/proposals and the PIVX blockchain. Free — no payment key required.

{ "filter": "all" }

{ "filter": "passing", "includeStats": true }

Two parameters:

• filter (optional) — all (default), passing, or failing. Filters proposals by voting status.
• includeStats (optional, default true) — include network overview and deflation metrics alongside proposals.

The response includes a network overview (masternode count, passing threshold, monthly budget in PIV and USD, budget allocation percentage, block height, supply stats), deflation metrics (unallocated treasury PIV that are never minted, effective inflation reduction, proposal fee burn), and all active proposals with vote counts, payment amounts, installments, and links.

View the governance dashboard at mpp32.org/governance.

manage_agent_budget

View, set, or reset the economic circuit breaker for your agent session. Prevents runaway spending with infrastructure-level budget enforcement.

{ "action": "get" }

{ "action": "set", "budgetLimitUsd": 10.0, "velocityLimitUsd": 1.0, "alertThresholdPercent": 80 }

{ "action": "reset" }

Three actions:

• get returns current budget status: remaining balance, hourly velocity, circuit breaker state, and per-service spending breakdown.
• set configures budgetLimitUsd (max total session spend), velocityLimitUsd (max spend per hour), and alertThresholdPercent (warn at this percentage of budget used). All three are optional and can be set independently.
• reset clears a tripped circuit breaker so the session can resume spending. Circuit breakers trip automatically when limits are exceeded and stay tripped until manually reset.

Budget limits can also be set at session creation time via the agent console at mpp32.org/agent-console or by passing budgetLimitUsd, velocityLimitUsd, and alertThresholdPercent to POST /api/agent/sessions.

How discovery works

MPP32 keeps a federated index of machine payable services so your agent can find what is out there without crawling every provider on its own. Four sources feed it.

Every row in list_mpp32_services carries a callable flag so it stays obvious which slugs can be passed to call_mpp32_endpoint.

Sessions for autonomous agents

For longer running workflows, MPP32 issues server side session keys with a 30 day expiry and full per call accounting. Sessions let an agent run inside a budget instead of negotiating payment every single call.

1. Create a session at mpp32.org/agent-console or by posting to /api/agent/sessions.
2. Get a key in the form mpp32_agent_*.
3. Put it in MPP32_AGENT_KEY in your MCP config, or send it as X-Agent-Key on direct API calls.
4. Watch spend, latency, and protocol mix live in the dashboard.

Sessions are scoped, revocable, and rotate cleanly. The key is hashed at rest on the server, so a database leak does not surrender live credentials.

How payment verification actually works

x402 payments are verified on chain through the Solana facilitator (for SVM) or the Base facilitator (for EVM). MPP32 never holds custody of funds. Every paid call settles directly from the caller's wallet to the provider's wallet.

Tempo payments are verified on chain by the proxy's mppx integration: the client signs a TIP-20 pathUSD transfer against the live challenge and the server confirms the transfer on Tempo mainnet before releasing the response. AP2 and AGTP run as live authorization and identity layers on every paid route. The ACP envelope is implemented and tested against synthetic challenges but stays disabled in production until its checkout-session client flow is verified end to end.

For API providers

List your endpoint once and receive payment over x402. MPP32 handles the payment negotiation, the on chain verification, the discovery listings via OpenAPI and A2A and MCP standards, the periodic health re check, and the analytics dashboard. Settlement lands in USDC on Solana or Base straight to your wallet.

Register at mpp32.org/build.

Links

License

MIT