# PumpView — Solana Trading & Live Data (remote · api.pumpview.fun) Solana swaps with local signing, confirmed receipts, trading volume and filtered live trade data. - Trust score: 64/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-17 ## Components - remote · `api.pumpview.fun`: 64/100 (this document), [markdown](https://verifymcp.io/servers/fun-pumpview-trading/api.md), [page](https://verifymcp.io/servers/fun-pumpview-trading/api) ## Channel facts - Endpoint: `https://api.pumpview.fun/mcp/` - Transports: `streamable-http` - Auth: `none` - Version: `1.2.3` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-17. - **Endpoint Security**: 57/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_swap). - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 69/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 2836 tokens (~202/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 3/100 - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## Install ### How do I install the PumpView — Solana Trading & Live Data MCP server? PumpView — Solana Trading & Live Data is a hosted endpoint at https://api.pumpview.fun/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http fun-pumpview-trading 'https://api.pumpview.fun/mcp/' ``` ### Cursor ```json { "mcpServers": { "fun-pumpview-trading": { "url": "https://api.pumpview.fun/mcp/" } } } ``` ### VS Code ```json { "servers": { "fun-pumpview-trading": { "type": "http", "url": "https://api.pumpview.fun/mcp/" } } } ``` ### Codex ```toml [mcp_servers.fun-pumpview-trading] url = "https://api.pumpview.fun/mcp/" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "fun-pumpview-trading": { "type": "remote", "url": "https://api.pumpview.fun/mcp/", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add fun-pumpview-trading --url 'https://api.pumpview.fun/mcp/' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: fun-pumpview-trading: url: "https://api.pumpview.fun/mcp/" ``` ### Netclaw ```json { "McpServers": { "fun-pumpview-trading": { "Transport": "http", "Url": "https://api.pumpview.fun/mcp/" } } } ``` ### Vellum ```bash assistant mcp add fun-pumpview-trading -t streamable-http -u 'https://api.pumpview.fun/mcp/' ``` ### Other ```json { "mcpServers": { "fun-pumpview-trading": { "type": "http", "url": "https://api.pumpview.fun/mcp/" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-17 (score 64, +1) - [functional improvement] Stability: unverified → 0.03 ### 2026-10-16 (score 63) First indexed and scored. ## MCP tools (14) ### `get_onboarding_instructions` (~93 tokens) Get API-key setup and integration instructions before your first PumpView call. Public: no key or data credits needed. Returns dashboard/Agent Kit/docs URLs, ordered HTTP wallet-challenge steps, and separate trading/data workflows. Does not create an account, sign, pay or trade. Once connected, use get_trading_config for swap policy or get_access_status for your purchased access. Output parameters: - `account_access` (string): Dashboard URL for login, wallet linking and API keys. - `agent_kit` (string): Public PumpView examples and installable skill repository. - `authentication` (string): Authorization header template; replace the placeholder with your own secret key. - `data` (object): Paid live-data requirements and URL of the current plan catalog. - `documentation` (string): Markdown integration guide with HTTP onboarding and payment steps. - `mcp_url` (string): Streamable HTTP MCP endpoint. - `name` (string): Service name: PumpView. - `network` (string): Solana network used by the API: solana-mainnet. - `skill_install` (string): Command to install the PumpView trading skill. - `trading` (object): Trading subscription requirements, policy URL, tool names and signing workflow. - `wallet_access` (array): Ordered HTTP challenge, local message-signing and access-exchange steps; no private key is transmitted. ### `get_trading_config` (~93 tokens) Read the current server's swap policy before choosing build_swap parameters. Public: no API key or data credits needed. Returns enabled, mint aliases, allowed pair assets, fee basis points, USD minimums, tip limits and build TTL. enabled is configuration status, not a liquidity quote or an RPC health check. Use get_trading_usage for executed account volume and get_access_status for grants. Output parameters: - `build_ttl_seconds` (integer): Time window for submitting a newly built transaction before its unsigned intent expires. - `enabled` (boolean): Whether the trading proxy is currently configured and enabled; not a guarantee that a route exists. - `free_minimum_usd` (string): Minimum swap value in USD without an active Unlimited grant, as a decimal string. - `mint_aliases` (object): SOL, WSOL and USDC alias-to-mint mapping. SOL spends native balance; WSOL spends SPL balance. - `platform_fee_bps` (integer): Platform swap fee in basis points; 50 means 0.5%. - `receipt_commitment` (string): Earliest commitment at which execution receipts are available: confirmed. - `required_pair_assets` (array): At least one swap leg must resolve to an asset in this list; see mint_aliases. - `slippage_bps` (object): Whether explicit slippage is required and its inclusive minimum/maximum in basis points. - `subscription_required` (boolean): False: building and submitting swaps needs no paid data package. - `tips` (object): Minimum tip in lamports and transfer recipients disclosed for review before signing. - `unlimited_minimum_usd` (string): Minimum swap value in USD with Unlimited, as a decimal string. ### `build_swap` (~518 tokens) Build and simulate an unsigned ExactIn swap, without spending funds. Requires a Bearer API key and its linked wallet, but no data subscription or credits. Check get_trading_config first. At least one leg must be SOL/WSOL or USDC; minimum value is $5 unless Unlimited is active. Execution costs 0.5% plus tips and network fees. Returns id, unsigned transaction_base64, expiry, expected/minimum output and cost breakdown. Review them, sign locally, then call submit_swap. Persist request_id; retry the identical intent after a build timeout. A 409 means conflicting intent; 410 means expired build and requires an explicit decision to create a new intent. Never silently increase slippage. Input parameters: - `amount` (string, required): Exact input amount in atomic units, encoded as a decimal integer string, at most u64. SOL/WSOL has 9 decimals and USDC 6; resolve other token decimals first. Example: 0.06 SOL is "60000000". - `input_mint` (string, required): Asset to spend: SOL for native balance, WSOL for SPL wrapped balance, USDC, or a base58 token mint. One leg must resolve to SOL/WSOL/USDC. - `max_priority_fee_lamports` (integer): Cap on the compute-unit priority fee in lamports. Excludes the base network fee, tips, token-account rent and platform fee; 1000000 = 0.001 SOL. - `output_mint` (string, required): Asset to receive using the same aliases or a base58 mint. Must differ from the input after alias resolution; SOL-to-WSOL wrapping alone is unsupported. - `request_id` (string, required): Client-generated idempotency key, persisted before calling. Reuse with identical arguments after a timeout; changing the intent under this ID returns 409. - `slippage_bps` (integer, required): Explicit signer-approved slippage tolerance. 100 basis points = 1%; 10000 allows 100%. Never silently increase it to fix a failed route. - `tip_lamports` (integer): Total acceleration tip in SOL lamports, separate from platform and network fees. 2000000 lamports = 0.002 SOL; charged only if the signed transaction executes. - `wallet` (string, required): Base58 public key of the signing wallet linked to this API-key account. Obtain/link it through onboarding; never pass a private key. Output parameters: - `error`: Failure information if present. Preserve the swap ID and inspect status before deciding on any new intent. - `expected_output_amount` (string): Quoted output in atomic units; execution may differ within the slippage bound. - `expires_at` (integer): Unsigned build expiry as Unix seconds; not proof that a submitted transaction failed. - `id` (string): PumpView swap ID (32 lowercase hex characters), passed as swap_id to status and submit tools. - `input_amount` (string): Exact input amount as a string of integer atomic units. - `last_valid_block_height` (integer): Last block height accepted by the transaction blockhash. - `minimum_output_amount` (string): Slippage-protected output threshold in atomic units to review before signing. - `network_fee_lamports` (string): Estimated total network fee for the built message, as an integer string. - `platform_fee` (object): Fee basis points, mint, recipient account and calculation basis. - `receipt`: Actual execution details from confirmed onward; null before confirmation or while RPC transaction metadata is pending. - `request_id` (string): Original client-generated idempotency key for this intent. - `signature`: Solana transaction signature, or null before submission. Not interchangeable with the PumpView swap ID. - `status` (string): Lifecycle state: built, submitted, confirmed, finalized, failed, or expired. A send timeout may leave state uncertain; poll this ID. - `tips` (object): Total tip and transfer destinations for wallet review, in lamports. - `transaction_base64` (string): Unsigned Solana v0 transaction for local wallet signing; only returned for a build still in built state. ### `get_trading_usage` (~125 tokens) Read all-time executed volume for the authenticated account and each API key. Use for accounting, not market history (get_recent_trades) or one receipt (get_swap_status). Bearer key required; no data package or credits consumed. Returns available, totals and by_api_key. Successful swaps count once from confirmed; finalization never adds them again. SOL/USDC amounts are decimal strings; USD uses build-time prices. available=false means temporary unavailability, not zero volume. Newly confirmed receipts may appear shortly later. Output parameters: - `available` (boolean): False means statistics are temporarily unavailable, not that volume is zero. - `by_api_key` (array): Per-key volume buckets. An unused key may have no bucket yet. - `counted_from` (string): Earliest counted commitment: confirmed; finalization does not add volume again. - `message` (string): Explanation when statistics are unavailable. - `period` (string): Aggregation period: all_time. - `totals`: All-time executed account volume and count when available. ### `submit_swap` (~202 tokens) Broadcast the wallet-approved, signed build through Kolibrio. This can spend funds. Requires a Bearer key for the account that built the swap. Only the exact build_swap message is accepted; the wallet must already have reviewed and authorized its amounts and costs. Returns the swap ID, signature and current status; submitted is not confirmation. Repeating the same ID and signed bytes cannot create a different trade. After a timeout or uncertain delivery, poll get_swap_status; never automatically build a replacement or change its blockhash. Input parameters: - `signed_transaction_base64` (string, required): Standard base64 of the complete serialized Solana v0 transaction from this build, after local wallet signing. Preserve the original message and blockhash. Not a signature string, seed, private key or… - `swap_id` (string, required): PumpView id returned by build_swap for this account, not a Solana signature or request_id. Output parameters: - `error`: Failure information if present. Preserve the swap ID and inspect status before deciding on any new intent. - `expected_output_amount` (string): Quoted output in atomic units; execution may differ within the slippage bound. - `expires_at` (integer): Unsigned build expiry as Unix seconds; not proof that a submitted transaction failed. - `id` (string): PumpView swap ID (32 lowercase hex characters), passed as swap_id to status and submit tools. - `input_amount` (string): Exact input amount as a string of integer atomic units. - `last_valid_block_height` (integer): Last block height accepted by the transaction blockhash. - `minimum_output_amount` (string): Slippage-protected output threshold in atomic units to review before signing. - `network_fee_lamports` (string): Estimated total network fee for the built message, as an integer string. - `platform_fee` (object): Fee basis points, mint, recipient account and calculation basis. - `receipt`: Actual execution details from confirmed onward; null before confirmation or while RPC transaction metadata is pending. - `request_id` (string): Original client-generated idempotency key for this intent. - `signature`: Solana transaction signature, or null before submission. Not interchangeable with the PumpView swap ID. - `status` (string): Lifecycle state: built, submitted, confirmed, finalized, failed, or expired. A send timeout may leave state uncertain; poll this ID. - `tips` (object): Total tip and transfer destinations for wallet review, in lamports. - `transaction_base64` (string): Unsigned Solana v0 transaction for local wallet signing; only returned for a build still in built state. ### `get_swap_status` (~154 tokens) Check an existing account swap after submission, including after a timeout. Requires the owning account's Bearer key; no data credits consumed. Returns id, signature, status and receipt. States are built, submitted, confirmed, finalized, failed or expired. Execution receipts start at confirmed and may still be null while RPC metadata catches up. Poll this ID with backoff within the account rate limit; use get_trading_usage for aggregate volume. This call refreshes stored status/receipts but never submits, signs or rebuilds a trade. Input parameters: - `swap_id` (string, required): PumpView id returned by build_swap for this account, not a Solana signature or request_id. Output parameters: - `error`: Failure information if present. Preserve the swap ID and inspect status before deciding on any new intent. - `expected_output_amount` (string): Quoted output in atomic units; execution may differ within the slippage bound. - `expires_at` (integer): Unsigned build expiry as Unix seconds; not proof that a submitted transaction failed. - `id` (string): PumpView swap ID (32 lowercase hex characters), passed as swap_id to status and submit tools. - `input_amount` (string): Exact input amount as a string of integer atomic units. - `last_valid_block_height` (integer): Last block height accepted by the transaction blockhash. - `minimum_output_amount` (string): Slippage-protected output threshold in atomic units to review before signing. - `network_fee_lamports` (string): Estimated total network fee for the built message, as an integer string. - `platform_fee` (object): Fee basis points, mint, recipient account and calculation basis. - `receipt`: Actual execution details from confirmed onward; null before confirmation or while RPC transaction metadata is pending. - `request_id` (string): Original client-generated idempotency key for this intent. - `signature`: Solana transaction signature, or null before submission. Not interchangeable with the PumpView swap ID. - `status` (string): Lifecycle state: built, submitted, confirmed, finalized, failed, or expired. A send timeout may leave state uncertain; poll this ID. - `tips` (object): Total tip and transfer destinations for wallet review, in lamports. - `transaction_base64` (string): Unsigned Solana v0 transaction for local wallet signing; only returned for a build still in built state. ### `get_recent_trades` (~310 tokens) Read filtered market swap summaries from PumpView's supported SOL-pair feed. Use for recent market activity, not your submitted swap receipt (get_swap_status). Requires a Bearer key, active data grant and sufficient key budget. Each call consumes max(1, returned event count) credits; repeated reads also count. Unlimited has no package event cap, but an explicit key budget still applies. Returns events in feed order, a cursor and health. Filtering follows batch scanning, so advance using the returned cursor even for an empty batch. On 409 cursor_expired restart without after and record a gap; 402 means access or budget exhausted, 503 means unavailable source. Use get_stream_connection for continuous WSS delivery. Amounts are decoder floats, not full transaction accounting. Input parameters: - `after`: Opaque cursor returned by the previous batch. Omit for a recent snapshot; supply unchanged to scan subsequent events. Not a timestamp or transaction signature. - `limit` (integer): Maximum accepted events scanned before mint/wallet filters, 1-500; default 100. The number returned can be smaller, including zero. - `mint`: Optional exact token mint address in base58. Filters the traded token of the supported SOL-pair feed; omit for all mints. No ticker aliases. - `wallet`: Optional exact base58 trader public key reported by the decoder. Combined with mint using AND; omit for all wallets. Output parameters: - `cursor`: Resume position after the scanned batch, including events removed by filters; use as the next after value. - `events` (array): Accepted events after mint/wallet filtering. May be empty even when the cursor advances. - `health` (object): Feed connection status, last-message age, drop/replay-gap counters and price_filter identifier. ### `get_access_status` (~141 tokens) Inspect the authenticated account's live-data grants, rate limit and feed health. Call before consuming data or after an access error. Bearer key required; no data credits consumed. Returns unexpired grants (remaining=-1 means Unlimited), http_rate_limit shared across account keys, and source health. An empty grants list means no unexpired package; a grant can still have zero credits. Key-specific budgets are managed in the dashboard and are not in this response. Use get_trading_usage for swap volume, get_trading_config for swap policy, and get_payment_instructions to create a data-package invoice. Output parameters: - `grants` (array): Unexpired packages: id, plan, expires (Unix seconds), remaining credits (-1 means unlimited), max_filters and max_connections. Empty means no unexpired grant. - `http_rate_limit` (object): requests_per_second, scope=account, shared_with_mcp=true. The allowance is shared by all keys and HTTP/MCP calls. - `source` (object): Current local feed health: connected/source_connected, last_message_age_seconds, cursor, dropped-event and replay-gap counters. ### `get_payment_instructions` (~226 tokens) Create a new unpaid USDC invoice for a live-data package; this spends no funds. Call only after choosing a current plan with list_data_plans and checking get_access_status. Trading alone needs no data subscription. Requires a Bearer key and linked Solana wallet; missing wallet returns 409, unknown plan 404, disabled sales 503. Returns invoice id, payer, recipient, mint, atomic amount, memo and Unix expiry. Each call creates another invoice, so retain its ID rather than retry blindly. Next use prepare_invoice_payment, review/sign/broadcast with your wallet, then confirm_invoice_payment with the transaction signature. get_invoice_status checks settlement. submit_swap is for swaps, not invoice payments. Never pay an expired invoice or repeat a payment while confirmation is pending. Input parameters: - `plan` (string, required): Exact data-package id from list_data_plans. Current ids: day (Day Pass), starter (Starter), builder (Unlimited). Use the id, not the display name; confirm current price and availability first. Output parameters: - `amount` (integer): Exact invoice amount in USDC atomic units; divide by 10^decimals for USDC. - `created` (integer): Invoice creation time as Unix seconds. - `decimals` (integer): USDC decimals: 6. - `expires` (integer): Invoice expiry as Unix seconds; do not pay an expired invoice. - `id` (string): Invoice ID for prepare_invoice_payment, get_invoice_status and confirm_invoice_payment. - `memo` (string): Exact payment memo binding the transaction to this invoice. - `mint` (string): Native Solana USDC mint address required for this payment. - `network` (string): Required payment network: solana-mainnet. - `paid` (boolean): Whether the invoice has been settled. A newly created invoice is unpaid. - `payer` (string): Linked Solana wallet that must authorize payment. - `payment_protocol` (string): Payment workflow identifier: pumpview-invoice-v1. - `plan` (string): Selected plan ID from the current public plan catalog. - `recipient` (string): Public payment recipient to verify before signing. ### `list_data_plans` (~107 tokens) List current data packages and prices before buying a live-data subscription. Public: no key or credits needed. Returns plan IDs, price in atomic USDC (6 decimals), duration, event allowance, filters, account request/connection limits and sales_enabled. -1 credits means Unlimited. Trading alone needs no data package. If sales are enabled, choose a plan and call get_payment_instructions with its exact id to create an unpaid invoice. Output parameters: - `base_url` (string): Public API origin for optional HTTP access. - `currency` (string): Payment currency: native Solana USDC, 6 decimals. - `network` (string): Payment network, Solana mainnet. - `payment_protocol` (string): PumpView invoice protocol, no Coinbase dependency. - `plans` (array): Currently configured prepaid data packages and exact prices. - `sales_enabled` (boolean): Whether new data-package invoices can currently be created. - `unit` (string): How delivered events and empty queries consume credits. ### `get_invoice_status` (~142 tokens) Read one of your account's existing invoices without creating or paying another. Bearer key required; no package or data credits needed. Returns payer, recipient, exact atomic USDC amount, memo, expires (Unix seconds) and paid. paid=false means not yet settled by PumpView, not proof of no on-chain payment. If your wallet already broadcast, use confirm_invoice_payment with that signature. Do not pay again while waiting. Missing or another account's invoice returns 404. Input parameters: - `invoice_id` (string, required): Invoice id returned by get_payment_instructions for this API-key account. Not a swap id or Solana transaction signature. Output parameters: - `amount` (integer): Exact invoice amount in USDC atomic units; divide by 10^decimals for USDC. - `created` (integer): Invoice creation time as Unix seconds. - `decimals` (integer): USDC decimals: 6. - `expires` (integer): Invoice expiry as Unix seconds; do not pay an expired invoice. - `id` (string): Invoice ID for prepare_invoice_payment, get_invoice_status and confirm_invoice_payment. - `memo` (string): Exact payment memo binding the transaction to this invoice. - `mint` (string): Native Solana USDC mint address required for this payment. - `network` (string): Required payment network: solana-mainnet. - `paid` (boolean): Whether the invoice has been settled. A newly created invoice is unpaid. - `payer` (string): Linked Solana wallet that must authorize payment. - `payment_protocol` (string): Payment workflow identifier: pumpview-invoice-v1. - `plan` (string): Selected plan ID from the current public plan catalog. - `recipient` (string): Public payment recipient to verify before signing. ### `prepare_invoice_payment` (~203 tokens) Prepare an unsigned USDC payment for an existing unpaid, unexpired invoice. Bearer key required; no package or data credits needed. Returns a base64 legacy Solana transaction and last_valid_block_height. Review it against get_invoice_status: payer, recipient, mint, amount and pumpview: memo. Your authorized wallet signs and broadcasts locally, using USDC plus SOL for network fees and possible token-account rent. PumpView never receives the private key. This tool does not sign, submit or activate the package. Next call confirm_invoice_payment with the wallet's broadcast signature. A 409 means expired/paid invoice. On blockhash expiry, check the old signature before preparing a replacement for the same invoice; never pay twice. Input parameters: - `invoice_id` (string, required): Invoice id returned by get_payment_instructions for this API-key account. Not a swap id or Solana transaction signature. Output parameters: - `last_valid_block_height` (integer): Block-height expiry of this transaction. Invoice expiry must also be respected. After expiry, check the prior signature before preparing another payment. - `transaction_base64` (string): Unsigned legacy Solana transaction. Review payer, recipient, exact USDC amount and invoice memo before local wallet signing and broadcast. Never submit through submit_swap. ### `confirm_invoice_payment` (~223 tokens) Verify an already-broadcast invoice payment and activate the purchased data package. Bearer key for the invoice owner required; no data credits consumed. Reads Solana at finalized and validates payer, recipient, USDC amount, memo and payment window. It never broadcasts a payment. Returns paid=true and invoice_id on settlement. Repeating the same invoice/signature is safe and never grants access twice. 409 may mean payment not finalized: retry this confirmation with backoff, not the payment. 400 means transaction mismatch; 404 means missing/foreign invoice; 503 means RPC unavailable. After success, use get_access_status, then get_recent_trades or get_stream_connection. Input parameters: - `invoice_id` (string, required): Invoice id returned by get_payment_instructions for this API-key account. Not a swap id or Solana transaction signature. - `signature` (string, required): Base58 Solana transaction signature returned by your wallet after broadcasting this invoice payment. Not a signed transaction, wallet-login signature or private key. Output parameters: - `invoice_id` (string): Settled invoice ID. Reconfirming the same signature never grants access twice. - `paid` (boolean): True once matching finalized payment is verified and the package has been activated. ### `get_stream_connection` (~137 tokens) Get WSS setup for continuous live trades instead of polling get_recent_trades. Requires a Bearer key with an active eligible data grant/budget; 402 means access is unavailable. Returns url, an Authorization header template, first_message JSON and cursor-resume instructions. This lookup consumes no data credits and opens no background connection. Your runtime must connect and insert its own key; all keys share one concurrent WSS connection per account. Delivered events consume data credits/budget under the plan. Persist the last cursor to resume; an expired cursor requires a fresh snapshot and gap handling. Output parameters: - `authentication` (string): Handshake header template. Supply your own API key; the response never echoes the secret. - `first_message` (object): Initial JSON subscription message. Customize filters.mints/wallets and filters.after as documented. - `resume` (string): How to resume with the last received cursor. An expired cursor requires a fresh snapshot. - `url` (string): WSS endpoint to open in the caller runtime. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fun-pumpview-trading/api#diagnostics ## Score history - 2026-10-17: 64 - 2026-10-16: 63 ## Common questions ### What is the PumpView — Solana Trading & Live Data MCP server? PumpView — Solana Trading & Live Data is an MCP server listed in the public MCP registry as fun.pumpview/trading. Solana swaps with local signing, confirmed receipts, trading volume and filtered live trade data. This page covers its hosted endpoint (https://api.pumpview.fun/mcp/). ### Is the PumpView — Solana Trading & Live Data MCP server safe to use? PumpView — Solana Trading & Live Data scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the PumpView — Solana Trading & Live Data MCP server expose? PumpView — Solana Trading & Live Data exposes 14 tools: get_onboarding_instructions, get_trading_config, build_swap, get_trading_usage, submit_swap, and 9 more. Their descriptions and schemas cost roughly 2,674 tokens of context every time the server is loaded. ### Does the PumpView — Solana Trading & Live Data MCP server require authentication? No. We connected to PumpView — Solana Trading & Live Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the PumpView — Solana Trading & Live Data MCP server still maintained? PumpView — Solana Trading & Live Data is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://api.pumpview.fun/mcp/ - Authorisation metadata: https://api.pumpview.fun/.well-known/oauth-protected-resource/mcp - Repository: https://github.com/grinchdev/pumpview-agent-kits - Website: https://pumpview.fun/solana-trading-api - Changelog RSS feed: https://verifymcp.io/servers/fun-pumpview-trading/api.xml - Changelog JSON feed: https://verifymcp.io/servers/fun-pumpview-trading/api.json - HTML version of this page: https://verifymcp.io/servers/fun-pumpview-trading/api