Skip to content
Data
MCP

solana-mcp-vybe

Ships with solana-mcp-vybe: Solana MCP by Vybe is a developer toolkit for live Solana data: wallets, trades, markets, transfers, and signable swaps. The public server publishes 44 tools. Each tool calls one…

From plugin
solana-mcp-vybe
2.2k3 skills1 command1 MCP

Claude Code

$ claude mcp add --transport http solana-mcp-vybe https://mcp.vybenetwork.xyz/mcp

Security report

Info

Not enough data

  • Known flaws

    Not published

  • Signed build

    Not published

  • Maintained

    Oct 27, 2026

    Last push

  • Licence

    Not published

  • Runs as

    Remote

    mcp.vybenetwork.xyz

  • Deprecated

    Not published

Signals from public registries, not an audit. Checked Nov 11, 2026.

solana-mcp-vybe README

Solana MCP by Vybe

Solana MCP by Vybe is a developer toolkit for live Solana data: wallets, trades, markets, transfers, and signable swaps. The public server publishes 44 tools. Each tool calls one Vybe API endpoint.

build-swap, build-close-token-accounts, and build-withdraw-mev return an unsigned transaction to sign in your own wallet. The server does not take private keys, and it does not broadcast transactions. get-x402-access-guide returns x402 pay-per-call instructions and does not send a payment.

This repo is the directory listing, Claude plugin, and MCP registry metadata. The running server is vybenetwork/vybe-mcp-oauth-proxy. Its current version is 1.3.2.

Versions

PieceVersionWhere
Live MCP server1.3.2initialize on https://mcp.vybenetwork.xyz/mcp
Claude plugin1.3.0.claude-plugin/plugin.json
MCP registry metadata1.1.3server.json

MCP endpoint

Use the streamable HTTP endpoint:

https://mcp.vybenetwork.xyz/mcp

Registry metadata (server.json) publishes the remote as:

https://mcp.vybenetwork.xyz

Clients that require an explicit MCP path (ChatGPT Developer Mode, Codex, Cursor HTTP) should use https://mcp.vybenetwork.xyz/mcp.

The public guide at docs.vybenetwork.com/docs/mcp still describes the old tools list-endpoints, search-endpoints, get-endpoint, and execute-request. Those names are not in the published tool list.

Quick setup

Cursor / Windsurf / Codex-style HTTP

{
  "mcpServers": {
    "solana-mcp-vybe": {
      "type": "http",
      "url": "https://mcp.vybenetwork.xyz/mcp"
    }
  }
}

Same snippet: .mcp.json.

Claude Desktop via mcp-remote

{
  "mcpServers": {
    "solana-mcp-vybe": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.vybenetwork.xyz/mcp"]
    }
  }
}

Claude.ai custom connector or Connectors Directory

Name: Solana MCP by Vybe
URL:  https://mcp.vybenetwork.xyz/mcp

Claude Code / Cowork plugin

This repo is a Claude plugin (/.claude-plugin/plugin.json). Validate, then submit the public GitHub URL:

claude plugin validate .

Sign in with OAuth when the client asks. Use your Vybe email as the username and your API key as the password, then approve consent. Do not commit API keys or private keys into this repo.

Claude directory links from .claude-plugin/plugin.json:

Classification on that manifest: acts on apis, finances, code, and databases, department engineering, industry software-saas, subject computing. claude plugin validate on Claude Code 2.1.138 reports the directory-only fields (displayName, icon, links, classification) as unrecognized. The plugin directory accepts them.

What this repository holds

  • server.json — metadata published to the official MCP Registry (GitHub Actions). Remote URL: https://mcp.vybenetwork.xyz.
  • .mcp.json — MCP server URL for the Claude and Codex plugins. Native HTTP to https://mcp.vybenetwork.xyz/mcp. No secrets.
  • .codex-plugin/plugin.json — Codex plugin metadata for local install against the same MCP URL.
  • .claude-plugin/plugin.json — Claude Code / Cowork plugin manifest (skills, commands, remote MCP, directory links, and classification).
  • skills/ — vybe-api-explorer, vybe-token-market-intel, and vybe-wallet-analytics.
  • commands/connect-vybe.md — Claude command for the OAuth sign-in steps.

Available tools

Published tools/list has these 44 tools. Pass each tool's own arguments. Do not pass a URL, path, or HTTP method.

