Solana MCP by Vybe

io.github.vybenetworkPublished by GitHub account vybenetworkv1.0.9Updated Nov 2, 2026

Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools.

VerifiedStreamable HTTPWeb executableDatabasesFinanceDeveloper Tools

Overview

AI-generated overview

Remote Vybe server that gives an assistant live Solana data: wallets, tokens, markets, trades, PnL, transfers and unsigned swap transactions.

What you can do
  • Look up tokens, markets and Pyth price feeds, including candles, prices, liquidity, holders and trade volume
  • Inspect wallets: token balances, balance history, PnL and PnL history, DeFi positions, counterparties, dust and empty accounts, transfer volume
  • Query trades and transfers, top traders, labeled accounts and programs, DEXes and instruction names
  • Build unsigned transactions for swaps, closing token accounts and withdrawing MEV, plus get swap quotes
  • Read x402 pay-per-call guidance for using endpoints without an API key
When to use it
Useful when you want an assistant to research Solana tokens, wallets or markets, or to prepare swap and wallet-cleanup transactions for you to sign yourself. It suits on-chain analysis and trading workflows that need live Vybe data rather than a local index.
Requirements
A remote streamable HTTP endpoint; no local package. An API key is required, sent in the X-API-KEY header (or OAuth sign-in with your Vybe email and API key as password). Network access to the Vybe service.
Before you install
The API key is a credential: keep it out of repositories and shared configs. The build tools return unsigned transactions that you must review and sign in your own wallet; the server does not hold private keys or broadcast. The pay-with-x402 path spends USDC on Solana per call. Wallet addresses you query are sent to a third-party API.

Installation

In SourceWeft

  1. Open Solana MCP by Vybe in the dashboard and add it to a workspace.
  2. Connect X-API-KEY credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.vybenetwork%2Fvybe-solana-api/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "solana-by-vybe": {
      "type": "http",
      "url": "https://docs.vybenetwork.com/mcp",
      "headers": {
        "X-API-KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

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:

text
https://mcp.vybenetwork.xyz/mcp

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

text
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

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

Same snippet: .mcp.json.

Claude Desktop via mcp-remote

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

Claude.ai custom connector or Connectors Directory

text
Name: Solana MCP by VybeURL:  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:

bash
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):

    bash
    git tag vX.Y.Zgit 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:

    bash
    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.

Source: README.md at commit 659c3ff

Tools

5

list-endpoints

List API Endpoints

Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.

Takes no parameters.

get-endpoint

Get Endpoint Details

Gets detailed information about a specific API endpoint, including security schemes and servers

Parameterspathrequiredmethodrequired

search-endpoints

Search API Endpoints

Performs 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'.

Parameterspatternrequired

execute-request

Execute API Request

Executes an API request with a given HAR request object.

ParametersharRequestrequired

pay-with-x402

Pay With X402

Before 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.

Takes no parameters.

Version history

1
  1. v1.0.9LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.