Finance · Remote MCP server
47620 Solana Data API
X402 pay-per-call Solana data + crypto market + JWT/unit utils for AI agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
xyz.47620/solana-data- Version
- 1.1.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-28
- Updated
- 2026-09-28
- Publisher
- xyz.47620 · 3 servers with pages here
- Listed under
- Solana MCP servers
- Repository
- github.com/47620-xyz/solana-data-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://47620.xyz/mcp/solana | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | 47620-solana-mcp | 1.1.0 | stdio |
How to connect 47620 Solana Data API
47620 Solana Data API is a remote MCP server: there is nothing to install. Its endpoint is https://47620.xyz/mcp/solana, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: 47620-solana-mcp version 1.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y 47620-solana-mcp@1.1.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"solana-data": {
"command": "npx",
"args": [
"-y",
"47620-solana-mcp@1.1.0"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from xyz.47620
| Server | Runs |
|---|---|
| 47620 Base + Polygon Data APIPay-per-call Base and Polygon onchain data over x402 for AI agents. | Remote & Local · HTTP, stdio |
| 47620 Multichain Data API — onchain, crypto, utilities, x402 statsX402 pay-per-call: onchain data (Solana/Base/Polygon), crypto market, JWT/unit utils, x402 stats. | Remote · HTTP |
More finance servers
| Server | Runs |
|---|---|
| 402SignalCheck paid API offers before your agent spends. Qualifying routes: $0.003 USDC. Normal misses: free. | Remote · HTTP |
| 42matters42matters MCP — wraps the 42matters App Market Data API (42matters.com) | Remote · HTTP |
| 47620 Solana DataPay-per-call Solana data for AI agents over x402: token, account, tx, trending. No signup, no key. | Remote · HTTP |
| A0nexus Bitcoin MCPCrypto (BTC/ETH) + ERCOT electricity data & forecasts as MCP tools. Pay-per-call via x402. | Local · stdio |
| A2AWireEscrow, reputation, and payments for agent-to-agent commerce. Non-custodial USDC/Base L2. | Remote · HTTP, SSE |
| aaaa-nexus — Formally Verified AI Safety APIsFormally verified AI safety APIs. Pay-per-call via USDC (x402). 75+ endpoints, no signup. | Remote · HTTP |
| AAAA-Nexus MCPFormally verified AI safety APIs. 75+ endpoints, pay-per-call via USDC x402, no signup. | Local · stdio |