ToolCalls
list-pyth-price-feedsGET /v4/oracle/pyth/pricefeeds
get-pyth-price-candlesGET /v4/oracle/pyth/pricefeeds/{priceFeedAddress}/candles
get-pyth-priceGET /v4/oracle/pyth/pricefeeds/{priceFeedAddress}/price
get-marketGET /v4/markets/{marketAddress}
list-marketsGET /v4/markets
get-market-candlesGET /v4/markets/{marketAddress}/candles
get-pyth-price-historyGET /v4/oracle/pyth/pricefeeds/{priceFeedAddress}/price-ts
get-pyth-productGET /v4/oracle/pyth/products/{productAddress}
get-token-candlesGET /v4/tokens/{mintAddress}/candles
list-tokensGET /v4/tokens
list-labeled-programsGET /v4/programs/labeled-program-accounts
list-supported-dexesGET /v4/reference/dexes
get-token-liquidityGET /v4/tokens/{mintAddress}/liquidity
get-tokenGET /v4/tokens/{mintAddress}
get-token-holder-count-historyGET /v4/tokens/{mintAddress}/holders-count-ts. Requires startTime and endTime as unix seconds, at most 2592000 seconds (30 days) apart. interval is hour or day.
list-instruction-namesGET /v4/reference/instruction-names
get-token-trader-activityGET /v4/tokens/{mintAddress}/trader-activity
get-token-top-pnl-tradersGET /v4/tokens/{mintAddress}/top-pnl-traders
get-token-top-holdersGET /v4/tokens/{mintAddress}/top-holders
list-transfersGET /v4/transfers
get-swap-quoteGET /v4/trading/swap-quote
get-token-trade-volume-historyGET /v4/tokens/{mintAddress}/trade-volume-ts
build-swapPOST /v4/trading/swap
list-tradesGET /v4/trades
get-empty-accounts-batchPOST /v4/wallets/batch/empty-accounts
get-dust-accounts-batchPOST /v4/wallets/batch/dust-accounts
get-token-balance-history-batchPOST /v4/wallets/batch/token-balances-ts
get-token-balances-batchPOST /v4/wallets/batch/token-balances
list-top-tradersGET /v4/wallets/top-traders
get-wallet-counterpartiesGET /v4/wallets/{ownerAddress}/counterparties
list-labeled-accountsGET /v4/wallets/labeled-accounts
get-token-accounts-batchPOST /v4/wallets/batch/token-accounts-balance-ts
get-wallet-defi-positionsGET /v4/wallets/{ownerAddress}/defi-positions
get-wallet-empty-accountsGET /v4/wallets/{ownerAddress}/empty-accounts
get-wallet-dust-accountsGET /v4/wallets/{ownerAddress}/dust-accounts
get-wallet-token-account-historyGET /v4/wallets/{ownerAddress}/token-accounts-balance-ts
get-wallet-token-balancesGET /v4/wallets/{ownerAddress}/token-balance
get-wallet-pnlGET /v4/wallets/{ownerAddress}/pnl
get-wallet-pnl-historyGET /v4/wallets/{ownerAddress}/pnl-ts
get-wallet-token-balance-historyGET /v4/wallets/{ownerAddress}/token-balance-ts
build-close-token-accountsPOST /v4/wallets/util/close-token-accounts
get-wallet-transfer-volumeGET /v4/wallets/{ownerAddress}/transfer-volume-usd
build-withdraw-mevPOST /v4/wallets/util/withdraw-mev
get-x402-access-guideStatic x402 pay-per-call guidance. Does not send a payment.

build-swap, build-close-token-accounts, and build-withdraw-mev return an unsigned transaction. They do not sign or broadcast it. The five *-batch tools POST a list of wallet addresses and only read data.

GitHub repository name

vybenetwork/solana-mcp-vybe (starts with solana-mcp, includes Vybe).

Publish a new listing version

  1. Clone or use this repo at github.com/vybenetwork/solana-mcp-vybe

  2. Tag and push (the workflow sets server.json version from the tag):

    git tag vX.Y.Z
    git push origin vX.Y.Z
    

    server.json is currently 1.1.3. The next registry tag should be newer than that. A tag push rewrites server.json version from the tag during the workflow.

    Or run Actions → Publish to MCP Registry → Run workflow (uses the version already in server.json).

Publishing uses GitHub OIDC in Actions; no personal token secret is required.

If you use mcp-publisher login github locally and get 403 for io.github.vybenetwork/...: Git apps like Git Credential Manager are unrelated. Open GitHub → Settings → Applications → Authorized OAuth Apps, choose the app you authorized during mcp-publisher login github (device flow), then under Organization access click Grant for vybenetwork. On SAML-enforced orgs, also complete SSO for that OAuth app. Then run mcp-publisher logout, mcp-publisher login github, and publish again.

  1. Verify:

    curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=vybenetwork" | jq .
    

Cursor and other directories

Use .mcp.json as the install snippet. For Cursor Directory, submit after the registry publish succeeds; use OAuth for https://mcp.vybenetwork.xyz/mcp.

Registry catalog id

server.json name: io.github.vybenetwork/solana-mcp-vybe. Display title: Solana MCP by Vybe.

Publish: push main, then git tag vX.Y.Z && git push origin vX.Y.Z, or Actions → Publish to MCP Registry.

@vybenetwork
Ships withsolana-mcp-vybe
2.2k3 skills1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
2.2k
Star history of vybenetwork/solana-mcp-vybe on GitHub, a chart by star-history.com

More MCP servers from other plugins.

mem0
Auto-invoked

mem0

MCP

Stores and retrieves long term memories for AI agents to personalize their responses.

mem05d69k
@mem0ai@mem0aiInstall MCP
phrocs

phrocs

MCP

Ships with posthog: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI…

posthog11d41k
@posthog@posthogInstall MCP
agentmemory
Auto-invoked

agentmemory

MCP

Ships with agentmemory: #1 Persistent memory for AI coding agents based on real-world benchmarks

@rohitg00@rohitg00Install MCP
skill-seekers

skill-seekers

MCP

Ships with skill-seekers: 🧠 The data layer for AI systems. Skill Seekers turns documentation sites, GitHub repos, PDFs, videos,…

Questions about solana-mcp-vybe.

Which coding agents can use solana-mcp-vybe?
solana-mcp-vybe works in any agent that reads an MCP config file: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf. Each agent reads it from its own file; this page names the file for each one.
How do I add solana-mcp-vybe to Claude Code?
Run this in your terminal: claude mcp add --transport http solana-mcp-vybe https://mcp.vybenetwork.xyz/mcp