PumpView — Solana Trading & Live Data
Solana swaps with local signing, confirmed receipts, trading volume and filtered live trade data.
التثبيت
أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: .cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).
claude mcp add --transport http pumpview-solana-trading-live-data 'https://api.pumpview.fun/mcp/' --header 'Authorization: <Bearer <PumpView API key>. Get a key from your account or through wallet-signature onboarding.>'
{
"mcpServers": {
"pumpview-solana-trading-live-data": {
"type": "http",
"url": "https://api.pumpview.fun/mcp/",
"headers": {
"Authorization": "<Bearer <PumpView API key>. Get a key from your account or through wallet-signature onboarding.>"
}
}
}
}
التوثيق
مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.
المحتويات
PumpView Agent Kit
Solana trading and live trade data for AI agents. Build a swap, sign locally, submit through PumpView, and read the execution receipt from confirmed onward.
Trading API · Dashboard · Quickstart · OpenAPI
Listed in the official MCP Registry
as fun.pumpview/trading. The hosted server uses the verified pumpview.fun domain namespace.
Also available in the Glama MCP directory.
Connect an agent
Install the skill from this repository:
npx skills add grinchdev/pumpview-agent-kits --skill pumpview-trading
Or configure a remote MCP connection in a client that supports custom headers:
URL: https://api.pumpview.fun/mcp/
Transport: Streamable HTTP
Authorization: Bearer <PUMPVIEW_API_KEY>
Header configuration syntax depends on your client. PumpView uses API keys, not OAuth. Keep the real key in your client's secret store. Initialization, tool discovery and trading configuration are public; account operations require your key. Installing a skill does not create an account or authorize spending.
Try public discovery without a key (Node 18+):
node examples/mcp-discovery.mjs
Get access
Existing PumpView account: sign in to the dashboard, link your signing wallet and create an API key.
Agent-owned wallet: request /v1/agent/challenge, sign its exact message
locally and exchange the signature at /v1/agent/access. This creates a key
without browser registration. See the
wallet onboarding reference.
Never send PumpView a private key or seed phrase.
Attribution
Keys record an optional acquisition_source at creation so PumpView can report
requests and confirmed volume by acquisition channel. For a npx skills
installation use skills_sh; for a ClawHub install use clawhub; direct GitHub
users can use github. Unknown kit installs use agent_kit. The Python client's
complete_wallet_access(..., acquisition_source="skills_sh") accepts the label.
This is client-declared attribution, not referral verification. Do not send raw
referrer URLs or secrets. It does not change fees, limits or permissions.
Buy live-data access through MCP
Use list_data_plans → get_payment_instructions → prepare_invoice_payment.
Review the invoice and unsigned payment, then sign and broadcast using your
local wallet. Call confirm_invoice_payment with that transaction signature
until finalized, then read get_access_status. get_invoice_status recovers
an existing invoice. Never repeat a payment while confirmation is pending.
Trading itself does not require a data package. No Coinbase service is needed.
Python client
Python 3.10+; the client has no runtime dependencies. Install from a local clone:
git clone https://github.com/grinchdev/pumpview-agent-kits.git
cd pumpview-agent-kits
python -m pip install -e .
Load PUMPVIEW_API_KEY through your environment or secret manager, then build
an unsigned 0.06 SOL → USDC swap with 1% slippage:
python examples/build_swap.py --wallet YOUR_LINKED_PUBLIC_KEY --output USDC --amount 60000000 --slippage-bps 100 --state state/intent-001.json
The example persists its request ID before contacting PumpView. Run it with the same file and arguments to recover after a build timeout. It only builds and simulates; it never signs or submits. USD minimum checks use current prices, so the amount in this example may need adjustment before starting a new intent.
The client also provides wallet_challenge, complete_wallet_access,
trading_config, swap_status, trading_usage, recent_trades, and
submit_swap. submit_swap broadcasts a transaction and can spend funds.
Supply only bytes reviewed and signed by the user's authorized local wallet.
import os
from pumpview_agent_kit import PumpView
client = PumpView(os.environ["PUMPVIEW_API_KEY"])
policy = client.trading_config()
volume = client.trading_usage()
# Recover a known submission without creating or sending another trade:
# receipt = client.swap_status(saved_swap_id)
For TypeScript, examples/build_swap.mts runs directly on Node 22.18+.
Provide PUMPVIEW_API_KEY, PUMPVIEW_WALLET, PUMPVIEW_OUTPUT,
PUMPVIEW_AMOUNT, PUMPVIEW_SLIPPAGE_BPS and a previously persisted
PUMPVIEW_REQUEST_ID; PUMPVIEW_INPUT defaults to SOL. Run
node examples/build_swap.mts. This example also only builds/simulates.
Trading workflow
- Read
/v1/swaps/configfor availability, supported pairs and current costs. - Persist a unique request ID and exact intent. Build with REST or MCP.
- Review the returned versioned message, minimum output, fees and tips against the approved intent; sign the exact message using your own wallet adapter.
- Persist the build ID and signed bytes securely. Submit the signed transaction.
- Poll the same swap ID. A
submittedresponse is not execution. Receipts start atconfirmed; continue polling when you needfinalizedsettlement.
The SDK deliberately has no automatic request retries or wallet signer.
After a build timeout, reuse the request ID; after a submit timeout, query the
same swap ID. Do not automatically change the blockhash or create a replacement.
Honor Retry-After on 429. The full
integration reference covers
authentication, recovery and atomic units.
Costs and supported pairs
- Trading API access has no subscription charge. Executed swaps have a 0.5% platform fee, plus tips and network costs. Minimum tips: 0.002 SOL.
- At least one leg must be SOL, WSOL or native Solana USDC. Other TOKEN–TOKEN swaps and wrapping-only SOL–WSOL requests are unsupported. Routing uses Jupiter; availability depends on the token and current pools.
SOLmeans native SOL with wrap/unwrap;WSOLmeans the SPL token balance. ExactIn amounts are integer strings in atomic units; slippage is explicit.- Minimum swap: $5 equivalent without Unlimited. Unlimited removes that minimum. All trades still require enough SOL for costs and applicable rent.
- PumpView sends through its landing infrastructure to 4 validators simultaneously with MEV protection. PumpView reports measured inclusion in the current block under 100 ms; this is its own benchmark, not a confirmed/finalized timing SLA.
- Authenticated HTTP and MCP calls share 3 / 5 / 20 requests per second per account for Free or Day Pass / Starter / Unlimited. Keys do not multiply limits.
Live data and volume
Trading and live-data access are separate. Data requires an active package; current plans are authoritative. Unlimited currently costs 49 USDC for 30 days. Every plan shares one WSS connection per account. Direct USDC invoice payment does not require Coinbase.
get_recent_trades returns accepted swap summaries; get_stream_connection
describes wss://api.pumpview.fun/v1/stream. Your agent runtime maintains the
socket and replay cursor. The feed preserves PumpView's suspicious-price filter
and decoder coverage; it is not every individual Solana swap or archival history.
get_trading_usage / /v1/swaps/usage returns account and per-key executed
volume. Confirmed swaps count once; finalization and repeated polls do not add
volume. USD totals use build-time price estimates; unpriced swaps remain visible.
Development
python -m unittest discover -s tests
server.json describes the hosted MCP for the official Registry. Publishing the
manifest does not deploy a new server. The hosted service retains its own access
controls and fees. This repository contains client code, examples and agent
instructions under MIT; it does not contain backend credentials or signing keys.
الأسئلة الشائعة
ما هو PumpView — Solana Trading & Live Data؟
Solana swaps with local signing, confirmed receipts, trading volume and filtered live trade data.
كيف أثبّت PumpView — Solana Trading & Live Data؟
يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http pumpview-solana-trading-live-data 'https://api.pumpview.fun/mcp/' --header 'Authorization: <Bearer <PumpView API key>. Get a key from your account or through wallet-signature onboarding.>'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.
هل يحتاج PumpView — Solana Trading & Live Data إلى مفتاح API؟
نعم. يتطلب Authorization، وتضبطها في إعداداته.
هل PumpView — Solana Trading & Live Data مفتوح المصدر؟
نعم. شيفرته متاحة على GitHub بترخيص MIT.
من يصون PumpView — Solana Trading & Live Data؟
ينشره grinchdev. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.
من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.