Sato Hub
MCP

Vybe Solana MCP

Hosted Solana MCP from Vybe Network: schema browsing plus live Solana API calls, no local deployment.

  • Sato Score86
  • ChainsSolana
ActiveSelf-ReportedQuiet · 5mo ago

Vybe Solana MCP is an open-source MCP server by Vybe Network on Solana, with last code activity on 2026-05-11 (Quiet). Latest release on 2026-05-11. Sato Score 86/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Vybe Solana MCP →

Last commit May 11, 2026 · Last release May 11, 2026 · ★ 213

Listed from github.com/vybenetwork/solana-mcp-vybe on 2026-07-13. Install: not attempted. Evidence →

Next step

Watch Vybe Solana MCP

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on vybenetwork/solana-mcp-vybe before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Vybe's Solana MCP server is a hosted (remote) Model Context Protocol endpoint at mcp.vybenetwork.xyz that lets agents browse Vybe's Solana API schemas and make live calls for Solana chain data without running any server locally. A builder points an MCP client (Cursor, Claude) at the hosted URL and authenticates via OAuth to give an agent direct access to Vybe's Solana data feeds.

Sato Score

86/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
19/20
Interface verifiability
10/10
Docs & demo
6/10
Listing transparency & provenance
13/15
Independent verification
3/10

Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).

Evidence — listed vs checked · what the words mean

Listed from github.com/vybenetwork/solana-mcp-vybe on 2026-07-13. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedSolanaself-reporteddocs.vybenetwork.comas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedgithub.com/vybenetwork/solana-mcp-vybeas of 2026-10-15
Recent activitylast release 2026-05-11 · last commit 2026-05-11observedgithub.com/vybenetwork/solana-mcp-vybe2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_specself-reporteddocs.vybenetwork.comas of 2026-09-14
MCP endpoint answersanswered — 7 tools listedobservedmcp.vybenetwork.xyz2026-10-15
Daily check record44 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Deploys asHosted API (remote MCP over OAuth)confidence 0.90self-reporteddocs.vybenetwork.comas of 2026-07-14
Works withCursor, Claude Desktop, Claude.ai, Windsurf, VS Code (Copilot), Cline, Continue…confidence 0.90self-reporteddocs.vybenetwork.comas of 2026-07-14
Sato Score86/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — not run by us — no falsifiable install+entry probe from deploy_spec

Runtime: remote

Add MCP connector with URL https://mcp.vybenetwork.xyz (client authenticates via OAuth) — e.g. npx mcp-remote https://mcp.vybenetwork.xyz for clients needing a local bridge
https://mcp.vybenetwork.xyz

You supply: OAuth sign-in via the MCP client (no static API key in the repo)

Add to CursorAdd to VS Code
claude mcp add --transport http satohub-vybe-solana-mcp https://mcp.vybenetwork.xyz/

A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-09-14. What a deploy spec is →

Tool inventory — 7 tools, probed live 2026-10-15

  • list-endpoints — Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
  • get-endpoint — Gets detailed information about a specific API endpoint, including security schemes and servers
  • search-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 searc
  • query-vybe-api — 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
  • query-vybe-api-batch — 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
  • build-vybe-transaction — 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 t
  • 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.
Answers a handshake
yes · 2026-10-15
Answers a call
not asked — HTTP 401

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Observed record — 91 daily checks since 2026-07-17

100%of 45 checks since 2026-09-01 succeeded
Currently responding for 52 days
Succeeded
54
Failed
37
Their error
0
Unattributed
37

State changed on 2026-07-19 (responding → unclear), 2026-08-25 (unclear → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
7
from the server's own tools/list · 29/30 days
Sato Score
86
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Tool inventory history — 7 now, peak 7, since 2026-08-25

  • 2026-09-17 5 → 7 +3 (build-vybe-transaction, query-vybe-api, query-vybe-api-batch) −1 (execute-request)

Recorded from our own daily tools/list handshake. A shrinking toolset is a real signal for an agent choosing a server; a gap in the series means the probe did not succeed that day, not that the tools disappeared.

Details

Chains
Solana
Agent types
MCP Server, Data Provider
Open source
Yes
Deploys as
Hosted API (remote MCP over OAuth)
Works with
Cursor, Claude Desktop, Claude.ai, Windsurf, VS Code (Copilot), Cline, Continue, OpenCode
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#solana#hosted#data-provider
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Vybe Solana MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Aug 25, 2026
    Sato Score tier: Medium → High
    Score 51 → 83.
  2. Jul 20, 2026
    Edited: mcp endpoint url
  3. Jul 19, 2026
    Edited: mcp endpoint url
  4. Jul 18, 2026
    Sato Hub began tracking this listing
  5. Jul 14, 2026
    Enriched: has pricing
  6. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  7. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Vybe Solana MCP

Is Vybe Solana MCP open source?
Yes. Vybe Solana MCP is open source; the repository is https://github.com/vybenetwork/solana-mcp-vybe. Checked as of 2026-10-15.
Which chains does Vybe Solana MCP support?
Vybe Solana MCP lists support for Solana as of 2026-10-15.
Is Vybe Solana MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-05-11 (last commit 2026-05-11, last release 2026-05-11), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Vybe Solana MCP?
remote. Install: Add MCP connector with URL https://mcp.vybenetwork.xyz (client authenticates via OAuth) — e.g. npx mcp-remote https://mcp.vybenetwork.xyz for clients needing a local bridge. Entry: https://mcp.vybenetwork.xyz. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.vybenetwork.xyz).
Is Vybe Solana MCP verified on Sato Hub?
Sato Hub holds one earned check for Vybe Solana MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 86 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Vybe Solana MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/vybe-solana-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.