PumpView — Solana Trading & Live Data MCP server
fun.pumpview/tradingpumpview.funstreamable-httpv1.2.3Scanned
Solana swaps with local signing, confirmed receipts, trading volume and filtered live trade data.
20 tools: 1 can delete or cancel things, 2 do something that can't be undone, 3 change things and 14 only read.
- Reads private data · 0
- Reads text others write · 6
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 2 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the PumpView — Solana Trading & Live Data MCP server can do
The PumpView — Solana Trading & Live Data MCP server is published by pumpview.fun, a domain the MCP Registry verified. It has 20 tools. It can delete or cancel things (1 tool: submit_swap), do things that cannot be undone, such as sending, paying or publishing (prepare_invoice_payment and confirm_invoice_payment) and create or change data (3 tools: build_swap, get_recent_trades and get_payment_instructions). 14 tools only read.
6 tools bring in text other people can write (build_swap, submit_swap, get_swap_status and 3 more).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.2.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
20 tools
Deletes or cancels 1Claude Code: deny
submit_swapBroadcast the wallet-approved, signed build through Kolibrio.Reads text others writeNo findings
Why it is in this group
- The name "submit_swap" says "submit": a word for a change.
- The description's first verb is "broadcast": a word for sending, and what is sent cannot be taken back.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: false
Can't be undone 2Claude Code: ask
confirm_invoice_paymentVerify an already-broadcast invoice payment and activate the purchased data package.Reads text others writeNo findings
Why it is in this group
- The name "confirm_invoice_payment" says "payment": a word that usually means money moves, which cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 means processing (landing, or unseen for under 30 s): retry this confirmation with backoff, not the payment. 422 means the signature is still not on Solana: check it is the one your wallet broadcast, not the prepared transaction's; if it was never sent or its blockhash expired, prepare a new transaction. 410 means not found and invoice expired. 400 means mismatch or failed transaction; 404 missing/foreign invoice; 429 retry later (Retry-After); 503 RPC unavailable. After success, use get_access_status, then get_recent_trades or get_stream_connection.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: false
prepare_invoice_paymentPrepare an unsigned USDC payment for an existing unpaid, unexpired invoice.Reads text others write1 finding
Why it is in this group
- The name "prepare_invoice_payment" says "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "prepare_invoice_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "prepare_invoice_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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:<id> 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. Wallets may add compute-budget or guard instructions, changing the signature. Next call confirm_invoice_payment with the signature the wallet broadcast. A 409 means expired/paid invoice; 422 means the payer wallet lacks the USDC. On blockhash expiry, check the old signature before preparing a replacement for the same invoice; never pay twice.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
Changes things 3Claude Code: ask
build_swapBuild and simulate an unsigned ExactIn swap, without spending funds.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: false
get_payment_instructionsCreate a new unpaid USDC invoice for a live-data package; this spends no funds.No findings
Why it is in this group
- The name "get_payment_instructions" says "get": a word for reading.
- The description's first verb is "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
get_recent_tradesRead filtered market swap summaries from PumpView's supported SOL-pair feed.Reads text others write1 finding
Why it is in this group
- The name "get_recent_trades" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "get_recent_trades" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_recent_trades" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
Only reads 14Show 14 read-only tools
get_access_statusInspect the authenticated account's live-data grants, rate limit and feed health.No findings
Why it is in this group
- The name "get_access_status" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_hot_tokensRead the current Hot Tokens snapshot, sorted by descending buy score.No findings
Why it is in this group
- The name "get_hot_tokens" says "get": a word for reading.
Description, as the server wrote it Read the current Hot Tokens snapshot, sorted by descending buy score. This is a filtered scanner ranking. Entries are current observations, not historical Hot Tokens trigger events. Requires a Bearer key. Uses the account request limit and consumes no trade credits. Check source_connected and snapshot_at before using the data. An unavailable snapshot returns an error.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_invoice_statusRead one of your account's existing invoices without creating or paying another.No findings
Why it is in this group
- The name "get_invoice_status" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_onboarding_instructionsGet API-key setup and integration instructions before your first PumpView call.No findings
Why it is in this group
- The name "get_onboarding_instructions" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_pump_migrationsRead finalized, canonical Pump.fun to PumpSwap pool migrations.No findings
Why it is in this group
- The name "get_pump_migrations" says "get": a word for reading.
Description, as the server wrote it Read finalized, canonical Pump.fun to PumpSwap pool migrations. Returns only verified migrations with the source bonding curve, exact destination pool, base and quote mints, transaction signature and slot. Requires a Bearer key and consumes no trade credits. Use get_research_coverage for observed collector coverage and freshness.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_research_coverageCheck retained signal history by strategy and the migration collector status.No findings
Why it is in this group
- The name "get_research_coverage" says "get": a word for reading.
Description, as the server wrote it Check retained signal history by strategy and the migration collector status. Returns the first and last retained database timestamps and record count for each platform strategy, journal start and retention, and the latest migration scan time, slot and known gap. Coverage summaries are cached for one minute. Requires a Bearer key and consumes no trade credits.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_research_eventsRead the ordered journal of newly captured research events.No findings
Why it is in this group
- The name "get_research_events" says "get": a word for reading.
Description, as the server wrote it Read the ordered journal of newly captured research events. Includes sampled Hot Tokens rankings, platform strategy firings, revisions, retractions and finalized Pump.fun to PumpSwap migrations. Requires a Bearer key and consumes no trade credits. Start without after for retained history, then persist next_after with the same filters even on empty pages. On cursor expiry, record the gap and restart without after. For point-in-time analysis use the conservative availability_confirmed_at timestamp once present. Earlier legacy signals remain available through get_signals and get_signal.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_signalRead the stored firing data for one retained PumpView strategy signal.No findings
Why it is in this group
- The name "get_signal" says "get": a word for reading.
Description, as the server wrote it Read the stored firing data for one retained PumpView strategy signal. Returns the original score, price, market cap and available firing-time features. Missing, deleted and out-of-scope IDs return the same error. Requires a Bearer key and consumes no trade credits.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_signalsPage through recorded PumpView strategy signals with optional filters.No findings
Why it is in this group
- The name "get_signals" says "get": a word for reading.
Description, as the server wrote it Page through recorded PumpView strategy signals with optional filters. Rows are ordered by descending signal ID. Use recorded_at for the database firing time. The retained history can have gaps and contains only platform signals. Historical feature definitions can vary. Requires a Bearer key and consumes no trade credits. Use get_signal for a specific record.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_stream_connectionGet WSS setup for continuous live trades instead of polling get_recent_trades.No findings
Why it is in this group
- The name "get_stream_connection" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_swap_statusCheck an existing account swap after submission, including after a timeout.Reads text others writeNo findings
Why it is in this group
- The name "get_swap_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
- readOnlyHint: true
get_trading_configRead the current server's swap policy before choosing build_swap parameters.No findings
Why it is in this group
- The name "get_trading_config" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_trading_usageRead all-time executed volume for the authenticated account and each API key.No findings
Why it is in this group
- The name "get_trading_usage" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
list_data_plansList current data packages and prices before buying a live-data subscription.No findings
Why it is in this group
- The name "list_data_plans" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 2 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.pumpview.fun/mcp/: tools/list returned 20 tools to an anonymous client, including submit_swap (destructive), prepare_invoice_payment (irreversible), confirm_invoice_payment (irreversible), build_swap (write), get_recent_trades (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "get_recent_trades" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_recent_trades" says "get": a word for reading.
The server marks "prepare_invoice_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "prepare_invoice_payment" says "payment": a word that usually means money moves, which cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools6 added, 2 changed.+6 added~2 changedView diff
- Added:get_hot_tokensOnly reads
- Added:get_pump_migrationsOnly reads
- Added:get_research_coverageOnly reads
- Added:get_research_eventsOnly reads
- Added:get_signalOnly reads
- Added:get_signalsOnly reads
- Changed:confirm_invoice_paymentCan't be undonedescription
- Changed:prepare_invoice_paymentCan't be undonedescription
Tools1 changed.~1 changedView diff
- Changed:confirm_invoice_paymentCan't be undonedescription
Install
Pinned to version 1.2.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http trading https://api.pumpview.fun/mcp/ --header 'Authorization: <your-authorization>'claude mcp add --transport http trading https://api.pumpview.fun/mcp/ --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__trading__get_onboarding_instructions",
"mcp__trading__get_trading_config",
"mcp__trading__get_trading_usage",
"mcp__trading__get_swap_status",
"mcp__trading__get_hot_tokens",
"mcp__trading__get_signals",
"mcp__trading__get_signal",
"mcp__trading__get_research_events",
"mcp__trading__get_pump_migrations",
"mcp__trading__get_research_coverage",
"mcp__trading__get_access_status",
"mcp__trading__list_data_plans",
"mcp__trading__get_invoice_status",
"mcp__trading__get_stream_connection"
],
"ask": [
"mcp__trading__build_swap",
"mcp__trading__get_recent_trades",
"mcp__trading__get_payment_instructions",
"mcp__trading__prepare_invoice_payment",
"mcp__trading__confirm_invoice_payment"
],
"deny": [
"mcp__trading__submit_swap"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trading. Review it before you use it.
Capability tags behind 6 rules
- mcp__trading__build_swap untrusted-input
- mcp__trading__submit_swap untrusted-input
- mcp__trading__get_swap_status untrusted-input
- mcp__trading__get_recent_trades untrusted-input
- mcp__trading__prepare_invoice_payment untrusted-input
- mcp__trading__confirm_invoice_payment untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/fun.pumpview/trading/verify?hash=96ad7e65d7c798d2a778fe171bafdaccd7e6414b0899a23664eb56ed30f7c105" | jq -e '.changed == false'Pinned hash 96ad7e65d7c7, from Nov 11, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/fun.pumpview/trading/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/fun.pumpview/trading)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.
PumpView — Solana Trading & Live Data MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the PumpView — Solana Trading & Live Data MCP server safe?
- No scan can promise that. What its definitions show: 20 tools, 6 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the PumpView — Solana Trading & Live Data MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: submit_swap.
Can the PumpView — Solana Trading & Live Data MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: prepare_invoice_payment and confirm_invoice_payment.
What tools does the PumpView — Solana Trading & Live Data MCP server have?
- 20 tools: 1 destructive, 2 irreversible, 3 write, 14 read. submit_swap, prepare_invoice_payment, confirm_invoice_payment, build_swap, get_recent_trades, get_payment_instructions, get_onboarding_instructions, get_trading_config and 12 more.
Does the PumpView — Solana Trading & Live Data MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the PumpView — Solana Trading & Live Data MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the PumpView — Solana Trading & Live Data MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.