Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
MCP registry metadata for the Vybe Solana API
This repo holds the public registry and client install metadata for Solana MCP by Vybe. It points MCP clients at `https://mcp.vybenetwork.xyz/mcp`, with separate files for registry publishing, directory installs, and Codex plugin setup.
Builders who want their agent to browse Solana schemas or call a live Solana API through MCP.
You can connect an MCP client to a public Solana API without wiring up your own server metadata.
What it does
Public MCP endpoint metadata
Publishes the remote server URL and registry details for `https://mcp.vybenetwork.xyz` and `https://mcp.vybenetwork.xyz/mcp`.
Client setup snippets
Shows ready-to-copy JSON for Cursor, Windsurf, Codex-style HTTP clients, and Claude Desktop via `mcp-remote`.
Registry publishing files
Includes `server.json` and GitHub Actions flow for publishing to the official MCP Registry.
Codex plugin metadata
Provides `.codex-plugin/plugin.json` for local Codex install and refresh.
Tool list for the API server
Documents tools like `list-endpoints`, `search-endpoints`, `get-endpoint`, `execute-request`, and `pay-with-x402`.
How to get it
- 1Run
Name: Solana MCP by Vybe URL: https://mcp.vybenetwork.xyz/mcp
README
Solana MCP by 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.
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.
Copy-paste setup for the public docs site: docs/mcp.md. Live product guides: docs.vybenetwork.com/docs/mcp (still may show the old .com host until that site is updated).
Quick setup
Cursor / Windsurf / Codex-style HTTP
{
"mcpServers": {
"solana-mcp-vybe": {
"type": "http",
"url": "https://mcp.vybenetwork.xyz/mcp"
}
}
}
Same snippet: examples/cursor-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
Name: Solana MCP by Vybe
URL: https://mcp.vybenetwork.xyz/mcp
Authenticate with OAuth when the client prompts. Do not commit API keys into this repo.
What this repository holds
server.json— metadata published to the official MCP Registry (GitHub Actions). Remote URL:https://mcp.vybenetwork.xyz..mcp.jsonandmcp.json— root MCP/plugin configs for directory UIs (e.g. Cursor “Submit a Plugin”). Native HTTP tohttps://mcp.vybenetwork.xyz/mcp— no secrets..codex-plugin/plugin.json— Codex plugin metadata for local install/refresh against the same MCP URL.chatgpt-app-submission.json— draft ChatGPT Apps submission fields.
Available tools
| Tool | Description |
|---|---|
list-endpoints | Browse API paths with methods and summaries |
search-endpoints | Search paths, operations, and schemas by keyword |
get-endpoint | Full OpenAPI details for one path and method |
execute-request | Live authenticated API calls |
pay-with-x402 | x402 pay-per-call integration guidance |
GitHub repository name
vybenetwork/solana-mcp-vybe (starts with solana-mcp, includes Vybe).
Publish a new listing version
-
Clone or use this repo at
github.com/vybenetwork/solana-mcp-vybe -
Tag and push (the workflow sets
server.jsonversionfrom the tag):git tag v1.0.0 git push origin v1.0.0Or 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.
-
Verify:
curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=vybenetwork" | jq .
Cursor and other directories
Use examples/cursor-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.
Files in the repo
- .codex-plugin
- .github
- assets
- docs
- examples
- .gitignore
- .mcp.json
- chatgpt-app-submission.json
- mcp.json
- README.md
- server.json
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More connectors
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

Universal provider proxy for OpenAI Codex & Claude Code — use any LLM (Claude, Gemini, Grok, DeepSeek, Ollama…) with Codex CLI, App, SDK, and Claude Code
Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zero external databases or dependencies. Built in pure Go.
Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows.
Stop your AI from making things up — it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.