"Launchpad" matching MCP tools:

• ctrl_create_workflow

  CTRL

  Create a CTRL workflow draft. ONE trigger + an ordered chain of up to 20 actions/conditions/utilities. Returns { workflowId, activateUrl }. Pass `targetChain` to pick which chain the workflow runs on — "base" (default, launchpads + Aerodrome + UniV4) or "ethereum" (UniV3 only, no launchpads, no clanker/zora). CRITICAL: call ctrl_get_block_catalog FIRST (with the same `chain` value) to discover field names — every key in trigger.config and chain[].config must exactly match catalog fields[].key. Populate EVERY field the user expressed intent for. For pool.created (Token Launch, Base-only) set launchpad (e.g. ["bankr"]), keywordIncludes ("ai,agent,claw"), keywordMatchMode "any", keywordCategories (["ai_agents"]), safetyEnabled true, safetyRejectHoneypot true, safetyMinScore 50. For cypher.swap set tokenIn ("ETH"), tokenOut ("{{trigger.tokenAddress}}"), tokenOutMode "dynamic", amount (ETH units, e.g. 0.005 — ASK USER if not specified), slippage (15 for snipes), and autoSell* if user wants an exit (autoSellEnabled true, autoSellMode "multiple", autoSellMultiplier 2, autoSellPercent 100, autoSellReceiveToken "USDC"). For notify.telegram set message with {{token}}/{{amount}}/{{txHash}} placeholders. Interview the user for missing critical fields (amount, exit strategy, keywords) — do not silently default.

  Connector

• zeekeo_create_campaign

  rankparse-mcp

  Creates a Zeekeo LinkedIn campaign: sends a connection invite using invite_template_id, and optionally — if followup_template_id is given — waits for the invite to be accepted, then sends a follow-up message using that template. Create templates first with zeekeo_create_template. Provide exactly one of filter_url (a LinkedIn search results URL) or profile_urls (specific profiles) as the target. This starts REAL LinkedIn automation once the campaign has profiles in it — confirm with the user before calling. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Connector

• zeekeo_list_campaigns

  rankparse-mcp

  List the user's Zeekeo Launchpad campaigns (LinkedIn automation). Use this to find a campaign_id for zeekeo_send_message, or call zeekeo_create_campaign to make a new one. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Connector

• zeekeo_create_template

  rankparse-mcp

  Creates a reusable Zeekeo message template. Call this BEFORE zeekeo_create_campaign — a campaign references templates by the template_id this returns, not inline text. type must be 'linkedin_invite' for a connection-request template, or one of linkedin_message/linkedin_inmail/email_message for a follow-up/reply template. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Connector

• launch_token

  aeX402 — Cross-Chain DeFi MCP: LINQ, AMM, Bridge, AI

  Launch a memecoin on the aeX402 launchpad on Robinhood Chain (EVM 4663) for a FIXED pump.fun-style bonding curve (1B supply, starts 0.0001 USDG, graduates at 10,000 USDG raised, quoted in USDG). You supply only identity — name + ticker (+ optional description/image/links). DEFAULT (custodial): the aeX402 backend SIGNS + SUBMITS the createVPool tx for you, so a claude.ai user with NO WALLET can launch in one call; returns {ok,status,txHash,vpId}. Optionally pass `creator` (a 0x address) to record as the coin owner. Pass build:true instead to get an UNSIGNED tx {to,value,data} to submit yourself (non-custodial — that requires `creator` and makes you the on-chain creator). Live create is gated on the launchpad facet upgrade (pending); until enabled a custodial call returns status "gated" and burns no gas.

  Connector

• till_funder_history

  biii

  HAS THE WALLET THAT PAID FOR THIS LAUNCH ALREADY KILLED ONE? till_launch_funder reads the graph and tells you a cluster exists; this reads our OWN observation record and tells you what happened to the rest of it. The distinction matters because every other check here asks the token a question it cannot answer in time: a curated security index returns an owner address for roughly one Base token in ten, so "who can still fire a rug power" — the question this whole scanner was built on — came back unanswerable on 221 of 221 launches we watched. Who PAID is answerable, because we watched that ourselves. THE EVIDENCE IS WALK-FORWARD, which is the only kind worth quoting: every token was replayed in time order and judged using strictly earlier history, so no prediction ever saw its own outcome or any later one. A payer with a prior kill was followed by another death in 62 of 67 resolved cases (93%) against a 52% base rate, and it holds across SIX independent payers, each 75-100% lethal — not one outlier carrying an average. Read the limits as part of the answer: six operators is not sixty, "clean so far" rests on two payers and is an absence of a bad record rather than a good one, and 47% of watched launches have no funder on file — but 96% of THOSE were never traced at all, because tracing is capped per run, so that number measures our own budget and not the chain; they are reported as out of reach rather than safe, and never as evidence. AND IT IS EVADABLE FOR THE PRICE OF ONE HOP — a fresh funding wallet lands in "never seen", which is already 30% of cases. It makes REUSE expensive, which is what an operation running dozens of launches an hour actually does; expect the strong bucket to decay as operators adapt. Structure, never intent: a shared funder proves shared control or shared infrastructure, and a launchpad looks identical from the graph. Every answer carries the age of the database, and past the freshness bar the reassuring verdicts are WITHDRAWN rather than annotated, because a stale "never killed" is the exact sentence that gets someone hurt. Pure, offline, read-only.

  Connector

