Skip to main content
Glama
734,463 tools. Updated 2026-11-02 04:12

"Launchpad" matching MCP tools:

  • Launch a token on X1, or read what has been launched. Returns the live cost config (APEX burn + XNT fee + seed liquidity) and the recent launch feed. The build endpoints return unsigned transactions you sign yourself.
    ConnectorNo auth
  • OpenFinance Launchpad — Solana token launchpad on a dynamic bonding curve. Launch a new SPL token in a single tx, trade it on a bonding curve, and graduate to a DAMM v2 AMM once the curve fills. Single-tool dispatch on `action`. ROUTING: • To LAUNCH a new token: use action='launch_token'. • To TRADE a DBC token PRE-graduation (still on the bonding curve): use action='buy' / 'sell' here. • To TRADE a DBC token POST-graduation: it's a DAMM v2 pool now — route through Jupiter (`onchain_jupiter_order` + `onchain_jupiter_execute`). Calling 'buy'/'sell' here on a graduated pool returns `alreadyGraduated: true`. • The PoolConfig PDA (env METEORA_DBC_CONFIG) controls total supply, decimals, fee tier, curve shape, and graduation threshold — these are NOT per-launch params. ACTIONS: launch_token — { name, symbol, image (base64), description?, website?, twitter?, telegram?, configAddress?, initialBuySol? }: pins image + Metaplex JSON metadata to IPFS via Pinata, generates a fresh mint keypair, calls DBC createPool. Set `initialBuySol` to also buy the new token in the SAME tx (creator "dev buy" — atomic, no snipe risk; creator needs ~0.035 SOL launch cost + the buy amount). Returns { mintAddress, poolAddress, metadataUri, imageUri, signature, initialBuySol?, initialBuyTokens? }. **DESTRUCTIVE — creates a permanent SPL mint on mainnet.** Always confirm with the user before calling. **WEBSITE NUDGE — `website` is optional but recommended: tokens that ship with a website tend to bond/graduate at a higher rate (more credible to traders). Before launching, if the user hasn't given a `website`, suggest adding one — e.g. "Want to add a website? Tokens with one tend to graduate more often. It's optional — I can launch without it." Launch fine without it if they decline; never block the launch on it.** list_tokens — { limit?, offset?, sort?, creator? } (PUBLIC — no auth): paginated explore feed of every token launched under the partner config. sort 'newest' (default, by on-chain activation time) or 'mcap' (market cap desc). limit ≤100 (default 30). Pass `creator` (a Solana wallet) to filter to one launcher's tokens — use this for "show me my launched tokens" / "what has wallet X launched". Returns { tokens: [{ pool, mint, name, symbol, image, description, website, twitter, telegram, externalUrl, metadataUri, creator, createdAt, curveProgress (0-1 bonding fill), graduated, priceSol, marketCapSol, marketCapUsd }], total, limit, offset, solUsd }. `website`/`twitter`/`telegram` 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. get_pool_state — { poolAddress }: returns { baseMint, quoteMint, graduated, quoteTokenCurveProgress (0-1), baseTokenCurveProgress (0-1), migrationQuoteThreshold }. Call before any buy/sell to check graduation status and mcap progress. quote_buy — { poolAddress, quoteAmount, slippageBps? }: returns { amountIn, amountOut, minimumAmountOut, priceImpactBps, alreadyGraduated }. `quoteAmount` is in the quote token's smallest unit (lamports for wSOL, atomic for USDC). quote_sell — { poolAddress, baseAmount, slippageBps? }: mirror. `baseAmount` is in the new token's smallest unit. buy — { poolAddress, quoteAmount, slippageBps? }: signs + broadcasts a buy. Returns { signature, amountIn, minimumAmountOut, amountOutQuoted }. sell — { poolAddress, baseAmount, slippageBps? }: mirror. migrate — { poolAddress }: anyone can call once `quoteTokenCurveProgress >= 1`. Migrates remaining reserves into a DAMM v2 pool, mints two LP-position NFTs. Returns { signature, firstPositionNft, secondPositionNft }. get_pool_fees — { poolAddress }: read-only claimed/unclaimed/total fee breakdown for a pool, split into creator and partner. Use to show a launcher how much they can withdraw. get_creator_fees — {}: the caller's accumulated creator fees across EVERY token they launched. Returns { creator, pools: [{ pool, creatorBaseFee, creatorQuoteFee, hasUnclaimedCreatorFees }] }. claim_creator_fees — { poolAddress }: withdraw the caller's creator trading-fee share from one of their pools to their own Privy wallet. Returns { pool, signature, receiver }. Show the unclaimed amount (from get_creator_fees / get_pool_fees) and confirm before calling. **⚠️ SAFETY — launch_token is irreversible.** Before calling, show the user: name, symbol, image preview link (the IPFS gateway URL after upload), the PoolConfig PDA being used, total cost in SOL (~0.035 SOL), and require explicit confirmation. Solana wallet must be delegated to the app (412 on first call otherwise). **⚠️ SAFETY — buy/sell are real swaps.** Always show the quote (input/output, slippage, price impact) before submitting and require user confirmation, same shape as Jupiter execute.
    ConnectorOAuth
  • OpenFinance launchpad (the "wrapper") — launch a token on Robinhood Chain (EVM, chain id 4663) with a FEE MODULE that decides, permanently, where its trading fees go. This is the "launch a token that burns its fees / splits them / runs a raffle / pays its holders" tool. **THIS IS THE DEFAULT LAUNCH TOOL FOR THE PONS CURVE ON ROBINHOOD CHAIN** — a plain launch with nothing said about fees uses module='keep', which sends the fees to the creator's own wallet and is the only module that can be repointed later. Do NOT use openfinance-pons-launch for a new launch; this tool launches on the same Pons curve, with the fee router added, so it is a superset. **It is not the only launch venue on this chain.** openfinance-launchpad-v4 is a separate product: a launch there IS a real Uniswap V4 position, paired against an approved quote token such as USDG, with a snipe tax and no fee modules. Route to it when the user names Uniswap or V4, names a pair asset like USDG, or wants the token tradable through the Uniswap router. If the user says only "launch a token on Robinhood Chain" with nothing about fee modules or Uniswap, ASK which venue — the pools are not interchangeable and the choice is permanent. HOW IT RELATES TO openfinance-pons-launch: • Same chain, same Pons curve underneath, same Privy EVM wallet. The token still trades on Pons. • This adds a fee router, so fees can be kept, sent to one wallet, split, burned, raffled, or airdropped to holders. • openfinance-pons-launch remains only for READING Pons state (quote assets, launch terms) and for the fee-claim actions on tokens launched through it BEFORE the wrapper existed. Its launch action is legacy — do not route a new launch to it. • **Module choices are FROZEN AT LAUNCH**, with one exception: `keep` may be repointed later (`FeeRouter.repointWallet`). A burn, split, raffle or holders module cannot be changed afterwards — no admin key, no migration. Treat those like deploying an immutable contract. • Every launch keeps 5% of its fee bucket (500 bps) for the keeper's gas. This is not optional and not a platform fee: without it the launch could never have its fees moved, and the keeper refuses to service it. The module gets the other 95%. MODULES (pick one, frozen): keep — fees to the creator's own wallet. wallet — fees to one named wallet (`recipient`). split — fees divided between 2-16 wallets (`split`), bps totalling exactly 10000. burn — fees buy the launched token back and burn it. raffle — fees fund a periodic prize draw among holders (`raffle`, required). holders — fees airdropped pro-rata to holders (`airdrop`, optional; defaults are sensible). ROUTING: • A bare "launch a token" with no fee preference → this tool, module='keep'. Do not ask the user to choose a module they did not raise; `keep` is the plain behaviour and is repointable. • Call action='get_readiness' first for a raffle launch — it reports whether the keeper and randomness contracts are live, and lists the stock assets a stock-prize raffle may use. A raffle launched without a live keeper would never draw. • Call action='simulate_launch' before action='launch' for anything non-trivial. It builds and validates the exact transaction without sending it, so a bad split or an impossible raffle fails for free. • action='list_launches' is the public feed of every launch from this factory, newest first — the "what has been launched" question. ACTIONS: launch — { module, name, symbol, description?, logo?, creatorTaxBps, pairToken?, developerBuy?, recipient?, split?, raffle?, airdrop? }: `module` — one of keep|wallet|split|burn|raffle|holders. Frozen. `creatorTaxBps` — the TOTAL trading tax in basis points, capped by Pons's live limit. The wrapper's own protocol surcharge is included in this number, not added to it. `pairToken` — optional; the asset the token trades against (a symbol or address — use openfinance-pons-launch's list_quote_assets to enumerate them, including Robinhood's tokenized stocks). Defaults to ETH. `recipient` — required for module='wallet'. `split` — required for module='split': [{ recipient, bps }], 2-16 entries, bps summing to EXACTLY 10000. They do not sum if each share is rounded independently — three equal shares floor to 9999 — so floor each and give the remainder to one recipient. `raffle` — required for module='raffle'. Frozen terms: cadence, prize pool share, winners per round, ticket size, prize bounds. **DESTRUCTIVE AND IRREVERSIBLE — launches a real token on mainnet, commits real funds for the launch fee, and freezes the fee module forever.** Show the user: module, resolved pair asset, creatorTaxBps, the 5% keeper slice, and every recipient/share. Require explicit confirmation. simulate_launch — same arguments as launch: builds and validates the transaction WITHOUT sending it. Returns the resolved allocations, the launch fee and the would-be addresses. Free and safe — prefer it before any launch. list_launches — { limit?, offset? } (PUBLIC — no auth): every launch from this factory, newest first. Returns { total, tokens: [{ token, curve, creator, name, symbol, router, adapter, raffle, pairToken, launchedAt, feesOwedWei, marketCapUsd }] }. `launchedAt` is a unix second from the launch's own block — a launch carries no timestamp on chain, so this comes from its `Deployed` event. `feesOwedWei` is what its buckets hold but have not yet delivered. `marketCapUsd` is null until a market-cap provider indexes the token, which is normal for a launch still on its bonding curve with no DEX pair. get_launch — { token } (0x… address): one launch's fee module and routing, read from the contracts. Returns its module, buckets, allocations, router, adapter and raffle. get_funding — { token } (0x… address): why a launch's fees have or have not moved. Returns { paidWei, spentWei, fundingWei, ledger }. `paid` is on chain (what the router has sent the keeper hub); `spent` comes from the keeper's own ledger. The keeper cranks a launch only when the fee covers the gas, so `fundingWei` is the number that explains a launch whose fees appear stuck. `ledger: null` means the keeper has never worked this launch, so spend is zero. list_creator_launches — { creator } (0x… address) (PUBLIC — no auth): every launch by one creator, with the same enrichment as list_launches. get_raffle — { raffle } (0x… address): a raffle's live state — current round, cadence, prize terms, and whether a round is drawable. get_raffle_claims — { raffle, wallet, round? }: a holder's claimable prizes with their Merkle proofs. The proofs come from the keeper's database; whether a slot is already PAID comes from the contract, which is authoritative. list_raffle_stocks — {} (PUBLIC — no auth): the tokenized-stock assets a stock-prize raffle may pay out in. get_readiness — {} (PUBLIC — no auth): whether a raffle can be launched at all in this environment — keeper hub, randomness contract, and whether the hub owner has paused launches. Call before offering a raffle launch. get_keeper_status — {} (PUBLIC — no auth): a deployment check, not launch data. Reports whether this host can reach the keeper's database and whether the keeper is alive. An unreachable database is a SUPPORTED state — proofs fall back to a slower rebuild from transfer history — so `configured: true` with `reachable: false` means proofs still work but the indexed path is not in use. **⚠️ SAFETY** — launch is irreversible, commits real funds, and freezes the fee module permanently. Always simulate_launch first, show the resolved allocations including the 5% keeper slice, and get explicit confirmation.
    ConnectorOAuth
  • OpenFinance launchpad on **Uniswap V4** (Robinhood Chain, EVM chain id 4663) — launch a token whose bonding curve IS a real Uniswap V4 position, trade it through the Universal Router, and graduate it into locked full-range liquidity. **WHICH LAUNCH TOOL TO USE ON ROBINHOOD CHAIN.** There are three, and they are different venues — not alternative spellings of one: • `openfinance-launchpad-v4` (this tool) — Uniswap V4 pools, paired against an APPROVED QUOTE TOKEN (e.g. USDG), with a snipe tax and a creator tax. Use when the user names Uniswap/V4, names a quote asset such as USDG, or wants the token tradable through the Uniswap router. • `openfinance-launchpad-wrapper` — the Pons curve plus a permanent FEE MODULE (burn / split / raffle / holders). Use when the ask is about where the fees go. • `openfinance-pons-launch` — legacy Pons reads only. If the user just says "launch a token on Robinhood Chain" with nothing about fee modules or Uniswap, ASK which venue rather than guessing: the choice is permanent and the pools are not interchangeable. For SOLANA launches use `openfinance-launchpad` (Meteora DBC) — a different chain entirely. **HOW A LAUNCH WORKS HERE** 1. `launch` deploys the token and opens a V4 pool against `pairToken` (an approved quote asset — call `list_quote_assets` first; passing anything else is rejected on chain). 2. The curve is a V4 position, so the token is tradable through the Universal Router immediately. `buy` / `sell` go through `get_quote` → router. 3. When the curve fills, the launch **graduates**: reserves become locked full-range liquidity. `buy` may graduate as a side effect when the buy consumes the rest of the curve — the response says `side: 'graduate'` when that happened. **AMOUNTS ARE BASE UNITS.** `amount` on buy/sell/quote is a raw integer string in the token's smallest unit, never a decimal. The pair asset's decimals are NOT always 18 — USDG is 6, so 1 USDG is "1000000". Read `decimals` from `list_quote_assets` and convert; a 10^12 error here spends a million times the intended amount. **TAXES, AND WHY A QUOTE IS CALLER-SPECIFIC** • A **snipe tax** of 99% applies for the first 3 seconds after launch, decaying to 0. It depends on WHO is swapping, so `get_quote` simulates from the trader's own address. A quote taken for someone else misprices that window and the swap then fails its minimum output. • A **creator tax** (0-10%, `creatorTaxBps`) is fixed at launch and cannot be changed afterwards. • The hook takes 1% of each swap; 30% of that is the protocol's share. **DEV BUY.** `devBuy` is an amount of the PAIR token (a decimal string here, e.g. "1" for 1 USDG — the server converts using that asset's decimals) bought for the creator in the same transaction. It needs that balance in the user's server wallet; the server sends the ERC20 approval itself. **IRREVERSIBLE.** A launch deploys a contract and opens a real pool with real liquidity. Name, symbol, pair token, and creator tax are frozen at launch. Confirm the parameters with the user before calling `launch`, and never launch to "test" the tool. ACTIONS: Reads (no key needed): get_readiness, list_quote_assets, get_pair_terms, list_launches, get_pool, get_market, get_candles Reads (key): get_quote, get_fees Writes (key, real money): launch, buy, sell, graduate, claim_fees Prerequisite: `openfin-setup` — the user needs a server-authorized Privy EVM wallet (POST /agent/auth/authorize-server), funded with the pair token for a buy or a dev buy.
    ConnectorOAuth
  • Retrieve recent Arc token launches tied to their launchpad and minting wallet, with transfer and recipient counts. Filter by launchpad or minimum transfers and paginate results.
    MIT
  • Analyze a token creator's holdings and transfers to detect rug pull risk. See if the dev still holds, sold out, or moved funds to fresh wallets—key warning signals.
    MIT

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    An MCP gateway that connects an owner's existing AI assistant to Estonian business back-office work: company profiles and obligation calendars built from public register data, job playbooks, curated connector catalogue, and server-enforced approvals with receipts. It lets a micro-entrepreneur's chat assistant read deadlines, check counterparties and draft filings while blocking any action that lacks an approval bound to the exact recipient, amount and document.
    7 npm
    MIT

Matching MCP Connectors

  • Read-only, sourced and dated facts on AI tools: search, compare, pricing, free alternatives.

  • Dual-version MCP for pons token launches on Robinhood Chain: v1 trading, v2 curve reads (plan-only).

  • Get the exact launch cost before spending: launch fee, initial buy, 1% trade fee, tokens received, and predicted token addresses. Confirms the irreversible total upfront.
    GPL 3.0
  • Check a token's liquidity pool: get USD depth, the DEX that holds it, and whether LP tokens are burned, locked, or still withdrawable. Use it to assess pull-risk.
    MIT
  • Find SAP development documentation across ABAP, RAP, CAP, UI5, BTP, and AI sources, returning document IDs and snippets so you can fetch full content.
    Apache 2.0
  • Generate a MIDI controller preset in TouchDesigner: creates a MIDI In CHOP and bind table, auto-binds faders/knobs to target parameters, and supports explicit control mappings.
    MIT
  • Compare DEX venues on a chain by pool count, dollar-priced pools, liquidity depth, swaps, and volume to verify where a stock token trades or catch implausibly low pool counts.
    MIT
  • Browse and sort Hedera meme tokens listed on the MemeJob bonding-curve launchpad. Filter by market cap, creation time, last activity, or nearest-promoted with pagination.
    MIT
  • List and filter Uniswap v4 launchpad tokens by status, search by name, symbol or contract address, and sort by newest, raised, progress or swap volume.
    MIT
  • Prioritizes open pull requests by status like ready to merge, conflicts, or awaiting review. Helps you decide what to work on next.
    MIT
  • Checks any launchpad token address for OpenHooks support, Uniswap v4 pool status, graduation, and readiness to open; returns an unsigned open transaction when ready.
    MIT
  • Retrieve an OpenHooks launchpad token's Uniswap v4 pool, bonding-curve progress, amount raised, and recent swaps by contract address.
    MIT
  • Apply a case action to multiple cases in one operation. Works with case-wide actions only, synchronously in Infinity or asynchronously in Launchpad.
    Apache 2.0
  • Search 49,000+ blockchain security audit findings using 14+ filters. Combine keywords, severity, firms, tags, date ranges, and more to find relevant vulnerabilities.
    MIT
  • Aggregate creation and graduation counts over a rolling window to identify active launchpads. Optionally set windowHours for custom ranges.
    MIT
  • Create a MIDI controller map for TouchDesigner: sets up MIDI input and bind tables for device presets, auto-binds controls to a COMP's parameters, and allows explicit overrides.
    MIT