A
licenseA
qualityD
maintenanceReal-time radar for Solana memecoins, Pump.fun launches, and KOL trades.
8
4
MIT
three.ws pump.fun MCP
Server Details
Free pump.fun and Solana token discovery and on-chain analysis tools, by three.ws.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 58 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- nirholas/three.ws
- GitHub Stars
- 23
TDQS
B3.2/5.0
Scored across 21 tools
Disambiguation3/5
Several tools occupy adjacent territory: get_coin_intel and get_oracle_conviction both serve as high-signal trade reads, and the three pumpfun_*_claims tools can be hard to distinguish at a glance. The descriptions are detailed enough to separate most tools, but an agent could easily fetch the wrong intelligence snapshot or claims variant.
Naming Consistency2/5
Naming conventions are mixed across several prefix families: get_*, pumpfun_*, sns_*, social_*, and kol_leaderboard. There is also an inconsistent camelCase outlier in sns_reverseLookup next to snake_case names elsewhere, making the surface feel patchwork rather than systematic.
Tool Count3/5
At 21 tools, the set sits in the heavy range and includes some near-redundant claim/intel tools that could be consolidated. However, the domain is broad—on-chain analytics, social signals, SNS resolution, and launch utilities—so the count is not unreasonable for the apparent scope.
Completeness4/5
The tool surface covers token discovery, holder/trade analysis, bonding curve and AMM quotes, sentiment, claims monitoring, and launch metadata preparation—a strong analytical workflow. Minor gaps exist, such as no actual token launch/swap execution step and no direct token price ticker, but agents can work around these with the provided quote and metadata tools.
Available Tools
21 toolsget_bonding_curveBonding CurveRead-onlyInspect
Bonding curve analysis: real reserves, virtual reserves, and graduation progress (on-chain). Pre-graduation only: these reserves come from the pump program bonding-curve account, not from a PumpSwap pool. Pump renamed the quote-side fields on-chain (real_sol_reserves -> real_quote_reserves, virtual_sol_reserves -> virtual_quote_reserves) once a non-SOL quote asset became possible; the response keys below keep their original names and are still denominated in SOL, because the curve quote_mint is the SOL default on every coin created to date. A v3 buy that empties the curve completes it and buys the rest through a synthetic migration, priced on the reserves the PumpSwap pool will open with, so a large final buy is not capped at realTokenReserves. Once complete=true the curve is retired and pricing moves to the PumpSwap pool, so use pumpfun_quote_swap from that point on. Use this to read graduation progress or the curve spot price of a coin that has not graduated yet.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mint | Yes | ||
| network | No | mainnet |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| mint | Yes | |
| network | Yes | |
| complete | Yes | true once the curve has graduated |
| solReserves | Yes | Real quote reserves in SOL (4-decimal string). On-chain field: real_quote_reserves. |
| tokenReserves | Yes | Real token reserves (raw base units) |
| graduationPercent | Yes | 0–100 graduation progress |
| virtualSolReserves | Yes | Virtual quote reserves (lamports). On-chain field: virtual_quote_reserves (u64). Spot price = virtual_quote_reserves / virtual_token_reserves. Distinct from the identically-named PumpSwap Pool.virtual_quote_reserves (an i128), which applies only after graduation. |
| virtualTokenReserves | Yes | Virtual token reserves (raw base units) |
get_coin_intelCoin IntelRead-onlyInspect
Full Coin Intelligence snapshot for a pump.fun mint. Returns every signal the engine recorded during the observation window: bundle vs organic verdict, bubblemaps-style cluster connectivity, smart-money presence (with wallet labels and win-rates), dev behaviour, category/classification, news-meme detection with the matching headline, risk flags, and a 0-100 quality score. Also returns the outcome if the coin is old enough to be labeled (graduated/rugged/ATH multiple). This is the single highest-signal read for a trade decision. Call this before entering any position.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mint | Yes | Solana mint address (base58). | |
| network | No | mainnet |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| mint | No | |
| name | No | |
| found | Yes | |
| oracle | No | Fused Oracle conviction score (null if the Oracle engine has not yet scored this coin). Call get_oracle_conviction for the full read including who's-in roster and narrative. |
| symbol | No | |
| outcome | No | Labeled outcome if available (graduated, ath_multiple, etc). |
| verdict | No | |
| category | No | |
| dev_sold | No | |
| oracle_url | No | Oracle deep-link for the coin — opens the Oracle war-room drawer directly. |
| risk_flags | No | |
| dev_buy_sol | No | |
| bundle_score | No | 0–1, coordinated-launch likelihood. |
| is_news_meme | No | |
| news_headline | No | |
| organic_score | No | 0–1, organic-demand likelihood. |
| quality_score | No | 0–100 composite quality. |
| unique_buyers | No | |
| smart_money_count | No | Proven wallets (score≥65) in this coin. |
| smart_money_score | No | |
| smart_money_notable | No | |
| bubblemap_connectivity | No | 0–1 wallet-cluster share. null = enrichment not yet run. |
get_new_tokensNew TokensRead-onlyInspect
Most recently launched pump.fun tokens. Use this to catch launches in their first minutes; for the largest coins by market cap call get_trending_tokens instead.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
get_oracle_convictionOracle ConvictionARead-onlyInspect
Oracle conviction score for a pump.fun mint: the fused 0-100 score the Oracle engine produces by combining four intelligence pillars: pedigree (who bought it), structure (organic vs bundle, holder concentration, bubblemaps connectivity), narrative (category, meme virality, news hook), and momentum (timing, velocity). Returns the tier (prime ≥86 / strong ≥72 / lean ≥54 / watch ≥36 / avoid), the per-pillar breakdown, the natural-language reasons that drove the score, the full "who's in" trader roster with reputation labels and win-rates, and the narrative read (category, virality, tags). Call this when you need the highest-confidence trade signal; it synthesises everything get_coin_intel exposes into one actionable score. Pairs with get_coin_intel for raw signals.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mint | Yes | Solana mint address (base58). | |
| network | No | mainnet |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| url | No | Oracle deep-link URL for this coin. |
| mint | No | |
| name | No | |
| found | Yes | |
| symbol | No | |
| outcome | No | Labeled outcome if available. |
| whos_in | No | Classified trader roster — every wallet that touched this coin, annotated with their reputation. |
| narrative | No | Narrative classification for the coin. |
| conviction | No | Fused conviction verdict. null if the Oracle has not yet scored this coin. |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds substantial behavioral context: the four intelligence pillars (pedigree, structure, narrative, momentum), the tier thresholds, and the comprehensive return payload. It does not disclose potential rate limits or caching, but goes well beyond annotation basics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is moderately long but every sentence adds value: purpose, components, return details, usage guidance, and sibling pairing. It front-loads the core function and follows with specifics. It could be slightly tighter, but it is well-organized and free of filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given an output schema exists, the description doesn't need to enumerate return fields, but it still details the tier ranges, pillar breakdown, trader roster, and narrative read. It covers complexity well and tells the agent exactly what to expect, making it complete enough for selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%: mint is described, network is not. The description names the mint implicitly ('for a pump.fun mint') but does not explain the network parameter or its options. Since network has an enum and default, the schema carries some meaning, but the description does not compensate for the missing parameter description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb—'get'—and resource—'pump.fun mint'—and clearly states the tool's output: a fused 0-100 conviction score, tier, per-pillar breakdown, reasons, roster, and narrative. It distinguishes from sibling get_coin_intel by positioning itself as a synthesis of raw signals into one actionable score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use: 'Call this when you need the highest-confidence trade signal.' It also provides an alternative/raw-signal counterpart: 'Pairs with get_coin_intel for raw signals,' implying when-not to use it (when you just need raw data). This meets the bar for explicit context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_token_detailsToken DetailsRead-onlyInspect
Full details for a specific pump.fun token by mint address. Use this when you already have a mint and need its metadata, market cap, and curve status; for holder concentration call get_token_holders, for recent fills call get_token_trades.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mint | Yes |
get_token_holdersToken HoldersRead-onlyInspect
Top holders of a token with concentration analysis (on-chain). Use this to check whether a few wallets control the supply before buying; for price and volume call get_token_details instead.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mint | Yes | ||
| limit | No | ||
| network | No | mainnet |
get_token_tradesToken TradesRead-onlyInspect
Recent buy/sell history for a token. Use this to read recent buy and sell flow on one coin; to see only large trades as they land, call pumpfun_watch_whales instead.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mint | Yes | ||
| limit | No |
get_trending_tokensTrending TokensRead-onlyInspect
Top pump.fun tokens by market cap. Use this to scan the largest coins on pump.fun right now; for fresh launches call get_new_tokens, for coins that left the curve call get_graduated_tokens.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
kol_leaderboardKOL LeaderboardRead-onlyInspect
Top KOL traders ranked by P&L for a given time window. Returns wallet, pnlUsd, winRate, trades, rank. Use this to find which trader wallets are worth following; to see whether they hold a given coin, call get_coin_intel or get_token_holders.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| window | No | 7d |
pumpfun_bot_statusIndexer StatusRead-onlyInspect
Returns the configuration and health status of the pump.fun indexer backend. Always available; does not require PUMPFUN_BOT_URL. Use this first when search_tokens, get_graduated_tokens, get_king_of_the_hill, or get_creator_profile fail or are missing, to see whether the indexer is configured and healthy.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| error | No | Failure reason when healthy is false |
| healthy | Yes | true when the indexer answered the health ping |
| message | No | Human-readable note when the indexer is unconfigured |
| latencyMs | No | Round-trip ms of the health ping (configured backends only) |
| configured | Yes | true when PUMPFUN_BOT_URL is set on the server |
pumpfun_first_claimsFirst Creator Fee ClaimsRead-onlyInspect
First-ever pump.fun creator fee claims in a time window: a cash-out signal. Returns creators who have never claimed before, with creator wallet, mint, lamports, and timestamp. Use this to spot creators cashing out for the first time across all coins; for one creator's history call pumpfun_list_claims.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| sinceMinutes | No | How far back to look for new claimers (minutes) |
pumpfun_list_claimsList Creator Fee ClaimsRead-onlyInspect
List recent pump.fun fee-claim events for a creator wallet (on-chain, no indexer needed). Returns signature, mint, lamports, and Unix timestamp for each claim. Creator fees from the v3 curve and v2 pool trades wait on the curve and pool until a sweep_creator_fee moves them to the creator vault, so a claim covers only what was swept (usually in the same transaction) and fees still waiting appear in no claim yet. Use this to audit how much a creator has already cashed out; for only the claims inside a recent window call pumpfun_watch_claims.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| creator | Yes | Creator wallet address (base58) | |
| network | No | mainnet |
pumpfun_quote_swapSwap Quote (Read-Only)Read-onlyInspect
Read-only price quote for a pump.fun AMM (PumpSwap) swap. No signing or tx sending. One of inputMint/outputMint must be wSOL (So11111111111111111111111111111111111111112). Only GRADUATED coins have an AMM pool; for a coin still on its bonding curve use get_bonding_curve instead. Pricing runs on the pool effective quote reserves (quote vault balance + pool.virtual_quote_reserves, a SIGNED i128 that is commonly negative because PumpSwap v2 trades keep waiting protocol and creator fees in the vault and subtract them there); the base side is the raw base vault balance. Returns amountOut, priceImpactBps, route, expiresAtMs, plus the reserves the quote was computed from so the number can be reproduced. Use this to size a trade on a graduated coin, or to measure its pool depth, before executing anywhere.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| network | No | mainnet | |
| amountIn | Yes | Input amount in raw base units (lamports for SOL). | |
| inputMint | Yes | Input token mint (base58). | |
| outputMint | Yes | Output token mint (base58). | |
| slippageBps | No | Slippage tolerance in basis points (default 100 = 1%). |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| route | Yes | AMM pool address the quote routes through (base58) |
| amountOut | Yes | Expected output amount in raw base units |
| expiresAtMs | Yes | Epoch ms after which the quote is stale |
| base_reserve | No | Raw base vault balance. Unchanged by the virtual-reserve rollout. |
| quote_reserve | No | Raw quote vault balance, before virtual reserves are added. Includes protocol and creator fees waiting for a sweep, so it overstates liquidity on its own; price on effective_quote_reserve. |
| priceImpactBps | Yes | Price impact in basis points |
| virtual_quote_reserves | No | Pool.virtual_quote_reserves, a SIGNED i128 serialized as a decimal string. Positive values add depth held outside the vault; negative values remove fees that sit in the vault waiting for a sweep (common since the PumpSwap v2 trades). Parse it as a signed integer: never unsigned, never clamped to 0, never absolute-valued. |
| effective_quote_reserve | No | quote_reserve + virtual_quote_reserves (signed addition). This is what the quote is priced against; the program guarantees it is never negative. |
pumpfun_upload_metadataUpload Coin MetadataIdempotentInspect
Upload coin metadata (name, symbol, description, image) to IPFS and get back a pump.fun-ready metadata URI. Call this before launching a coin: pass the returned uri to the launch-agent endpoint or the studio launch flow. Requires a valid bearer token (API key). Image may be a public HTTPS URL or a base64 data URI (max 10 MB). The returned uri is a permanent ipfs:// link; the call is idempotent for the same content.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Coin name (1–32 chars). | |
| symbol | Yes | Ticker symbol (1–10 chars, no $). | |
| No | Twitter/X handle or URL (optional). | ||
| website | No | Website URL (optional). | |
| telegram | No | Telegram URL (optional). | |
| image_url | Yes | Image for the coin icon. Public HTTPS URL or base64 data URI (data:image/png;base64,…). Square image, at least 400×400 px, under 5 MB. | |
| description | Yes | Coin description (max 500 chars). |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| cid | Yes | IPFS CID of the metadata JSON. |
| uri | Yes | ipfs:// URI ready for the pump.fun launch-agent `uri` field. |
| provider | No | IPFS provider used. |
| image_cid | No | IPFS CID of the uploaded image. |
pumpfun_vanity_mintVanity Mint KeypairRead-onlyInspect
Generate a Solana keypair whose address ends/starts with a vanity pattern. Returns publicKey + secretKey (base58). Caller must save the secret key immediately; it is never stored. Hard timeout: 60 s. Use this before launching a coin when its mint address should carry a recognizable prefix or suffix.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| prefix | No | Desired address prefix (case-insensitive by default) | |
| suffix | No | Desired address suffix (case-insensitive by default) | |
| maxAttempts | No | ||
| caseSensitive | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| ms | Yes | Wall-clock grind time in milliseconds |
| attempts | Yes | Keypairs ground before the match |
| publicKey | Yes | Matched Solana address (base58) |
| secretKey | Yes | Secret key (base58) — caller is sole custodian |
pumpfun_watch_claimsWatch Creator Fee ClaimsRead-onlyInspect
Return all pump.fun fee-claim events for a creator wallet within a look-back window (durationMs). Use this for batch collection after a delay; for a creator's full recent claim history call pumpfun_list_claims.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| creator | Yes | Creator wallet address (base58) | |
| network | No | mainnet | |
| durationMs | No | Look-back window in ms (default 300000 = 5 min, max 1800000) |
pumpfun_watch_whalesWatch Whale TradesRead-onlyInspect
Collect whale trades on a pump.fun token for a short window (max 10 s). Returns all trades whose USD value meets minUsd. Use this to see who is moving size on a coin right now; for the full recent tape call get_token_trades.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mint | Yes | SPL mint pubkey (base58) | |
| minUsd | No | Minimum trade value in USD (default 5000) | |
| durationMs | No | Collection window in ms (default 5000, max 10000) |
sns_resolveResolve .sol DomainRead-onlyIdempotentInspect
Resolve a .sol Solana Name Service domain to its owner wallet address. Use this when a wallet is named by its .sol domain and you need the address; for the reverse direction call sns_reverseLookup.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | .sol domain name, e.g. "bonfida.sol" |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| name | Yes | The .sol domain that was resolved |
| address | Yes | Owner wallet address (base58) |
sns_reverseLookupReverse .sol LookupRead-onlyIdempotentInspect
Reverse-lookup a Solana wallet address to its primary .sol domain name. Use this to label a raw wallet address with its human-readable .sol name; to go from name to address call sns_resolve.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Base58 Solana wallet address |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| name | Yes | Primary .sol domain for the address |
| address | Yes | The wallet address that was looked up |
social_x_post_impactX Post Price ImpactRead-onlyInspect
Correlate an X (Twitter) post to a memecoin price impact. Fetches post metadata via oEmbed (no API key) and computes price delta from the pump.fun bonding curve in a ±windowMin window around the post. Use this to measure how one X post moved a coin that is still on its bonding curve (pricing is virtual_quote_reserves / virtual_token_reserves); a graduated coin has no curve, so the call fails rather than returning a zero price.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mint | Yes | Solana token mint address (base58) | |
| network | No | mainnet | |
| postUrl | Yes | X post URL (e.g. https://x.com/user/status/123) | |
| windowMin | No | ±window in minutes around the post time |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
pumpfun_quote_swap3 fields changed- changed
Output schema / properties / effective_quote_reserve / descriptionPrevious value: -"quote_reserve + virtual_quote_reserves. This is what the quote is priced against."New value: +"quote_reserve + virtual_quote_reserves (signed addition). This is what the quote is priced against; the program guarantees it is never negative." - changed
Output schema / properties / quote_reserve / descriptionPrevious value: -"Raw quote vault balance, before virtual reserves are added."New value: +"Raw quote vault balance, before virtual reserves are added. Includes protocol and creator fees waiting for a sweep, so it overstates liquidity on its own; price on effective_quote_reserve." - changed
Output schema / properties / virtual_quote_reserves / descriptionPrevious value: -"Pool.virtual_quote_reserves. Quote-side liquidity the pool carries outside its vault. 0 on non-launchpad pools."New value: +"Pool.virtual_quote_reserves, a SIGNED i128 serialized as a decimal string. Positive values add depth held outside the vault; negative values remove fees that sit in the vault waiting for a sweep (common since the PumpSwap v2 trades). Parse it as a signed integer: never unsigned, never clamped to 0, never absolute-valued."
2 tool updates
- Added
get_new_tokens - Added
get_trending_tokens
2 tool updates
- Changed
get_bonding_curve2 fields changed- changed
Output schema / properties / solReserves / descriptionPrevious value: -"Real SOL reserves in SOL (4-decimal string)"New value: +"Real quote reserves in SOL (4-decimal string). On-chain field: real_quote_reserves." - changed
Output schema / properties / virtualSolReserves / descriptionPrevious value: -"Virtual SOL reserves (lamports)"New value: +"Virtual quote reserves (lamports). On-chain field: virtual_quote_reserves (u64). Spot price = virtual_quote_reserves / virtual_token_reserves. Distinct from the identically-named PumpSwap Pool.virtual_quote_reserves (an i128), which applies only after graduation."
- Changed
pumpfun_quote_swap4 fields changed- added
Output schema / properties / base_reserveAdded value: +{ + "description": "Raw base vault balance. Unchanged by the virtual-reserve rollout.", + "type": "string" +} - added
Output schema / properties / effective_quote_reserveAdded value: +{ + "description": "quote_reserve + virtual_quote_reserves. This is what the quote is priced against.", + "type": "string" +} - added
Output schema / properties / quote_reserveAdded value: +{ + "description": "Raw quote vault balance, before virtual reserves are added.", + "type": "string" +} - added
Output schema / properties / virtual_quote_reservesAdded value: +{ + "description": "Pool.virtual_quote_reserves. Quote-side liquidity the pool carries outside its vault. 0 on non-launchpad pools.", + "type": "string" +}
1 tool update
- Removed
kol_radar
3 tool updates
- Added
get_coin_intel - Added
get_oracle_conviction - Added
pumpfun_upload_metadata
7 tool updates
- Removed
get_creator_profile - Removed
get_graduated_tokens - Removed
get_king_of_the_hill - Removed
get_new_tokens - Removed
get_trending_tokens - Added
pumpfun_bot_status - Removed
search_tokens
22 tool updates
- First observed
get_bonding_curve - First observed
get_creator_profile - First observed
get_graduated_tokens - First observed
get_king_of_the_hill - First observed
get_new_tokens - First observed
get_token_details - First observed
get_token_holders - First observed
get_token_trades - First observed
get_trending_tokens - First observed
kol_leaderboard - First observed
kol_radar - First observed
pumpfun_first_claims - First observed
pumpfun_list_claims - First observed
pumpfun_quote_swap - First observed
pumpfun_vanity_mint - First observed
pumpfun_watch_claims - First observed
pumpfun_watch_whales - First observed
search_tokens - First observed
sns_resolve - First observed
sns_reverseLookup - First observed
social_cashtag_sentiment - First observed
social_x_post_impact
Related MCP Connectors
Solana token/wallet rug-risk scoring. Free scan; $2 SOL unlocks full wallet report. No signup.
AI price forecasts, whale flows, market sentiment and prediction signals. 18 tools free, no account.
Solana on-chain intelligence — token scans, wallet profiling, bundle detection, 19 MCP tools.
Solana meme-coin trust scores, rug-risk flags, and wallet analytics from SolRadar.
Related MCP Servers
- FlicenseAqualityBmaintenanceEnables read-only on-chain analysis to spot trending and new memecoin pools, evaluate rug risk, and surface early buyer wallets across Solana, Base, and Ethereum.5-
- AlicenseAqualityAmaintenanceRug pull risk scores and on-chain forensics for memecoins on Solana, Ethereum, Base and Robinhood Chain - launch-bundle detection, funding-origin tracing, deployer history, insider networks and whale flow. 15 read-only tools.1517 npmMIT
- AlicenseNot gradedqualityDmaintenanceSolana on-chain intelligence API — token scans, wallet PnL, bundle detection, fresh wallets, dev profiling. MCP server for Claude, Cursor & AI agents. Live PumpFun/Raydium streams1MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.
social_cashtag_sentimentCashtag SentimentRead-onlyIdempotent Inspect
Score social-post sentiment for a cashtag using a deterministic lexicon. Returns score (-1..1), positive/negative/neutral percentages, and example posts. Use this to score posts you have already collected; it fetches nothing itself, so pass the posts in.
Output Schema