Skill
vybe-api-explorer
Explore and call the Vybe Solana API catalog through MCP — discover endpoints, inspect OpenAPI params, then run authenticated live requests. Use when the user…
@vybenetworkView SkillData
Skill
/vybe-wallet-analytics
Analyze Solana wallets with Vybe MCP — balances, holdings, PnL, transfers, and counterparties. Use when the user asks about a wallet address, portfolio, realized/unrealized PnL, token accounts, or transfer history on Solana.
Install
$ npx -y skills add vybenetwork/solana-mcp-vybe --skill vybe-wallet-analytics --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/vybe-wallet-analytics
Context preview
The summary Claude sees to decide when to auto-load this skill.
Analyze Solana wallets with Vybe MCP — balances, holdings, PnL, transfers, and counterparties. Use when the user asks about a wallet address, portfolio, realized/unrealized PnL, token accounts, or transfer history on Solana.
SKILL.md
vybe-wallet-analytics.SKILL.mdname: vybe-wallet-analytics
description: Analyze Solana wallets with Vybe MCP — balances, holdings, PnL, transfers, and counterparties. Use when the user asks about a wallet address, portfolio, realized/unrealized PnL, token accounts, or transfer history on Solana.
Vybe wallet analytics
Use the **Solana MCP by Vybe** tools (`list-endpoints`, `search-endpoints`, `get-endpoint`, `query-vybe-api`, `query-vybe-api-batch`) to answer wallet questions with live data.
When to use
- Wallet balances, holdings, or portfolio value
- Realized / unrealized PnL for a wallet
- Transfer history or counterparties
- Empty / dust token accounts
Workflow
1. Confirm you have a Solana wallet address (base58 pubkey). If missing, ask for it. 2. Discover the right route:
- Prefer `search-endpoints` with keywords like `wallet`, `pnl`, `transfer`, `token-balance`.
- Or `list-endpoints` then pick the matching path.
3. Call `get-endpoint` for the chosen path + method to learn required params, auth, and response shape. 4. Call `query-vybe-api` with the `path` and `query` params, or `query-vybe-api-batch` when covering several wallets in one call. 5. Summarize results for the user: top holdings, USD values when present, PnL figures, notable counterparties. Cite the endpoint used. 6. Offer a clear follow-up (e.g. deeper PnL window, specific mint, transfer filters).
Rules
- Never ask for or handle private keys / seed phrases.
- Do not broadcast transactions; if a route returns an unsigned tx, say the user must sign in their own wallet.
- If OAuth / auth is required, tell the user to connect the Vybe MCP connector and retry.
- Prefer read-only endpoints for analytics. Use `build-vybe-transaction` only when the user explicitly asks for a transaction payload.
Read more
name: vybe-wallet-analytics description: Analyze Solana wallets with Vybe MCP — balances, holdings, PnL, transfers, and counterparties. Use when the user asks about a wallet address, portfolio, realized/unrealized PnL, token accounts, or transfer history on Solana.
Vybe wallet analytics
Use the **Solana MCP by Vybe** tools (`list-endpoints`, `search-endpoints`, `get-endpoint`, `query-vybe-api`, `query-vybe-api-batch`) to answer wallet questions with live data.
When to use
- Wallet balances, holdings, or portfolio value
- Realized / unrealized PnL for a wallet
- Transfer history or counterparties
- Empty / dust token accounts
Workflow
1. Confirm you have a Solana wallet address (base58 pubkey). If missing, ask for it. 2. Discover the right route:
- Prefer `search-endpoints` with keywords like `wallet`, `pnl`, `transfer`, `token-balance`.
- Or `list-endpoints` then pick the matching path.
3. Call `get-endpoint` for the chosen path + method to learn required params, auth, and response shape. 4. Call `query-vybe-api` with the `path` and `query` params, or `query-vybe-api-batch` when covering several wallets in one call. 5. Summarize results for the user: top holdings, USD values when present, PnL figures, notable counterparties. Cite the endpoint used. 6. Offer a clear follow-up (e.g. deeper PnL window, specific mint, transfer filters).
Rules
- Never ask for or handle private keys / seed phrases.
- Do not broadcast transactions; if a route returns an unsigned tx, say the user must sign in their own wallet.
- If OAuth / auth is required, tell the user to connect the Vybe MCP connector and retry.
- Prefer read-only endpoints for analytics. Use `build-vybe-transaction` only when the user explicitly asks for a transaction payload.
Ships withsolana-mcp-vybe
Solana MCP by Vybe lets Cursor, Claude, Codex, and other MCP clients browse schemas or make live Solana API calls through one public MCP server. Public Model Context Protocol (MCP) registry metadata for Solana MCP by Vybe.
Get the whole plugin
Stats
1,285
Stars
98
Forks
Active
Maintenance
23h ago
Last commit
5mo ago
Created
Repo: vybenetwork/solana-mcp-vybe
In this plugin
See everything inside Other skills on solana-mcp-vybe.
@vybenetworkView SkillSkill
vybe-token-market-inte…
Solana token and market intelligence via Vybe MCP — prices, holders, liquidity, candles, DEX trades, and top traders. Use when the user asks about a mint,…
@vybenetworkView Skill