Skip to main content
Glama
742,443 tools. Updated 2026-11-04 15:25

"A website for discovering new pump.fun launches" matching MCP tools:

  • Live feed of pump.fun launches from the last 24h with creator context: who deployed each one, how many they launched before, whether they bought their own bonding curve. Poll with ?since= for only what is new. This history cannot be reconstructed afterwards. Facts and flags only, never advice. Free tier: 3 calls per hour per IP, shared with the website; unlimited access costs $0.030 per call over x402 at /v1/launches
    ConnectorNo auth
  • Recently launched Solana tokens grouped by launchpad such as pump.fun. Highest-risk category. Use for 'what launched recently' and 'new pump.fun coins'; pair with `get_smart_money_pulse` (`fresh_launch`) to see which launches whales are buying.
    ConnectorNo auth
  • Register a new Fractera user and start the deployment of their server in one atomic call. Use this AFTER you have collected the user's email (entered twice for typo protection), server IP, and root password. Creates the User row (or reuses an existing one with the same email), creates a free Subscription, creates a ServerToken, wipes any previous installation on the target server, and launches bootstrap. The deploy is IP-first (phase-1): the server comes up on plain HTTP at http://<IP>:3002 in 8-14 minutes; it does NOT get a domain or HTTPS cert here (that is an optional later step inside the workspace). Returns session_id (for a single on-demand check_status read — do not poll) and server_token (so the user can recover via retry_deploy if anything breaks). Call this AT MOST ONCE per conversation.
    Connector
    Destructive
    No auth
  • Register a new Fractera user and start the deployment of their server in one atomic call. Use this AFTER you have collected the user's email (entered twice for typo protection), server IP, and root password. Creates the User row (or reuses an existing one with the same email), creates a free Subscription, creates a ServerToken, wipes any previous installation on the target server, and launches bootstrap. The deploy is IP-first (phase-1): the server comes up on plain HTTP at http://<IP>:3002 in 8-14 minutes; it does NOT get a domain or HTTPS cert here (that is an optional later step inside the workspace). Returns session_id (for a single on-demand check_status read — do not poll) and server_token (so the user can recover via retry_deploy if anything breaks). Call this AT MOST ONCE per conversation.
    Connector
    Destructive
    No auth
  • Launch a full overnight-grade research report on a local business: an autonomous research crew maps the competitive landscape, reads the business's and rivals' web presence, and delivers a long-form graded report with structured findings and an action list. ASYNC: this tool returns a slug immediately; the report takes roughly 10-20 minutes. Poll check_report_status, then fetch with get_report_result. Price: $9.99, charged when the report launches; if the report fails, the charge is refunded automatically. Each call starts a NEW report — do not retry a call that already returned a slug.
    ConnectorNo auth
  • Begin setting up Canarics (AI voice agents + call analysis) for a company that has no account yet. Returns a claim URL: ALWAYS show that URL to the person immediately and verbatim — it is useless sitting in your context; they open it, sign in, verify their phone by SMS and accept the terms; the trial then provisions itself with a demo AI agent generated from the company website. Keep the returned intentToken to follow progress with check_signup_status. All other Canarics tools need the API key that check_signup_status hands you after the claim. GROUNDING: companyName and website must come from what the person actually told you in this conversation — if either is missing, ask for it; never guess, never use placeholders like "New Company" or example.com. Never ask for or collect a password or any credentials in chat: identity is verified entirely on the claim link.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Reviewed Singapore new-launch floor plans, area details and buyer rules. Trial.

  • Launches MCP — wraps Launch Library 2 API (ll.thespacedevs.com)

  • Adds, replaces, or removes hosted images on an existing Carryo website without replacing its HTML. Reusing a path replaces that image without consuming another image slot; new paths are subject to the website image allowance. Returns hosted-image metadata and URLs. New paths appear in the page when referenced by its HTML. Pass attached images through imageFiles. For one attachment, assets needs only its relative website path; Carryo matches the attachment automatically. For multiple attachments, use fileIndex (0 for the first imageFiles entry). Do not invent file IDs or ask for a public URL when attachment upload is available. Known fileId references and fetchable HTTP(S) sourceUrl imports also work. Carryo imports and hosts its own copy. Base64 image bytes and data URLs are unsupported.
    Connector
    Destructive
    No auth
  • Adds, replaces, or removes hosted images on an existing Carryo website without replacing its HTML. Reusing a path replaces that image without consuming another image slot; new paths are subject to the website image allowance. Returns hosted-image metadata and URLs. New paths appear in the page when referenced by its HTML. Pass attached images through imageFiles. For one attachment, assets needs only its relative website path; Carryo matches the attachment automatically. For multiple attachments, use fileIndex (0 for the first imageFiles entry). Do not invent file IDs or ask for a public URL when attachment upload is available. Known fileId references and fetchable HTTP(S) sourceUrl imports also work. Carryo imports and hosts its own copy. Base64 image bytes and data URLs are unsupported.
    Connector
    Destructive
    No auth
  • Live pump.fun heartbeat: trades/min, launches, graduations, graduation rate, hottest tokens in the last 15 min. Computed from our own live recording of every pump.fun bonding-curve trade. Use it to decide whether the launch market is hot or dead before scanning individual tokens. When to use: For the market right now; for trends over days use pump_history. Price: free. Errors: returns isError with a message for invalid input or an upstream failure (not charged).
    ConnectorNo auth
  • LAUNCH COHORT / BACKTEST of MANY token launches at once — every token whose FIRST trade falls inside a launch window (for example all pump.fun launches of a day), one row per launch: supply, price and FDV at launch, sniper and first-minutes buying, and the outcome over the following hours — peak price (the highest hourly average), peak multiple, hours to peak, last price, drawdown, whether it still traded. output=summary returns the cohort's distribution instead (quartiles, share that reached 2x / 5x / 10x, share still trading) in one row. Answers "backtest yesterday's pump.fun launches", "what share of new tokens did 10x within 24 hours", "snipers and first-5-minute buying across launches", "survival of launches after 6 hours", "which of today's launches had the most buyers in the first minute". For one token or a given list of up to 50 (`addresses`) use token_launch_stats (launch snapshot), for one token's wallets early_buyers; to list what just launched with its current price use new_tokens. Prefer this tool over writing SQL for launch cohorts and launch backtests. Works for rare and newly-launched tokens. COHORT: tokens on `blockchain` whose first trade is inside [after_time, before_time) and that had no USD-priced trade in the `lookback_days` (default 7) before the window. Narrow it with address_pattern, a LIKE pattern on the token address (`%pump` = pump.fun mints, `%bonk`, `%4444`), and/or protocol, the DEX of the first trade (pump, pumpfun, pump_amm, raydium_launchpad, pons_v2, fourmeme_v1, flap_v5, uniswap_v2 …). min_volume_usd (default 1000) drops launches with less USD volume over the horizon (so far, while it is still running) — most launches never trade $1,000; 0 keeps all. min_window_buyers keeps launches with at least that many buying wallets in the early window. Tokens that never had a USD-priced trade are left out (almost all of them are dust). WINDOW: at most 24 hours of launches per call; default = the 6 hours before before_time (default now). With output=summary and neither after_time nor before_time, the default window instead ends horizon_hours ago, so every launch in it has a finished horizon. A longer range keeps its NEWEST 24 hours — read Launch_Window_Start / Launch_Window_End and call again with before_time = Launch_Window_Start for the previous day. Trade history reaches back about 30 days, and a launch within lookback_days of its start cannot be told apart from an older token. Arc trades begin on 2026-09-16, so Arc launches within lookback_days of that day may be older tokens. ROW COLUMNS (output=tokens): Token_Address, Token_Symbol, Launch_Time (first trade), First_Protocol, First_Pool, First_Quote_Symbol, Supply_At_Launch, Launch_Price_Usd, Launch_Fdv_Usd; sniper window (first sniper_seconds): First_Block_Buyers, Sniper_Buyers, Sniper_Buy_Usd; early window (first window_seconds): Window_Trades, Window_Unpriced_Trades, Window_Buyers, Window_Sellers, Window_Buy_Usd, Window_Sell_Usd, Window_End_Price_Usd, Window_End_Fdv_Usd, Window_Complete; horizon (horizon_hours): Horizon_End, Horizon_Complete, Horizon_Volume_Usd, Peak_Price_Usd, Peak_Fdv_Usd, Peak_Multiple, Hours_To_Peak, Close_Price_Usd, Valuation_Price_Usd, Valuation_Fdv_Usd, Valuation_Multiple, Return_From_Window_End_Pct, Drawdown_From_Peak_Pct, Last_Active_Hour, Traded_In_Last_Horizon_Hour, Supply_Change_Pct; Launch_Window_Start, Launch_Window_End, Cursor. READING THE ROWS: Launch_Price_Usd is the first swap worth at least $1 — a smaller first fill prints a junk price, because on a bonding curve it buys at the cheapest point the token will ever have (a $0.02 swap taking a tenth of the supply implies a launch FDV of a few cents, and every multiple divides by it). Window_End_Price_Usd keeps a $0.01 floor. USD amounts value each swap at the lower of its two priced sides, and Window_Unpriced_Trades counts swaps without a price. First_Block_Buyers = buying wallets that traded at the exact timestamp of the first trade (on chains with several blocks per second this can include the next block). The HORIZON is measured on hourly bars that start with the launch hour: Horizon_End is the top of an hour, so it covers between horizon_hours − 1 and horizon_hours after the launch. Peak_Price_Usd = the highest hourly AVERAGE price inside it, each hour weighted by its volume, counting only hours that carried at least a thousandth of the launch's own volume: one odd or tiny swap can print an extreme price, high or low, and a near-empty hour can average one, so neither a bar's high nor its close nor a trickle hour can set the peak. Peak_Fdv_Usd is that price × the supply at launch. The peak can therefore sit BELOW Launch_Price_Usd — that one is the price of the first swap of at least $1 — and Peak_Multiple can be under 1 for a launch that only fell. The horizon end has TWO prices and they answer different questions. Close_Price_Usd = the last hourly close before Horizon_End (the last price if the token stopped trading earlier): the latest thing known, but ONE swap, so it can sit far above or below anything real. Valuation_Price_Usd = the average of the newest hour that carried at least a thousandth of the launch's volume — the same volume gate as the peak, so it is the last price at which real volume changed hands, and it can never exceed Peak_Price_Usd. Quote Close_Price_Usd as "the last print" and Valuation_Price_Usd as what the launch is worth. The two are far apart when the last swap was junk — and also when the launch STOPPED TRADING after its last real hour, which on a bonding curve leaves Valuation_Price_Usd above Launch_Price_Usd for a launch that is already dead: Traded_In_Last_Horizon_Hour and Drawdown_From_Peak_Pct say which of the two it is, and both read the close. Drawdown_From_Peak_Pct = Close_Price_Usd against Peak_Price_Usd, never above 0 and 0 for a launch that ends at or above its peak hour: it shows a collapse inside the peak hour and a launch that died after it, both of which a hour-against-hour comparison reads as 0. Hours_To_Peak = whole hours from the launch hour to the peak hour (0 = the launch hour; the earliest hour when several hours reach the peak). Peak_Multiple and Valuation_Multiple divide by Launch_Price_Usd; Return_From_Window_End_Pct = buying at Window_End_Price_Usd and selling at the end of the horizon. Valuation_Fdv_Usd, Valuation_Multiple and Return_From_Window_End_Pct are all measured at Valuation_Price_Usd, NOT at Close_Price_Usd — a single closing swap made launches report an 80-million FDV on a few thousand dollars of trading, and a close multiple above the peak multiple. Close_Price_Usd × the supply is therefore not Valuation_Fdv_Usd, and Valuation_Multiple cannot exceed Peak_Multiple any more. FDV = price × total supply — the supply at launch, except Valuation_Fdv_Usd, which uses the latest supply (NULL when the supply is unknown); Supply_Change_Pct below 0 = supply burned. Window_Complete = 0 or Horizon_Complete = 0 means that period has not elapsed yet and its figures are still moving. SUMMARY (output=summary): one row per group_by value (none = whole cohort, protocol = DEX of the first trade, hour = launch hour) with Tokens, Tokens_Horizon_Complete, totals, [p25, p50, p75, p90] arrays for window buy USD, window buyers, sniper buyers and buy USD, first-block buyers, launch FDV, peak FDV, peak and valuation multiples and return from window end, Hours_To_Peak_Q = [p50, p90], and Pct_Peak_2x / 5x / 10x, Pct_Valuation_At_Or_Above_Launch, Pct_Up_From_Window_End (both measured at Valuation_Price_Usd, like the row columns they come from), Pct_Down_90_From_Peak, Pct_Traded_In_Last_Horizon_Hour. NEITHER SHARE IS A PROFIT RATE: almost every launch has stopped trading by the end of a day-long horizon (on one measured cohort Pct_Traded_In_Last_Horizon_Hour was 4.1 %), so a launch counted at or above its launch price is usually one that went quiet holding the valuation of its last real hour, not one you could still have sold into. Quote Pct_Traded_In_Last_Horizon_Hour beside them, and Pct_Down_90_From_Peak — which reads the last close — for how far the latest prints have fallen. Outcome figures count only tokens whose horizon has elapsed (NULL or [] while none has): the default summary window already ended horizon_hours ago; an explicit window should end at least horizon_hours ago too. An empty result means no launch matched. PAGING: sort=newest (default, newest launch first) pages with cursor — pass the last row's Cursor and repeat every other argument, with after_time and before_time set to the Launch_Window_Start / Launch_Window_End of the first page. Other sorts (window_buy_usd, window_buyers, peak_multiple, horizon_volume) return only the top `limit` launches, with an empty Cursor. A call reads every launch of its window whatever the limit: for a distribution use output=summary instead of paging through thousands of rows. Follow launches up with token_launch_stats (one token, or a given list of up to 50 in `addresses`), early_buyers or token_trade_bars. Symbols longer than 32 characters are cut and end in `…` (spam tokens carry symbols of up to 32,000 characters).
    ConnectorOAuth
  • Changes the dates or the number of travelers of a trip you can edit (the same edits the Anywayr website allows; budget, title and preference edits are refused for now). Requires the version you last read with anywayr_get_trip; a stale version is refused rather than overwritten. Multi-city date changes and child-leg party changes require the Anywayr website. Does not share, invite or book. Effects: Writes a new trip version.
    Connector
    Destructive
    OAuth
  • Create a NEW Grigora website with AI from a description of what it should be. Grigora's AI website builder designs and writes the whole site from the prompt in the background (usually a few minutes). This uses the account's AI credits and counts toward its plan's website limit, so call it once per website the user actually asked for. The site is NOT published. Then: poll get_website_build_status(project_id) until status is "completed" (or "failed"); after that the new site's project_id works with every other tool (products, directory, blog, assets...), edit_website changes it with more prompts, and publish_project makes it live when the user wants. Give the user the returned editor_url to open the site in Grigora's editor. Args: prompt: What the website is for and what it should contain — business, audience, pages, tone, style. Specific is better. name: The website's name, e.g. "Pumpkin". Optional; derived from the prompt when empty. attachments: Optional links to files for the builder to use — logos, photos, brand guides, menus (PDF), price lists (CSV), audio, video. A list of up to 10 public URLs, e.g. ["https://example.com/logo.png"]. Grigora downloads them itself (up to 80 MB each), so only pass links — never file contents. Refer to them in the prompt by file name, e.g. "use logo.png in the header". For a LOCAL file (e.g. on the user's computer), first call get_attachment_upload_url, upload it with the returned curl command, then pass the returned url here. A refused attachment fails the call before anything is built or charged.
    Connector
    Destructive
    OAuth
  • List every city What's Up In covers, with its site, its own MCP endpoint, its status (live or beta) and how many travel-worthy events it indexes now. Call it to find valid `city` values for search_events, list_upcoming, get_event and get_city, or names for search_across_cities' `cities`; for one city's neighborhoods, topics and event counts use get_city. Takes no arguments; the list changes only when a city launches. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
    ConnectorNo auth
  • Starts the AI usability test for a proposal from propose_usability_test or revise_usability_test. Intended to run only after the user has reviewed the plan and explicitly approved launching it, because it spends AI-tester runs and creates a new project. A proposal launches once: calling it again (for example after the user launched from the plan view) returns that test with alreadyLaunched: true. Requires the latest proposalId: each revise replaces earlier ids, and an outdated id fails with PROPOSAL_NOT_FOUND. Optional last-minute edits: add or remove tasks or questions, swap personas. Returns the testId, the final personas and plan, and a `startedMessage` with the expected duration (usually several minutes). Results come from wait_for_results. Another batch on an existing project is run with relaunch_usability_test, which avoids a duplicate project.
    ConnectorOAuth
  • OpenFinance Pons v2 launch — launch a token on Robinhood Chain (EVM, chain id 4663) paired against ETH or any Pons-approved asset, INCLUDING Robinhood's own tokenized-stock mirrors (TSLA, AAPL, NVDA, GOOGL, AMZN, MSFT, META, COIN, PLTR, GME, SPY, and more). This is the "launch a token against a Robinhood stock" tool. ROUTING: • **For a NEW launch, use openfinance-launchpad-wrapper instead.** It launches on this same Pons curve and adds a fee module, so it is a superset; a plain launch is module='keep' there. This tool's launch_token is legacy, kept for compatibility — do not route a new launch to it. • This tool remains the right one for reading Pons state (list_quote_assets, get_launch_terms, list_tokens) and for fee actions on tokens launched through it before the wrapper existed (get_claimable_fees, sweep_fees, claim_fees, enable_holder_fee_sharing). • Always call action='list_quote_assets' first if the user hasn't stated an exact pair asset, or wants to see what's available — the approved list is live-checked and can change. • This is a DIFFERENT chain/protocol from the Solana launchpad tools (openfinance-raydium-launchpad, openfinance-raydium-cpmm) — Pons runs on Robinhood Chain, an EVM chain, and the user's Privy EVM wallet is used, not their Solana wallet. • There is no Pons API — everything here is a direct on-chain contract call (confirmed at docs.ponsfamily.com/v2). ACTIONS: launch_token — { name, symbol, image (base64), description?, twitter?, telegram?, website?, quoteAsset, creatorTaxBps?, developerBuyAmount?, snipeTaxExemptions? }: `twitter`/`telegram`/`website` are full URLs (e.g. "https://x.com/handle") — pass them exactly as given, do not construct or prefix a URL from a bare handle. `quoteAsset` — REQUIRED, a symbol (e.g. "TSLA", "ETH", "AAPL") or address from list_quote_assets. `creatorTaxBps` — optional creator trading tax in basis points (0-10000), capped by Pons's live limit. Default 0. `developerBuyAmount` — optional atomic dev buy in the quote asset's own human units (e.g. 0.05 for 0.05 ETH), executed in the SAME transaction as the launch via Pons's launchAndBuy helper. No platform fee — the launching user's own wallet is set as `creatorFeeRecipient` by default, so they keep 100% of Pons's creator-fee bucket. Set `creatorFeeRecipient` to redirect it to a specific wallet instead, OR set `shareFeesWithHolders: true` to redirect it to a Pons holder distributor (pro-rata to token holders) — these two are mutually exclusive; see enable_holder_fee_sharing below for the fuller explanation of the holders path. Returns { token, curve, pairToken, launchConfigId, graduationThreshold, txHash, tokensOut?, holderFeeSharing? }. **DESTRUCTIVE AND IRREVERSIBLE — launches a real token on mainnet with real ETH/asset committed for the launch fee (and dev buy if set).** Show the user: name, symbol, exact quoteAsset resolved, launch fee (from get_launch_terms), creatorTaxBps, and developerBuyAmount. Require explicit confirmation before calling. list_quote_assets — {} (PUBLIC — no auth): returns [{ address, symbol, name, decimals, isNative }] — every asset currently approved as a launch pair, including Robinhood's tokenized-stock mirrors. get_launch_terms — { quoteAsset }: live launch eligibility + fee terms for the caller against one quote asset. Call this before launch_token to show the user the current launch fee and confirm their wallet is eligible (`canLaunch`). Returns { launchFee, launchEnabled, canLaunch, maxCreatorTaxBps, snipeTaxStartBps, snipeTaxSeconds, activeConfig, graduationThreshold, expectedEconomics, protocolFeeShareBps, hookFeeBps, buybackBurnBps }. list_tokens — { limit?, offset?, creator? } (PUBLIC — no auth): paginated list of tokens launched under our platform. Returns { tokens: [{ token, curve, pairToken, name, symbol, logoUri, creatorAddress, twitter, telegram, website, marketCapUsd, marketCapDisplay, ... }], total, limit, offset }. `marketCapUsd` (raw number) + `marketCapDisplay` (compact, e.g. "143K"/"2.5M"/"1.2B") come from Codex via Uniblock — both `null` until Codex indexes the token, expected for very recent launches. `twitter`/`telegram`/`website` fall back to Codex's own indexed data when our own launch record doesn't have them (e.g. older launches) — our stored value always wins when present. enable_holder_fee_sharing — { token } (0x… address): redirects an already-launched token's creator fees to its Pons holder distributor — the retry path if launch_token's own `shareFeesWithHolders` attempt failed, or for opting in after the fact on a token launched without it. Idempotent. Irreversible via Pons's own public creator-controls once done — a durable economic choice, not a UI toggle, so it needs the same explicit-confirmation treatment as launch_token itself. get_claimable_fees — {} (uses the caller's connected wallet): READ-ONLY. Pons fees are never pushed to a wallet as they accrue (docs.ponsfamily.com/v2#claiming) — they build up on a launch's bonding curve and must be swept into a shared fee escrow before they're claimable. Call this FIRST, before sweep_fees or claim_fees, to see both: what's already claimable right now, and which of the caller's own launches still have fees sitting unswept on their curve. Returns { claimable: [{ quoteAssetSymbol, quoteAssetAddress, balance }], unswept: [{ token, quoteAssetSymbol, quoteAssetAddress, graduated, quoteFeeBalance, creatorTaxBalance }] }. `graduated: true` entries can't be swept yet (see sweep_fees). sweep_fees — { token } (0x… address): moves a launch's unswept curve fees into the shared fee escrow, where they become claimable via claim_fees. The caller's connected wallet must be that token's current on-chain creator-fee recipient. Only pre-graduation launches are supported — a graduated token's fees accrue on its pool instead and this action rejects it rather than risk an unverified call. Writes a real transaction (moves the launch's own accrued fees; no user funds are put at risk beyond gas) — mention the amounts from get_claimable_fees before calling, but this doesn't need launch_token-level ceremony since it can't misdirect funds, only move them from curve to escrow. Returns { txHash, quoteFeeSwept, creatorTaxSwept }. claim_fees — { quoteAsset? } (symbol like "ETH"/"TSLA" or address; defaults to native ETH): withdraws the caller's already-swept escrow balance for one quote asset to their own connected wallet. Call get_claimable_fees first to know which quote assets actually have a balance — this errors if the chosen asset's balance is zero. Returns { txHash, quoteAssetSymbol, claimed }. **⚠️ SAFETY** — launch_token is irreversible and commits real funds (the launch fee, plus any dev buy) on mainnet. Always call get_launch_terms first, show the resolved launch fee and quote asset, and get explicit confirmation.
    ConnectorOAuth
  • Use this before connect_feed when the user gives a website or blog URL rather than a feed URL, or to confirm what a feed contains before subscribing. Resolves the URL, discovering the site's feed when given a plain page URL, and reports what would be subscribed to. Returns kind "feed" with the resolved feedUrl and a sample of its newest entries when there is one answer, or kind "candidates" when the site exposes several feeds — in that case show the user the candidates and ask which to use, then pass that feedUrl to connect_feed. Nothing is saved and no credits are spent. Org-scoped: needs no accountId.
    ConnectorOAuth
  • Live pump.fun heartbeat: trades/min, launches, graduations, graduation rate, hottest tokens in the last 15 min. Computed from our own live recording of every pump.fun bonding-curve trade. Use it to decide whether the launch market is hot or dead before scanning individual tokens. When to use: For the market right now; for trends over days use pump_history. Price: free. Errors: returns isError with a message for invalid input or an upstream failure (not charged).
    ConnectorNo auth
  • Claims `hostname` for this website and registers it with the Cactal edge. Custom domains must first be enabled for the website (`websiteDomains.setEnabled`, owner-only — enabling is the billing moment); the request fails with 403 `custom_domains_disabled` otherwise. Adding or removing domains on an enabled website never changes billing. The domain is created in `pending_dns` status, and the returned `dnsRecords` list exactly what to create at your DNS provider: an ownership TXT record on `_cactal.<hostname>` plus a routing record (a CNAME for subdomains or an A record for apex domains). Hostnames must be lowercase ASCII domains (not IP addresses or Cactal platform hosts), each website can have at most 10 custom domains, and a hostname can be claimed by only one website; claims that never verify expire after 7 days. After creating the records, call the verify endpoint or wait for the automatic re-checks.
    ConnectorOAuth
  • Find similar or competitor websites based on classification. Takes a URL, classifies it (or uses cached classification), and returns other websites from the same category and subcategory. Useful for competitive analysis and discovering related content. Rate limited to 1 request per minute per domain. Args: url: The website URL to find similar sites for. limit: Maximum number of similar sites to return (1-50, default 10). Returns: Dictionary with: - url: The input URL (normalized) - classification: The URL's category and subcategory - similar_sites: List of similar URLs from the same category - total_in_category: Total sites in this category/subcategory - cached: Whether the classification was from cache
    ConnectorNo auth
  • Look up the public Website Launches launch record for a single domain. Returns launch timing, owner verification status, milestone summary, public trust context, and a public record URL. Single domain only; does not search, list, discover, or export websites. Hosting, registrar, and location are secondary details — only surface them if the user explicitly asks.
    ConnectorNo auth
  • Live pump.fun heartbeat: trades/min, launches, graduations, graduation rate, hottest tokens in the last 15 min. Computed from our own live recording of every pump.fun bonding-curve trade. Use it to decide whether the launch market is hot or dead before scanning individual tokens. When to use: For the market right now; for trends over days use pump_history (callable here by name). Price: free. Errors: returns isError with a message for invalid input or an upstream failure (not charged).
    ConnectorNo auth