Skip to main content
Glama
511,934 tools. Updated 2026-09-04 15:15

"A server for analyzing meme coins and providing buy signals" matching MCP tools:

  • Scan Zora for trending coins and trading signals. Returns top movers with market cap, volume, 24h change, and BUY/SELL/STRONG_BUY signals.
    Connector
  • Purpose: Query research signals with dynamic filters (symbol / interval / action / score / confidence). Triggers (casual questions too): "should I buy / sell X?", "살까 말까?", "good entry?", "what's the signal for BTC / AAPL / 삼성전자?", "is X bullish or bearish?", "any buy signals right now?". Returns a research signal + score (NOT an order or advice — always surface the disclaimer). Pair with get_latest_decisions to show what the system did. When to call: drilling into a specific signal slice; symbol-by-symbol scanning; any "should I trade X?" question about a live symbol. Prerequisites: market://{market_id}/signals/summary recommended for global view. Next steps: get_signal_detail, get_role_analysis. Caveats: When `symbol`/`coin` is omitted, the whole market is scanned in one consolidated query (2 newest rows per symbol, newest-first scan cap per interval). Args: market_id: Market ID (crypto, kr_stock, us_stock; aliases coin/kr/us accepted) symbol: Asset identifier to query (preferred; optional — targets a specific symbol DB) coin: Legacy alias of symbol (kept for backward compatibility) interval: Timeframe filter (15m, 30m, 240m, 1d, combined) action_filter: Action filter (buy, sell, hold) min_score: Minimum signal score threshold min_confidence: Minimum confidence threshold limit: Max results (default 500) hours_back: Only signals within last N hours (default 24) Disclaimer: Information only, not investment advice. Signals are research output, not orders.
    Connector
  • READ-ONLY wallet summary for a SOMA app user: their SOMA Coins balance plus a summary of coins expiring within the next 30 days. Requires a wallet token that only the human can generate inside the SOMA mobile app (Wallet tab → 'Share balance with your AI') — ask them for it; tokens expire after ~10 minutes. This tool can never claim, redeem, spend, or move coins (there are deliberately no claim/redeem tools over MCP). Returns { error: 'invalid_or_expired_token' } for a bad or stale token — ask the user to generate a fresh one in the app.
    Connector
  • Get details for one CoinPaprika tag (a category such as 'defi' or 'stablecoin'): its id, name, description, coin_counter, ico_counter, and optionally the coins and ICOs grouped under it. Use for 'what coins are in the defi tag', 'show the stablecoin category', 'tokens tagged ai'. To list every tag or find a tagId first use getTags. Read-only. Params: tagId (required) is a tag id from getTags such as 'defi'; additionalFields (optional, default none) is a comma-separated list of extra sections, valid values 'coins' and 'icos' (example 'coins,icos'). An unknown tagId returns an error. No API key required.
    Connector
  • Get Lenny Zeltser's expert CTI writing guidelines. Topics include tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance), handoffs (cross-server routing), methodology (the three subsections), fields (per-field guidance), and CTI-specific topics: attribution (full Six Signals prose), confidence (ICD-203 ladder), pyramid_of_pain, six_signals (signals table only), and anti_patterns. The general writing topics (tone/words/structure/executive_summary) now defer to `get_security_writing_guidelines` for the canonical Five Elements rules; CTI-specific content lives in the other topics. Pair the 'fields' topic with field_id for single-field guidance. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.
    Connector
  • [TRUTH ANCHOR] Batch canonical prices for several coins in one call. coins = comma-separated symbols, e.g. 'BTC,ETH,SOL' (max 50). Returns {prices:{SYM:price}, missing:[...], source, age_secs}.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Three independent sensors read pre-price Bitcoin flows every 30s and reject almost everything. When they converge, a call is emitted with evidence — and the public rejection funnel proves how often it stays silent. Auditable in one call. Free tier; Pro 50 USD/month or 0.01 USD/query via x402.

  • MCP server for meme generation, template search, caption rendering, and AI meme creation.

  • Crypto market-data lookups (CoinGecko-sourced pricing and market data), paid per call in USDC/USDm directly from the caller's own wallet via the x402 protocol — no Abstraxn account needed. Pick one `action`: - search ($0.001): fuzzy-search coins by name/symbol. Requires `q`. Call this first to resolve a coin id before using price_feed or historical_data, both of which need an id (e.g. "bitcoin"), not a ticker. - price_feed ($0.001): current price (and optionally 24h change / market cap) for one or more coins. Requires `ids` (comma-separated coin ids). Optional `currencies` (comma-separated fiat codes, default "usd"), `include_24h` (default true), `include_mcap` (default false). - market_data ($0.002): coins ranked by market cap (or another order) — use for "top N coins" / market overview questions. Optional `currency` (default "usd"), `category`, `order` (default "market_cap_desc"), `limit` (1-250, default 100), `page` (default 1). - historical_data ($0.003): historical price/market cap/volume series for one coin. Requires `id`. Optional `currency` (default "usd"), `days` (lookback window or "max", default 30), `interval` (e.g. "daily"). - trending ($0.001): currently trending coins by search interest. No extra parameters. - token_prices ($0.005): DEX-derived prices for up to 200 tokens in one call. Requires `tokens`, an array of `{chain, token_address}` objects. Prices above are indicative — the exact charge for a given call is always whatever the live payment challenge specifies for that request. The first call (no `paymentPayload`) returns `paymentRequired`; retry with the same arguments plus `paymentPayload` to complete payment and get the real result.
    Connector
  • Purchase a service listing from the Lightning-native agent marketplace. Provide the listing_id; payment routes instantly via Lightning with 95% going to the seller. Use to hire other agents' services, buy data feeds, signals, or analysis. Returns purchase confirmation and the seller's delivery content. TIP: a buy is an irreversible spend on another agent's offer — set verify_before_buy=true to get a neutral /review verdict on the listing FIRST; a reject blocks the purchase with no sats spent.
    Connector
  • Which coins and schemes this gateway accepts for payment. Free. Ways to pay any paid tool: a prepaid KAS session (open_session — simplest, no per-call step); per-call in any listed coin (pay the offer a 402 returns, then pay_per_call); or, where the experimental 'kaspa-channel' scheme is offered, a covenant payment channel that settles per-call vouchers on L1 with no custodian (see channel_config). Coins may include Kaspa, Pearl, BTC, LTC, DOGE, BCH, DASH, and EVM assets (ETC, ETH, USDC, USDT).
    Connector
  • Scan the S&P 500 universe and return filtered signals. Pushes filters + pagination to the server (GET /signals): the REST API applies min_conviction/direction/sector and returns one page of size limit, so the LLM payload stays tight regardless of how broad the universe is. Use this to discover high-conviction opportunities across the market rather than analyzing tickers one by one. The scan covers all S&P 500 tickers simultaneously, surfacing cross-ticker convergence patterns that per-ticker analysis would miss. Freshness: scan runs on a scheduled cadence (typically several times per day). Results carry scan_generated_at, and a `data_freshness` sentence only when the scheduled run did not land. Pagination: results are deterministically ordered server-side. When more results remain, next_cursor is a non-null opaque token — pass it back as cursor= to fetch the next page (scan_universe(..., cursor=next_cursor)). next_cursor is null on the last page. Args: min_conviction: Minimum conviction score (0–10). Recommended: 6.0+ for actionable signals, 7.5+ for high-conviction only. direction: Filter by signal verdict — "BUY", "WAIT", "AVOID", or "WATCH". Case-insensitive. sector: Filter by sector name (partial match, case-insensitive). Examples: "Technology", "Health Care", "Financials". limit: Page size — max results per call (default 20, max 100). cursor: Opaque pagination cursor from a previous call's next_cursor. Omit for the first page. Returns a dict with count, scan_generated_at, results list, next_cursor (null when no further pages), and disclaimer embedded in the payload.
    Connector
  • Real-time crypto quotes: the largest coins, each with a display name. The feed carries 4,771 coins in alphabetical order, which is far more than one response can hold — so this returns `limit` of them ordered by market capitalisation, largest first, and the response states how many were left out. Pass `symbols` for specific coins, or call get_crypto_quote for a single one. Read `note` before summarising: it says how many coins the slice covers out of how many exist, so a "top coins" answer is not mistaken for the whole market. `volume` on a crypto row is the source venue's own figure and is not a common unit across coins — some rows count coins, others quote-currency turnover. It does not rank the market and coins cannot be compared on it. Args: symbols: Comma-separated coins (optional; overrides the ranked slice) limit: How many ranked coins to return (optional)
    Connector
  • List all available coins with id, name, symbol and rank. Use to discover coins or map a name to an id. Does NOT include prices; for prices use getTickers or getTickersById. Read-only; limit caps the number of coins returned. No API key required.
    Connector
  • List all CoinPaprika tags (categories such as 'defi', 'stablecoin', 'memecoin', 'ai') used to group coins, returned as a list with each tag's id, name, coin_counter and ico_counter. Use for 'what crypto categories exist', 'list market sectors', or to find a tagId before calling getTagById. For the coins inside one tag use getTagById. Read-only. Params: additionalFields (optional, default none) is a comma-separated list of extra sections per tag, valid values 'coins' and 'icos' (example 'coins,icos'; omit for just summaries); limit (optional, default 50, max 250) caps how many tags return. No API key required.
    Connector
  • Free with a feed_handle from crypto_feed_subscribe: every published advice change since your cursor, across all covered coins — new signals, classification flips (previous_classification vs classification), status/score/entry-zone changes. Send back next_cursor each time; for the full advice behind a signal_id call get_crypto_signal (paid).
    Connector
  • Compact replay summary for analysis. Returns replay metadata (totals, passed/failed/skipped counts) + one row per step with status, action, duration, diff scores, and a short error excerpt. Always small — call this first when analyzing a replay, then use flow_replay_step for full per-step detail.
    Connector
  • Crypto market-data lookups (CoinGecko-sourced pricing and market data), paid per call in USDC/USDm directly from the caller's own wallet via the x402 protocol — no Abstraxn account needed. Pick one `action`: - search ($0.001): fuzzy-search coins by name/symbol. Requires `q`. Call this first to resolve a coin id before using price_feed or historical_data, both of which need an id (e.g. "bitcoin"), not a ticker. - price_feed ($0.001): current price (and optionally 24h change / market cap) for one or more coins. Requires `ids` (comma-separated coin ids). Optional `currencies` (comma-separated fiat codes, default "usd"), `include_24h` (default true), `include_mcap` (default false). - market_data ($0.002): coins ranked by market cap (or another order) — use for "top N coins" / market overview questions. Optional `currency` (default "usd"), `category`, `order` (default "market_cap_desc"), `limit` (1-250, default 100), `page` (default 1). - historical_data ($0.003): historical price/market cap/volume series for one coin. Requires `id`. Optional `currency` (default "usd"), `days` (lookback window or "max", default 30), `interval` (e.g. "daily"). - trending ($0.001): currently trending coins by search interest. No extra parameters. - token_prices ($0.005): DEX-derived prices for up to 200 tokens in one call. Requires `tokens`, an array of `{chain, token_address}` objects. Prices above are indicative — the exact charge for a given call is always whatever the live payment challenge specifies for that request. The first call (no `paymentPayload`) returns `paymentRequired`; retry with the same arguments plus `paymentPayload` to complete payment and get the real result.
    Connector
  • Requires owner auth (OAuth or begin_agent_link). Without it refuse and start connect — do not pretend the order went through. Propose or place an order in an allowlisted store using AgentPay coins. Cursor/Claude Code with MCP elicitation: server shows a button «Оформить · N коинов» — do NOT ask «да/нет» in chat; the button is the owner's payment approval for orders above confirmAbove. Without elicitation the server falls back to awaiting_confirmation + cabinet/Telegram HITL. If testMode, spend only gray test coins in test stores. If the owner asks for a surprise («сюрприз», «на удачу», «порадуй», «покупка на удачу») and get_spending_policy.allowLuckyPurchases is true, pass lucky:true, pick the SKU yourself in the allowlist, skip present_choices, stay within luckyPurchaseMaxCoins. If clarifyHint required present_choices/ask_one and lucky is not set, you MUST pass choiceSetId (chosen) or clarification:{confirmed:true,answerSummary}. Otherwise server returns NEED_CLARIFICATION — do not grab the first SKU. If the owner enabled review on merchant site, this does NOT debit: status awaiting_review — you MUST show photos and product links (url/trackedUrl) and tell the owner to confirm in the AgentPay cabinet. On ANY failure the JSON has recovery: tell the owner userMessageRu / sayToUserRu and open recovery.openUrl (VPN) plus recovery.openUrlRu (без VPN). Never change limits, freeze, autotopup, allowlist (exception: set_test_mode). If review is off, server still enforces allowlist, catalog prices, limits, HITL, freeze, clarify gate. Response includes paid + payment.status. Never send userId. Never ask for a bank card. Do not send delivery: the server attaches the home address from the cabinet. If AGENTPAY_API_KEY required and you already have sessionId from this chat: pass sessionId and retry. Never begin_agent_link again. Never ask the owner to edit connector settings or reconnect. Never web-search.
    Connector
  • Rug pull probability for one token: a 0-100 score where HIGHER MEANS MORE DANGEROUS, a verdict label, and the individual signals that drove it. This is the opposite direction from get_token_scan's safety score. Call this tool ONLY when the user explicitly asks for a rug probability or rug likelihood; every general "is this safe" or "should I buy" question goes to get_token_scan instead. Not for the evidence behind the number — it names the signals but does not list the wallets; for who is behind the risk call get_wallet_links, get_dev_tracker or get_launch_bundles. Arguments: address and chain; one API unit on any chain.
    Connector
  • Purpose: Cross-market lead-lag relationships and decoupling events. Shows how markets influence each other (correlations) and when they diverge (decoupling, e.g. BTC up while stocks down). Triggers (casual questions too): "do crypto and stocks move together?", "코인이랑 주식이 따로 노나?", "any decoupling lately?", "시장끼리 상관관계 어때?", "is BTC tracking the Nasdaq?". When to call: when analyzing macro regime changes or divergent signals. Prerequisites: none. Next steps: get_macro_influence_map for the static causal hypotheses. Caveats: correlation data may be empty until enough regime changes accumulate. Args: source_market: Optional source market filter target_market: Optional target market filter Disclaimer: Information only, not investment advice.
    Connector
  • Get daily narrative/sector history — top crypto market sectors ranked by market cap change %, strength, and token count over up to 90 days — Daily historical narrative strength per market sector (e.g. DeFi, Layer 2, AI, Meme Coins) from CoinGecko Categories. One row per day per sector: market cap change %, strength score (0-100), token count in sector, daily rank, and top tokens. Filter by ?sector= for a single sector trend. Useful for identifying which narratives are accelerating or fading. DB-backed, 5-min cache. Powered by narrative_daily table (365d retention, permanent monthly archive). — Use this for daily historical data; use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.
    Connector