Solana MCP by Vybe
REMOTE · MCP.VYBENETWORK.XYZ · SCANNED SEP 20
Solana MCP developer toolkit: wallets, trades, markets, PnL, transfers, onchain, swaps & API tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security95
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 773 tokens (~110/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability check failed: schema churn in the 26 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay-with-x402" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Solana MCP by Vybe server?
Solana MCP by Vybe is a hosted endpoint at https://mcp.vybenetwork.xyz/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.vybenetwork.xyz
claude mcp add --transport http vybenetwork-solana-mcp-vybe 'https://mcp.vybenetwork.xyz/'
{
"mcpServers": {
"vybenetwork-solana-mcp-vybe": {
"url": "https://mcp.vybenetwork.xyz/"
}
}
} {
"servers": {
"vybenetwork-solana-mcp-vybe": {
"type": "http",
"url": "https://mcp.vybenetwork.xyz/"
}
}
} [mcp_servers.vybenetwork-solana-mcp-vybe] url = "https://mcp.vybenetwork.xyz/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vybenetwork-solana-mcp-vybe": {
"type": "remote",
"url": "https://mcp.vybenetwork.xyz/",
"enabled": true
}
}
} openclaw mcp add vybenetwork-solana-mcp-vybe --url 'https://mcp.vybenetwork.xyz/' --transport streamable-http
mcp_servers:
vybenetwork-solana-mcp-vybe:
url: "https://mcp.vybenetwork.xyz/" {
"McpServers": {
"vybenetwork-solana-mcp-vybe": {
"Transport": "http",
"Url": "https://mcp.vybenetwork.xyz/"
}
}
} assistant mcp add vybenetwork-solana-mcp-vybe -t streamable-http -u 'https://mcp.vybenetwork.xyz/'
{
"mcpServers": {
"vybenetwork-solana-mcp-vybe": {
"type": "http",
"url": "https://mcp.vybenetwork.xyz/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67.
- 17 Sept 26 −1
- Stability: 0.73 → fail ▼ security
- Tool “execute-request” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “build-vybe-transaction”, which the server declares destructive security
- Schema quality: 57 → 110 ▼ functional
- Destructive annotations: 50% → 0% ▼ functional
- Tool “get-endpoint” now declares an output schema ▲ functional
- Tool “list-endpoints” now declares an output schema ▲ functional
- Tool “pay-with-x402” now declares an output schema ▲ functional
- Tool “search-endpoints” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- Server version: 1.1.3 → 1.2.0 functional
- New tool “query-vybe-api” functional
- New tool “query-vybe-api-batch” functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.vybenetwork.xyz
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.vybenetwork.xyz | CN=WR3,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | RSA 2048 | SHA256-RSA | d7955d79c6f97f3b10894b17df288058 |
| SANs: mcp.vybenetwork.xyz | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.vybenetwork.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| vybenetwork.xyz. | present | 53761 | 8 | Verified |
| mcp.vybenetwork.xyz. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://mcp.vybenetwork.xyz/.well-known/oauth-protected-resource/mcp"
Bearer realm="mcp", resource_metadata="https://mcp.vybenetwork.xyz/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://mcp.vybenetwork.xyz/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.vybenetwork.xyz/mcp |
| Authorisation server | https://mcp.vybenetwork.xyz |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.vybenetwork.xyz | Verified | 200 | |
| http (plaintext) | http://mcp.vybenetwork.xyz | HTTPS enforced | 302 | https://mcp.vybenetwork.xyz/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build-vybe-transaction Build Unsigned Solana Transaction ~155
Builds 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | JSON request body for the endpoint. Call get-endpoint for the exact schema. |
| path | string | yes | Transaction builder endpoint to call. |
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| status | integer | – | – |
No examples provided.
get-endpoint Get Endpoint Details ~65
Gets detailed information about a specific API endpoint, including security schemes and servers
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | The HTTP method (e.g. GET, POST, PUT, DELETE). |
| path | string | yes | The API endpoint path (e.g. /api/v1/users). |
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | – |
| operation | object | – | – |
| path | string | – | – |
No examples provided.
list-endpoints List API Endpoints ~35
Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | object | – | – |
No examples provided.
pay-with-x402 Pay With X402 ~54
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | – | – |
| guidance | string | – | – |
No examples provided.
query-vybe-api Query Vybe Solana API ~189
Runs 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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Vybe API path beginning with /v4, with any path parameters already substituted (e.g. /v4/wallets/HN7.../pnl). |
| query | object | – | Optional query string parameters as name/value pairs (e.g. {"limit": "3", "resolution": "1d"}). |
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| status | integer | – | – |
No examples provided.
query-vybe-api-batch Query Vybe Solana API (Batch Wallets) ~124
Reads 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | JSON request body for the endpoint, typically the list of wallet addresses. Call get-endpoint for the exact schema. |
| path | string | yes | Batch read endpoint to call. |
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| status | integer | – | – |
No examples provided.
search-endpoints Search API Endpoints ~70
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| pattern | string | yes | Search pattern (case-insensitive) |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | – | – |
No examples provided.
What is the Solana MCP by Vybe server?
Solana MCP by Vybe is listed in the public MCP registry as io.github.vybenetwork/solana-mcp-vybe. Solana MCP developer toolkit: wallets, trades, markets, PnL, transfers, onchain, swaps & API tools. This page covers its hosted endpoint (https://mcp.vybenetwork.xyz).
Is the Solana MCP by Vybe server safe to use?
Solana MCP by Vybe scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Solana MCP by Vybe server expose?
Solana MCP by Vybe exposes 7 tools: list-endpoints, get-endpoint, search-endpoints, query-vybe-api, query-vybe-api-batch, and 2 more. Their descriptions and schemas cost roughly 692 tokens of context every time the server is loaded.
Does the Solana MCP by Vybe server require authentication?
Yes. Solana MCP by Vybe asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Solana MCP by Vybe server still maintained?
Solana MCP by Vybe is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.