Skip to main content
Glama
47620 Solana Data

47620 Solana Data

by 47620-xyz
README.md
# 47620 Solana Data — MCP server

Give any MCP-capable AI agent (Claude, Cursor, Windsurf, OpenClaw, …) native access to
**[47620](https://47620.xyz)** pay-per-call Solana data, settled over **x402** (HTTP 402) in
USDC on Solana — **non-custodial, no signup, no API key**.

## Tools

| Tool | What it returns | Price |
| --- | --- | --- |
| `solana_health` | Current slot, epoch, SOL/USD | $0.001 |
| `solana_token` | Price, liquidity, 24h volume, DEX pairs for an SPL mint | $0.002 |
| `solana_account` | SOL + all SPL token balances for an address | $0.002 |
| `solana_tx` | Status, slot, fee, transfers for a tx signature | $0.003 |
| `solana_trending` | Trending Solana DEX pairs by 24h volume | $0.005 |

Each tool call is an x402 paid request: the server gets a `402`, pays USDC to the merchant
wallet on Solana, and retries with the payment header. Funds go **directly to the seller's
wallet**; a 1% platform fee is a second on-chain transfer.

## Install

Run straight from GitHub (no npm publish needed):

```bash
npx -y github:47620-xyz/solana-data-mcp
```

Or clone and run:

```bash
git clone https://github.com/47620-xyz/solana-data-mcp
cd solana-data-mcp && npm install && node src/index.js
```

## Configure (Claude Desktop / Cursor / any MCP client)

```json
{
  "mcpServers": {
    "47620-solana-data": {
      "command": "npx",
      "args": ["-y", "github:47620-xyz/solana-data-mcp"],
      "env": {
        "X402_BASE_URL": "https://47620.xyz",
        "X402_WALLET_KEY": "<base58 Solana secret key>"
      }
    }
  }
}
```

### Payment modes

1. **`X402_WALLET_KEY`** — base58 secret key of a Solana wallet that holds a little USDC + SOL.
   The server signs the transfer and retries automatically. **Fully autonomous** (best for agents).
2. **`X402_PAY_URL`** — an HTTP payment broker: `POST { url, challenge } → { header }`. For hosted /
   MPC wallets where the key never touches the process.
3. **neither** — the tool returns the `402` challenge plus a ready-to-run
   `npx awal x402 pay "<url>"` command, so the agent (or its x402-aware runtime) pays.

## Env vars

| Var | Default | Notes |
| --- | --- | --- |
| `X402_BASE_URL` | `https://47620.xyz` | API base |
| `X402_WALLET_KEY` | — | base58 Solana secret key (payment mode 1) |
| `X402_PAY_URL` | — | payment broker (payment mode 2) |
| `X402_RPC_URL` | mainnet-beta | Solana RPC for settlement |

## Try it

```jsonc
// agent prompt
"Use solana_trending to get the top Solana DEX pairs right now."
```

## Also available

- **HTTP API** directly: `GET https://47620.xyz/x/solana/trending` → `402` (pay & retry)
- **Agent Skill**: `npx skills add 47620-xyz/solana-data-skills`
- **Gateway**: https://47620.xyz — payment buttons for ecommerce, non-custodial

## License

MIT

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct Solana data resource: network health, token price, account balances, transaction status, and trending pairs. There is no overlap in purpose.

Naming Consistency5/5

All tools follow the exact verb_noun-like pattern 'solana_' plus a clear resource name (health, token, account, tx, trending). Perfectly consistent.

Tool Count5/5

Five tools cover the core Solana data access needs without bloat. The count is well-scoped for a data-focused server.

Completeness4/5

Provides essential reads: network status, token prices, account balances, transaction details, and trending activity. Minor gaps like historical account transfers or block details exist, but the main domain is well covered.