Mpp32 MCP Server vs PayRam
A side-by-side look at the Mpp32 MCP Server and PayRam MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mpp32 MCP Server for finance & fintech work as a local process; choose PayRam for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mpp32 MCP Server when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MPP32_AGENT_KEY, MPP32_SOLANA_PRIVATE_KEY, MPP32_PRIVATE_KEY. - You want tools like
get_mpp32_diagnostics, debug_mpp32, list_mpp32_services.
Choose PayRam when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
payram_setup_plan, payram_doctor, payram_troubleshoot.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 65/100 · Great | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | MPP32_AGENT_KEYMPP32_SOLANA_PRIVATE_KEYMPP32_PRIVATE_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 221 | 158 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | 44 |
| Full listing | View Mpp32 MCP Server | View PayRam |
Tools & capabilities
Mpp32 MCP Server tools 16
get_mpp32_diagnosticsReport what the mpp32-mcp-server detected at startup: version, API URL, env vars (MPP32_AGENT_KEY, MPP32_SOLANA_PRIVATE_KEY, MPP32_PRIVATE_KEY, MPP32_PREFERRED_NETWORK), and a live API connectivity check. Use this FIRST if payments fail with 'no key configured' even though you set one in claude_desktop_config.json.debug_mpp32Alias for get_mpp32_diagnostics. Reports env-var detection, API connectivity, and ready-to-pay status.list_mpp32_servicesBrowse the MPP32 federated catalog of 4,500+ machine-payable APIs and data services. Includes native MPP32 services (callable end-to-end through this MCP), x402 Bazaar services (pay-per-call in USDC, mostly on Base, some on Solana — callable when they expose an HTTPS endpoint), curated free APIs (DexScreener, Jupiter, CoinGecko health, httpbin, etc.), and the public MCP Registry (npx-installable servers; listing-only). Each result indicates whether it is callable through `call_mpp32_endpoint` or listing-only. The catalog is large (~4,500 entries) — by default a single call returns up to 100 results and the response will tell you the true total and whether the page was truncated. Use `q` (free-text search), `category`, `source`, or `protocol` to narrow down, or raise `limit` (max 500) for broader pages.find_mpp32_serviceDescribe what you need in plain language instead of browsing the 4,500+ entry catalog yourself. Returns a ranked shortlist — ranked by keyword relevance, catalog health status (broken listings are excluded automatically), verification, and whether the price actually fits your stated budget. Use this before `list_mpp32_services` when you have a task in mind ('check if this wallet is a rug', 'generate a product image', 'get real-time SOL price') rather than a category to browse. The top result's slug is ready to pass straight to `call_mpp32_endpoint`.call_mpp32_endpointCall any HTTP-callable service in the MPP32 federated catalog. Free services return immediately. Paid services return a 402 challenge that this tool will sign and retry automatically when a payment key is configured: MPP32_SOLANA_PRIVATE_KEY pays x402 USDC on Solana; MPP32_PRIVATE_KEY (one EVM key) pays x402 USDC on Base and Tempo pathUSD. The result is checked after payment — a rejected payment is reported, never shown as success. Set MPP32_AGENT_KEY for dashboard tracking. Use `list_mpp32_services` first to find a slug. Many catalog entries store only the upstream BASE URL (e.g. `https://api.exa.ai`) — pass the upstream path (e.g. `/search`) via the `path` argument when calling those. Listing-only entries (npx-installable MCP servers, etc.) cannot be called through this tool.get_solana_token_intelligenceGet real-time Solana token intelligence from the MPP32 Intelligence Oracle. Returns alpha score (0-100), rug risk assessment, whale activity, smart money signals, 24h pump probability, projected ROI ranges, and aggregated DexScreener/Jupiter/CoinGecko market data. **FREE TIER: Every agent session gets 10 free calls per day — no wallet, no USDC, no payment setup required.** Just set MPP32_AGENT_KEY. After free tier: $0.008/query, paid automatically in USDC via x402 on Solana (MPP32_SOLANA_PRIVATE_KEY) or Base (MPP32_PRIVATE_KEY), or pathUSD via Tempo (MPP32_PRIVATE_KEY). M32 token holders receive up to 40% discount.try_solana_token_intelligence_freeFREE preview of the MPP32 Intelligence Oracle — quick anonymous test, no keys required. Rate-limited to 10 calls/minute per IP. Returns the same payload as the paid endpoint. **Better option: get an MPP32_AGENT_KEY from mpp32.org/agent-console and call `get_solana_token_intelligence` instead — you get 10 FREE attributed calls per day, plus dashboard tracking, before any payment is needed.**get_m32_whale_trackerM32-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 via X-Wallet-Address header). Free for qualifying holders — no payment required. Returns 403 if the wallet holds insufficient M32.compare_tokens_m32M32-gated head-to-head intelligence comparison of two Solana tokens. Returns side-by-side alpha scores, rug risk, whale activity, volume, liquidity, market data, and a winner verdict. Requires the caller to hold 2,500,000+ M32 tokens (balance verified on-chain via X-Wallet-Address header). Free for qualifying holders. Returns 403 if insufficient M32.scan_portfolio_m32M32-gated full wallet portfolio scan. Discovers all SPL tokens in a Solana wallet, runs intelligence on top holdings, and returns per-token analysis with aggregate portfolio risk metrics. Requires the caller to hold 5,000,000+ M32 tokens (balance verified on-chain via X-Wallet-Address header). Free for qualifying holders. Returns 403 if insufficient M32.get_pivx_dao_intelligenceGet real-time PIVX DAO governance intelligence. Returns active budget proposals with masternode voting tallies (Yes/No counts, net yes percentages), budget allocation status, network deflation metrics (unallocated treasury PIV that are never minted), and masternode network health. PIVX is a fully community-governed cryptocurrency where Masternode owners vote on budget proposals every ~30 days (43,200 blocks per superblock cycle, 432,000 PIV max monthly budget). Data is served by the MPP32 backend, which aggregates pivx.org/proposals and the PIVX blockchain via Chainz CryptoID, and caches for 5 minutes. Free — no payment or API key required.manage_agent_budgetView and control the spending limits of your MPP32 agent session. 'get' = current budget status (remaining budget, hourly velocity, paused / circuit-breaker state). 'set' = configure limits (budget cap in USD, hourly velocity limit, alert threshold). 'pause' = immediately stop all paid calls (safe to use any time). 'resume' = lift a pause, and 'reset' = clear a tripped circuit breaker — ONLY use 'resume' or 'reset' when the human operator explicitly asks you to; never on your own to get past a limit, because the breaker exists to stop runaway agent spending.- +4 more on the listing page
PayRam tools 44
payram_setup_planStart here to install PayRam on a VPS. Returns an ordered, personalised plan — prepare server → install → claim admin + set public URL → wallets (incl. Smart Bridge review) → API key + first payment link → hardening → store/app integration — with who runs each step (agent shell vs human/dashboard), exact commands, what success looks like, and hard stops that need the human (cold wallet, mainnet spend, root-only settings). Ask the user first whether you can run commands on their server (access "ssh") or only chat with them (access "human_runs_commands": they run each command and paste the output back). Pass stage to resume mid-way; payram_doctor tells you the stage of a running server.payram_doctorRead-only diagnosis of a PayRam server by its public URL — works from the hosted MCP without credentials: reachability, health, TLS certificate, installed vs latest version, worker states. Optionally validates an API key without creating anything. Returns ranked likely causes and exact fixes for the first failing stage. Run this first when anything PayRam-related fails.payram_troubleshootSomething is not working? Describe the problem in plain words and/or paste the error or log text. Returns the known PayRam problems it matches, what each usually means, how to confirm it and the fix, plus which tool to use next. Needs no credentials and no access to the server; what you paste is not stored. Call with nothing to list known problems. For a live check of a running server use payram_doctor.payram_runbookStep-by-step procedures for changes to a running PayRam, each step marked agent vs human with hard stops: set_site_url, change_domain, ssl_setup, ssl_renewal_fix, firewall_ports, upgrade, backup, restore, add_chain, smart_bridge, mainnet_cutover, operator_setup, rotate_api_key, reset_test_install, shopify_connector, woocommerce_plugin, secure_analytics_mcp, install_failed, custom_port_or_proxy, external_database, forgot_root_password. Omit task to list them.payram_ops_playbookExact, copy-paste recipes for day-2 operations and troubleshooting that YOU run against the merchant's PayRam API with credentials that stay on your machine: which endpoint, which credential (public / dashboard JWT / project API key), a curl+jq command, how to read the answer, and what not to do. Start with "connect". Tasks: connect, health, version_check, workers, restart_worker, node_sync, site_url, payment_options, unswept_funds, payments_today, payment_lookup, stuck_payment, create_payment_link, payouts, webhooks, logs, daily_check. Omit task to list them.generate_env_templateCreates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.generate_setup_checklistReturns a step-by-step checklist of everything a merchant must configure to start using Payram.suggest_file_structureSuggests a recommended backend folder/file structure for integrating Payram.get_agent_setup_flowReturns the canonical PayRam headless-agent guide: agent CLI commands, env vars, merchant vs operator mode, wallet flows, adding chains, troubleshooting. Long (~11k tokens). For a short personalised plan use payram_setup_plan.generate_payment_sdk_snippetGenerates backend code using the official Payram JS/TS SDK to create a payment.generate_payment_http_snippetGenerates a raw HTTP sample for creating a Payram payment in the requested language.generate_payment_status_snippetGenerates backend code to query the status of a Payram payment.- +32 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Mpp32 MCP Server
{
"mcpServers": {
"mpp32-mcp-server": {
"command": "npx",
"args": [
"-y",
"mpp32-mcp-server@latest"
],
"env": {
"MPP32_AGENT_KEY": "YOUR_MPP32_AGENT_KEY_HERE",
"MPP32_SOLANA_PRIVATE_KEY": "YOUR_MPP32_SOLANA_PRIVATE_KEY_HERE",
"MPP32_PRIVATE_KEY": "YOUR_MPP32_PRIVATE_KEY_HERE"
}
}
}
}
PayRam
{
"mcpServers": {
"payram": {
"url": "https://mcp.payram.com/mcp"
}
}
}
Frequently asked questions
Mpp32 MCP Server is categorized under Finance & Fintech and uses a local stdio subprocess. PayRam belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Mpp32 MCP Server for finance & fintech work and PayRam for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mpp32 MCP Server has no declared pricing — check the project's own site. PayRam has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mpp32-mcp-server and payram as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mpp32 MCP Server has a quality signal of 65/100 (Great) with 1 views, 0 installs and 221 GitHub stars. PayRam has 63/100 (Good) with 1 views, 0 installs and 158 GitHub stars.