• mainstreet_wallet_cluster

  mainstreet

  Map the 1-hop on-chain neighborhood of a wallet or token and return a cluster verdict: CLEAN_CLUSTER / MIXED_CLUSTER / TOXIC_CLUSTER / ISOLATED / UNKNOWN. ISOLATED means we read our sources and found NO connection (brand-new or dormant wallet) — that is a measurement; UNKNOWN means the sources themselves were unreadable. Edges are INDEX FACTS, not ownership claims: deployed, also-deployed, co-sniped, paid, rated, contract, wallet. Every response carries `reasoning` (why this verdict) and `coverage` (sources read vs total, plus how many peers could NOT be screened) — UNKNOWN means our sources were unreadable, NOT that the wallet is isolated. ⚠️ There is NO exchange/CEX label: a high-degree hub is not distinguished from a coordinated cluster, so an exchange hot wallet can read TOXIC. ⚠️ Structure proves who transacted with whom, never WHY — a shared funder is equally the signature of a launchpad and of a rug factory. Use to refuse an interaction, never to accuse a person.

  Connector

• zeekeo_send_message

  rankparse-mcp

  Sends a REAL LinkedIn message, InMail, or email through Zeekeo Launchpad to a profile in one of the user's existing Zeekeo campaigns. Only call this after showing the user the drafted message and getting explicit approval. Resolves linkedin_url into that campaign first, so the profile must be reachable from it (use zeekeo_list_campaigns to pick campaign_id). Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Connector

• zeekeo_activate_campaign

  rankparse-mcp

  Activates a paused Zeekeo campaign so it starts running (sends real LinkedIn connection invites per the campaign's configured limit/delay). Zeekeo campaigns are created paused by default — call this after zeekeo_create_campaign to actually start sending. This resumes REAL LinkedIn automation — confirm with the user before calling. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Connector

• robinx_follows

  robinx-mcp

  Follow/unfollow transitions by the X accounts that matter on Robinhood Chain — the chain's principals and launchpad accounts — checked roughly every 6 hours and recorded as timestamped events. X exposes only CURRENT following state, so this history cannot be reconstructed after the fact. Every newly-followed handle is crossed with its MEASURED RobinX caller record, so you can see when a principal starts following an account RobinX grades. Pollable with since=<cursor>; filter by watched=<handle> or event=follow|unfollow. Edges that already existed when tracking began are marked baseline and never reported as dated follows. Costs $0.02 USDC on Base. (paid $0.02 — see instructions)

  Connector

• build_launch_tx

  ScanHood

  Build (but do not sign or send) a launchToken transaction against ScanHood's live no-rug launchpad on Robinhood Chain — either Uniswap V3 (anti-snipe protection, supports an atomic initial buy) or V4 (Uniswap's newest, no anti-snipe window). Returns raw unsigned tx fields (to, data, value, gas) for the caller's own wallet to sign and broadcast — ScanHood never holds funds or keys. On success the token's liquidity is locked (V3: locker-held position; V4: locker-held one-sided position) and cannot be pulled.

  Connector

• collection_team

  fingers

  WHO is behind an OpenSea collection / mint: the creator-owner wallet, the PAYOUT recipient wallet(s) where mint + royalty money goes, the contract, verification status, and socials. THE tool for 'who created this mint / can they rug and run / is this marketplace or launchpad launch legit / where does the money go'. On no-code / SeaDrop mints the contract deployer is usually OpenSea itself, so vet the OWNER + PAYOUT wallets this returns (run address_security, deployer_check, wallet_nfts on them, and check if the payout wallet has drained funds). Accepts a collection slug, name, OpenSea URL, or contract address.

  Connector

• rug_check

  fingers

  One-call MARKETPLACE RUG-RISK scorecard for an NFT mint / collection: resolves the team, vets the creator/payout wallet (scam flags, wallet age, prior deployed-contract track record), follows the mint proceeds, checks contract safety, and flags the classic launchpad-scam patterns. THE tool for 'is this mint a scam / will this team rug / is this launchpad launch safe'. Weighs facts honestly (a flagged wallet or fast cash-out is a real red flag; a fresh wallet is neutral context). Accepts a collection slug, OpenSea URL, or contract address.

  Connector

• request_launch_token

  Gitbank

  Request a token launch on Base Mainnet via Clanker (MCP-exclusive launchpad). Requires a 0.01 ETH creator buy-in: the ETH buys the newly launched token and distributes it to all $GITBANK holders. Returns a confirm_code and payment instructions.

  Connector

