PayRam vs Solana MCP by Vybe
A side-by-side look at the PayRam and Solana MCP by Vybe MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PayRam for finance & fintech work over a hosted endpoint; choose Solana MCP by Vybe 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 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.
Choose Solana MCP by Vybe when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list-endpoints, get-endpoint, search-endpoints.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 63/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 158 | 2,069 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 44 | 7 |
| Full listing | View PayRam | View Solana MCP by Vybe |
Tools & capabilities
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
Solana MCP by Vybe tools 7
list-endpointsLists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.get-endpointGets detailed information about a specific API endpoint, including security schemes and serverssearch-endpointsPerforms a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.query-vybe-apiRuns a read-only GET request against a documented /v4 path on the Vybe Solana API (see https://docs.vybenetwork.com) and returns live Solana data: token prices, holders, liquidity and candles; wallet balances, PnL, counterparties and DeFi positions; markets, trades, transfers, top traders and labeled accounts. Use list-endpoints or search-endpoints to find a path and get-endpoint to check its parameters first. This tool cannot create, modify, or delete anything.query-vybe-api-batchReads Solana wallet data for many addresses in one call from the Vybe Solana API (see https://docs.vybenetwork.com). These endpoints use a POST body only to carry the list of wallet addresses; they do not create, modify, or delete any data. Use query-vybe-api for single-wallet and all other reads.build-vybe-transactionBuilds an unsigned Solana transaction with the Vybe Solana API (see https://docs.vybenetwork.com) for a token swap, a token-account close, or an MEV withdrawal, and returns it as base64 for the user to review and sign in their own wallet. This tool never signs, submits, or broadcasts a transaction, never moves funds on its own, and never accepts private keys. Use query-vybe-api with /v4/trading/swap-quote first when the user only wants a price quote.pay-with-x402Before calling any Vybe endpoint without an API key (e.g. AI agent, throwaway script, premium-only path), use this to access the same endpoint via x402 pay-per-call USDC on Solana.
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.
PayRam
{
"mcpServers": {
"payram": {
"url": "https://mcp.payram.com/mcp"
}
}
}
Solana MCP by Vybe
{
"mcpServers": {
"solana-mcp-by-vybe": {
"url": "https://mcp.vybenetwork.xyz/mcp"
}
}
}
Frequently asked questions
PayRam is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Solana MCP by Vybe belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick PayRam for finance & fintech work and Solana MCP by Vybe 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.
PayRam has no declared pricing — check the project's own site. Solana MCP by Vybe 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 payram and solana-mcp-by-vybe as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PayRam has a quality signal of 63/100 (Good) with 0 views, 0 installs and 158 GitHub stars. Solana MCP by Vybe has 63/100 (Good) with 0 views, 0 installs and 2,069 GitHub stars.