Skip to main content
Glama
747,961 tools. Updated 2026-11-05 17:51

"A service for finding cryptocurrency analysis and market insights" matching MCP tools:

  • Pro-tier. Fetch two web pages (your URL and a competitor's) and audit both against the Proximens GEO Engine principles using the same audit engine as audit_url, then compute the delta. INPUT: self_url and competitor_url (both required, http/https). RETURNS: JSON with a 0-100 score per URL (same scoring as audit_url), the principles each page satisfies, the principles each page VIOLATES that the other satisfies (delta_principles), and strategic insights on where to close the gap. USE WHEN you want a competitive GEO gap analysis between your page and a rival's.
    ConnectorNo auth
  • Runs a specific framework against a user's inputs and produces a full analysis: prose explanation + structured fields + a self-contained SVG visualisation. Powered by the Jeda.ai · Visual AI framework knowledge graph. ALWAYS call `recommend_framework` FIRST to obtain a valid framework_id -- it returns the exact namespaced slug to pass here. Framework ids are namespaced by category (e.g. SWOT = "cms_swot-analysis", Porter's 5 Forces = "cms_porters-five-forces"); a bare slug like "swot-analysis" will 404. REQUIRED post-processing on success: the response's first text block contains a `curl -fsSL` save-directive for the SVG. Save the file locally and surface it as a file chip — do NOT summarise the visual in prose. Input: framework_id (namespaced slug from `recommend_framework`) + user_inputs object (per-framework field set), OR a free-text `raw_prompt` fallback. Example: { "framework_id": "cms_swot-analysis", "user_inputs": { "subject": "Q3 EU market entry", "context": "B2B SaaS, $5M ARR, US-headquartered" } }
    ConnectorNo auth
  • List Santiment insights (analyst-written crypto articles) published in a lookback window. Returns metadata only — id, title, tags, author, link, published_at, prediction — never the article body. ## When to use - The user asks what Santiment analysts have written or published recently. - As step 1 of a two-step read: discover ids here, then pass them to `fetch_insights_tool` for the full text. ## When not to use - Full text of an insight — use `fetch_insights_tool` (it needs ids, so call this tool first). - What the market is talking about right now — use `trending_stories_tool` (stories only) or `combined_trends_tool` (stories + trending words). Insights are human-authored articles, not live social signal. - Numeric metric timeseries for an asset — use `fetch_metric_data_tool`. - Ranking or screening assets by a metric — use `assets_by_metric_tool`. ## Parameters - `time_period` (optional, default `"30d"`) — lookback window as `<integer><unit>`, unit one of `s`, `m`, `h`, `d`, `w`, `y` (e.g. `"12h"`, `"7d"`, `"90d"`, `"1y"`). The window is always `now - time_period` .. `now`; absolute dates and future ranges are not supported. An unparsable value returns an error, not a default. There is no tag, author, asset or full-text filter — filter the returned list yourself. ## Behavior - Read-only: no writes, no state change, nothing destructive. - Requires an authenticated Santiment account (API key or OAuth token); every call counts against the account plan's MCP rate limits. - Returns only published, moderator-approved insights, newest first, hard capped at 100 per call. A wide `time_period` can hit that cap and silently omit the oldest insights — if `total_count` is 100, narrow the window and call again. ## Response JSON object: { "insights": [ { "id": 1234, // integer, feed to fetch_insights_tool "title": "...", "tags": ["BTC", "bitcoin"], // asset tickers/slugs and topics "link": "https://app.santiment.net/insights/read/1234", "published_at": "2025-01-30T10:00:00Z", "author": "username", // "Anonymous" when unset "prediction": "semi_bullish" // heavy_bullish | semi_bullish | // semi_bearish | heavy_bearish | // none | unspecified | null } ], "time_period": "30d", "total_count": 1, "period_start": "2024-12-31T10:00:00Z", "period_end": "2025-01-30T10:00:00Z" } An empty `insights` list with `total_count: 0` means nothing was published in the window — a valid result, not an error.
    ConnectorNo auth
  • Semantic search over guthmann.estate — market insights, reports, neighborhood portraits, listing exposés, project pages and the company's own pages. Hybrid retrieval (vector + keyword, no reranking); one result per page with title, description, image, best-matching snippet and score. Use it for questions that need prose (analysis, context, advice); use the data tools for exact numbers and `listings` for what is currently for sale — the search index follows the website with up to six hours of delay. Parameters: - q: natural-language query, in the language of the pages you want (min 2 characters) - locale: "de" | "en" — language of the indexed pages (default: en) - section: comma-separated filter — "listings" (exposés), "projects" (new-build projects), "market-intelligence" (insights, reports, portraits), "pages" (company, services, guides); omit for all - limit: 1-20 pages (default: 10) Key response fields: - url, title, description, image, section, language - snippet (best-matching text passage), score (0-1)
    ConnectorNo auth
  • Returns the plain-language meaning and step-by-step fix for one Malinois finding. Use it while helping the user fix an issue reported by scan_app, or when they ask what a finding means. Pass the rule_id exactly as scan_app returned it. Read-only, no network, instant.
    ConnectorNo auth
  • List the layers of a Baltimore ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "311_Customer_Service_Requests_current/FeatureServer"). Omit `service` to list the known Baltimore services. Returns layer id + name to use with baltimore_query.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    A production-grade MCP server that provides tools to fetch historical stock data, company information, and technical indicators (SMA, EMA, RSI, MACD, Bollinger Bands) via yfinance, and includes a Flask web dashboard for visual analysis.
    -