• hederaFindMemeCoins

  EmblemAI AgentWallet

  Browse Hedera meme tokens listed on the MemeJob bonding-curve launchpad. Sort by market cap, creation time, last activity, or nearest-promoted; paginated for discovery feeds.

  Connector

• deployer_check

  fingers

  Due diligence on the WALLET/DEPLOYER behind a token, NFT, or mint: how many contracts it has deployed before and when (its TRACK RECORD), how old the wallet is, plus its scam/abuse reputation. THE key check for 'who is behind this project / is this team legit', especially on a launchpad mint where the contract is a clean template but the PEOPLE are the real risk. A first-time deployer with no history is UNPROVEN (not necessarily bad); a wallet that has launched and abandoned mints before, or is flagged, is a real red flag. Needs the creator/deployer 0x ADDRESS (get it from token_security's creator_address or the contract).

  Connector

• aex402_rh_pool

  aeX402 — Cross-Chain DeFi MCP: LINQ, AMM, Bridge, AI

  Get the live state of the aeX402 AMM on Robinhood Chain (EVM 4663) — the diamond-contract port of the Solana AMM. The AMM is the set of GRADUATED launchpad coins whose pools are seeded in-diamond on the canonical launchpad (0xED2F); this enumerates them live by scanning VPoolGraduated events + reading each pool's reserves, so it tracks reality as coins graduate. Returns graduatedPools[] (poolId, token, reserves, TVL), graduatedPoolCount, and status ("live" | "no-graduated-pools" | "unknown"), plus the legacy standalone 0xA1F6 USDG/WETH pool (legacy-drained). Distinct from the chain's Uniswap-fork DEX. No inputs.

  Connector

• till_launch_funder

  biii

  WHO PAID FOR THIS LAUNCH, AND WHAT ELSE DID THEY PAY FOR? Follows the money backwards: a token names its creator, a creator minted minutes ago names the wallet that funded it, and that funder usually funded others. Three free explorer queries surface a cluster no buyer can see from a chart. Proven live: one funder had sent an identical 15.020 ETH to 26 fresh wallets. Reports STRUCTURE ONLY — a shared funder proves shared control or shared infrastructure, never fraud; a launchpad and a rug factory are indistinguishable from the graph. What it does prove is that these tokens share fate and should be judged together.

  Connector

• onchainpulse

  pulsenetwork

  OnchainPulse: Intelligence API for the onchain financial transition. Decodes legislation, tracks RWA tokenization, models sector scenarios, guides onchain integration. All endpoints require x402 payment (USDC on Ba Coverage: Global Endpoints: • legislation ($0.15): Translate crypto bills to plain English with sector impact • rwa ($0.15): Survey the real-world-asset market across asset classes • scenario ($0.20): Model sector impact scenarios with if/then analysis • transition ($0.10): Guide practical onchain onboarding by organization type • monitor ($0.10): Monitor institutional onchain activity, weekly briefs • compliance ($0.15): Map regulatory compliance duties by jurisdiction • tokenize ($0.15): Explain how to tokenize any asset type, step by step • glossary ($0.05): Decode any onchain finance or regulatory term plainly • snapshot ($0.10): Summarize the onchain transition in a weekly macro brief • memecoin ($0.015): Scan a Solana memecoin pre-trade, deterministic verdict • evmtoken ($0.015): Scan an EVM token pre-trade, multi-chain, deterministic • rwa-risk ($0.25): Assess issuer and redemption risk for a named RWA product • gold-check ($0.15): Compare tokenized gold products: PAXG vs XAUT • etf-flows ($0.15): Track US spot crypto ETF flows with per-issuer detail • clarity-watch ($0.10): Track CLARITY Act status, CFTC/SEC split, passage odds • vault-apy ($0.02): Live USDC yield panel on Base — onchain lending rates + realized Morpho vault APY, deterministic • asatoken ($0.015): Scan an Algorand ASA pre-trade, deterministic verdict • exit-depth ($0.02): Estimate sell-side depth of a v3 pool at 1-25% price impact • holder-map ($0.02): Map holder concentration with LP/burn/contract labeling • narrative-check ($0.15): Check a project's public claims against observed chain data • receipts ($0.35): One-call composite token due-diligence report • honeypot ($0.005): Check honeypot sellability flags, half a cent • liquidity ($0.005): Check token DEX liquidity and momentum, half a cent • rh-launches ($0.01): Live Uniswap-launchpad launch feed on Robinhood Chain, one cent • iso-receipt ($0.05): ISO 20022 camt.054-style receipt for an on-chain settlement (signed, verifiable)

  Connector

• hoodly_list_robinhood_launches

  Hoodly GMGN Robinhood Research

  Read-only discovery of newly created, near-completion, or graduated Robinhood Chain launchpad tokens. This is chain-wide, not Pons-only provenance.

  Connector