Clicks Protocol vs Solana MCP by Vybe
A side-by-side look at the Clicks Protocol 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 Clicks Protocol for finance & fintech work as a local process; 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 Clicks Protocol when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CLICKS_PRIVATE_KEY. - You want tools like
get_protocol_stats, get_agent_info, get_yield_info.
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 | 52/100 · Good | 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 | CLICKS_PRIVATE_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 2,069 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 7 |
| Full listing | View Clicks Protocol | View Solana MCP by Vybe |
Tools & capabilities
Clicks Protocol tools 4
get_protocol_statsTVL, APY, agent countget_agent_infoCheck if an agent is registeredget_yield_infoYield balance for an agentsimulate_yieldProject earnings over time
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.
Clicks Protocol
{
"mcpServers": {
"mcp-server-108": {
"command": "npx",
"args": [
"-y",
"hardhat"
],
"env": {
"CLICKS_PRIVATE_KEY": "YOUR_CLICKS_PRIVATE_KEY_HERE"
}
}
}
}
Solana MCP by Vybe
{
"mcpServers": {
"solana-mcp-by-vybe": {
"url": "https://mcp.vybenetwork.xyz/mcp"
}
}
}
Frequently asked questions
Clicks Protocol is categorized under Finance & Fintech and uses a local stdio subprocess. Solana MCP by Vybe belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Clicks Protocol 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.
Clicks Protocol 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 mcp-server-108 and solana-mcp-by-vybe as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clicks Protocol has a quality signal of 52/100 (Good) with 1 views, 0 installs and 2 GitHub stars. Solana MCP by Vybe has 63/100 (Good) with 0 views, 0 installs and 2,069 GitHub stars.