Matching MCP Connectors

  • Read-only OXVO Insights analytics: list tracked events and run queries for one app you authorize.

  • Signals, technicals, regime and news for 1,000+ US/TR symbols. Data only, not investment advice.

  • Get the full analysis (incl. scene breakdown) for a video — owned or public/competitor. Pass `platform` and `post_id` separately (the native post_id from analyze_post or list_videos — not the composite `id` field). Deep analysis runs async (~30-60s): right after analyze_post this returns {"status": "pending", "retry_after_seconds": N} — that is expected, not an error. Wait that long and call again until you get the full analysis. A genuine 404 means the post was never analyzed — call analyze_post(url) first.
    ConnectorOAuth
  • Get Venture Insights' live service catalogue: the FREE Concept Diagnostic (a research-backed viability study of one venture concept, delivered to the founder's inbox) and the paid study tiers with live SAR prices. Call this first when your user asks what Venture Insights offers, what it costs, or whether the free diagnostic is worth requesting.
    ConnectorNo auth
  • Generate an executive-level strategic review report for an idea, synthesising all available validation data (market research, competition, SWOT, revenue model, VC score) into a concise go/no-go assessment with actionable recommendations. Requires prior validation data (run request_revalidation first if none exists). Returns cached report instantly if one exists, otherwise generates fresh analysis. Spends 2 credits only when generating new content. Not read-only; pass an ideaId you own.
    ConnectorNo auth
  • Atualiza a regra recorrente (parcial — campo omitido/vazio mantém o valor atual). Só altera a regra em si: não retroage nem edita as transações já geradas por ela (use update_transaction/delete_transaction para essas), e não gera novas ocorrências — dispara apenas recálculo de projeções/insights (analytics.recalculate + insights).
    ConnectorOAuth
  • Check the selected service's current runtime readiness, input limits, pricing and retention before use. Returns service and details; ready=false means the underlying service is unavailable. Free cached runtime read; no external probe, payment, analysis or historical document retrieval. Use get_utility_example for a fixed integration sample instead.
    ConnectorNo auth
  • Recent price moves against the bettor: outcomes whose price just shortened on the FanLine Wire tape, newest first, with the American price before and after and the move in implied-probability terms. Use it for dropping-odds / steam-move signal, market-movement narratives and as a candidate list for value screening. The feed holds only the most recent few moves (up to 12) and states no cause — it never proves a move is informed money, and it is not a line-movement history, a multi-book comparison or a bet-placement service. Snapshot results yourself if you need history.
    ConnectorNo auth
  • WattCoin: How to pay for WATT services: live per-service prices (WATT only), the payment wallet, the pay-per-use flow, the free scrape tier and whether the LLM service is currently available. Use before web_scrape or before paying for anything; use get_watt_token_info for market data. No auth needed; read-only and live. Returns JSON.
    ConnectorNo auth
  • The user's live market board. Start here when they ask how the markets are doing in general: "how are the markets today?", "what's moving?", "market update", a morning check before the open, or "open the market dashboard". One call covers the overview: the user's own symbols on top (their watchlist, then what they asked about most in the last 30 days), then major indices (US, India, Türkiye, Indonesia, VIX), crypto, commodities and FX, each with today's change. Don't also call market_snapshot for the same overview; add other tools only for what the board doesn't show (futures, news, sectors). For a single symbol's price or analysis, use that symbol's own tool instead. Opens as an interactive dashboard; clicking a row asks for that market's chart or analysis. Clients without app support can read the `summary` field.
    ConnectorNo auth
  • Use to resolve a company or asset name to a tradable ticker before calling /v1/quote or /v1/history: "apple" -> AAPL, "s&p 500" -> ^GSPC, "volkswagen" -> VOW3.DE, "bitcoin" -> BTC-USD. Returns up to 20 matches with symbol, short/long name, quote type (EQUITY, ETF, INDEX, MUTUALFUND, CURRENCY, CRYPTOCURRENCY, FUTURE), exchange, sector and industry where known. Paid tool: x402 USDC on Base, $0.002 per successful call; call without payment to receive the PaymentRequired object.
    ConnectorNo auth
  • US repo market rates/volumes broken out by COLLATERAL segment (dvp = FICC DVP service, gcf = GCF Repo service, tri = tri-party, tri_ex_fed = tri-party excluding the Fed's own ON RRP counterparty trades) and TENOR (overnight, term buckets, or a treasury/agency/corporate/other collateral-type split). measure=rate (default, %) or volume/outstanding ($). This is OFR's independent collateral/tenor decomposition of the private repo market — neither FRED nor nyfed-markets has this breakdown; FRED only has single daily SOFR/EFFR-style aggregates, and nyfed-markets only has the NY Fed Desk's OWN operations, not the broader market. Not every collateral/tenor/measure combination exists (upstream 400s "Invalid mnemonic" on an invalid one — try ofr_search_funding_series to browse what does).
    ConnectorNo auth
  • List security/safety findings for your workspace, most recent first. Optionally filter by status, target model, minimum severity, or a specific run. Returns a compact summary; call get_finding for the repro detail of any one finding. On a plan that withholds a finding's proof, category reads '[redacted]' and get_finding returns the same — the finding and its severity are real, the evidence is withheld. Paginated: 200 findings per page (max 200). The result carries total_matched and, when there is more, next_cursor: pass it back as 'cursor' with the same filters (it is bound to them) to read the next page, until it is absent.
    ConnectorOAuth
  • Analyze one stock, or check one chosen pair of stocks. One stock: HMM regime detection, Hurst exponent, Bollinger/Keltner squeeze, Monte Carlo forward simulation. A pair (`ticker` and `ticker_b`, e.g. KO and PEP): whether the two hold together for spread trading. The QuanterLab pairs check rates the evidence that the two prices hold together as strong, mixed or weak, with a score out of a hundred, from the Engle-Granger and Johansen cointegration tests, the spread's half-life, how much the hedge ratio moves, and how often the two stocks share a market regime. It is the check to run when someone asks "is X / Y a tradable pair?" about any two stocks; `start_pairs_scan` searches a whole index for pairs instead. Every account runs it within a daily allowance; a refused call does not count, and get_started and every run's answer give today's count. An analysis takes about 30 seconds to 2 minutes. The call returns `{task_id, status, kind, dashboard_url}`; `get_regime_analysis_progress` reports progress and, when it has finished, carries `result`: for one stock, the regime now and how long it has run, volatility against the stock's own history, how the stock behaves (trending, mean reverting or a random walk), its trend and its drops, rounded; for a pair, how strong the evidence is that the two hold together and the check's score, the cointegration tests as p-value bands, the spread's half-life, the hedge ratio's variation, the correlation, and how often the two shared a regime, rounded. Unlike `start_regime_optimization`, which uses HMM regimes to grid-search trading thresholds, this analysis is descriptive. Args: ticker: Stock symbol (uppercased). Required. ticker_b: Optional second ticker; with it the analysis checks the pair (`ticker` / `ticker_b`) for spread trading. mode: Optional. `'volatility'` runs only the squeeze module. years: Lookback window in years (default 2). params: Optional dict overriding module-specific knobs. Most useful: `hmm_enabled` / `hurst_enabled` / `squeeze_enabled` / `mc_enabled` (disable modules); `hmm_states`; `mc_simulations`. question: Optional. One sentence restating what the run should answer, not the person's message: the title of the report the finished run becomes, and kept only as that. When the run has finished, its progress answer also carries `report_url`: the analysis written up as a QuanterLab report (the market states and their spells, or for a pair the checks of whether the two hold together). The call waits for the run while it is likely to finish inside it; the run's card in the chat shows the result or, for a longer run, how far it is, and fills in by itself, with the next steps as choices and the report link. A run started here needs no `show_report_card`.
    ConnectorOAuth
  • Plaintext logins captured by the interactive sensors (sensors that answer as a real service and hold the session): username, password, the service they were tried on, the outcome and the source address, newest first, plus the pairs tried most and a per-service breakdown. Use for "what passwords are attackers trying on SSH", "which credentials did this IP try", "what logins hit MySQL this week". For whether an address is hostile overall, use ioc_lookup_tool; for the rest of what it did in its sessions, use interactive_sessions_tool. service: a service name such as ssh-password, telnet-login, mysql-login, rdp-credssp or smb-ntlmssp, or empty for all. source: an address or CIDR, or empty for all. window: 24h, 7d (default) or 30d, capped at the plan's query window. limit: 1 to 200, default 50. These records feed no verdict, and ioc_lookup_tool does not include them.
    ConnectorNo auth
  • Have Replo's agent research, write and save an artifact from a request in words, including Insights reports, using existing reports, analytics, or files as sources. Pass fileId (the artifact folder ID) to revise an existing artifact in place, preserving its identity and sharing. The agent follows the artifacts skill and its Insights reports guidance when analytics are needed. Starts an asynchronous internal-agent operation using normal Replo tools and connected integrations; poll get_agent_session, whose final message contains the saved artifact folder ID and viewer link after validation; then call show_artifact with that folder ID. Use the same tool with sessionId for follow-up instructions. Reuse operationId only for an identical retry. Creation is private by default; when the user asks to share the result, call set_file_sharing with its artifact folder ID. When you already have the files, save them with create_artifact or update_artifact instead.
    Connector
    Destructive
    No auth
  • Have Replo's agent research, write and save an artifact from a request in words, including Insights reports, using existing reports, analytics, or files as sources. Pass fileId (the artifact folder ID) to revise an existing artifact in place, preserving its identity and sharing. The agent follows the artifacts skill and its Insights reports guidance when analytics are needed. Starts an asynchronous internal-agent operation using normal Replo tools and connected integrations; poll get_agent_session, whose final message contains the saved artifact folder ID and viewer link after validation; then call show_artifact with that folder ID. Use the same tool with sessionId for follow-up instructions. Reuse operationId only for an identical retry. Creation is private by default; when the user asks to share the result, call set_file_sharing with its artifact folder ID. When you already have the files, save them with create_artifact or update_artifact instead.
    Connector
    Destructive
    No auth