MCP reference

Connect an agent

The API's data as tools an AI agent can call, on a hosted Model Context Protocol server. No sign-in and no key; 60 requests a minute per visitor are free.

Server URL

https://weball.fun/mcp

Claude Code

claude mcp add --transport http weball https://weball.fun/mcp

Claude (web and desktop)

Settings, then Connectors, then Add custom connector, and paste the server URL.

Other clients

Most accept a server entry like this in their MCP settings:

{
  "mcpServers": {
    "weball": {
      "url": "https://weball.fun/mcp"
    }
  }
}

Coin names, symbols, descriptions and links are written by coin creators, so the server wraps each as {"untrusted_text": …} and tells the agent to treat them as data, never instructions.

Pricing

How paying works

With x402, in USDC on Solana: no account, no key, no subscription. A request that needs paying gets a tool result with the price (the x402 payment requirements). Your agent signs a USDC transfer for that amount and calls the tool again with it in the payment argument (or _meta["x402/payment"]). We check it, settle it on Solana and answer, with the receipt in _meta["x402/payment-response"]. x402-aware clients and agent wallets do this automatically.

WeBall pays the network fee. You only ever sign a transfer of the stated amount to WeBall's address; nothing else can move from your wallet.

Launch a coin

An agent can launch a coin with its own wallet, calling these tools in this order. WeBall never holds the key: prepare_launch returns an unsigned transaction, the agent signs it, then submits it. Preparing a launch is free for a limited time. A wallet may prepare 5 launches an hour. On pump.fun (prepare_pump_launch, submit_pump_launch, pump_launch_status) the coin pairs with SOL, USDC or a token pump.fun lists and pays its holders 70% of every creator fee; on Meteora (prepare_launch, submit_launch, confirm_launch) it's SOL coins without a creator lock. The same steps are in the API.

• Step 1get_launch_terms(wallet)Launch#

  Launch step 1a: the terms message a wallet must sign (UTF-8, ed25519) before it can launch. Sign it within 10 minutes and pass the signature to accept_terms. Once per wallet per terms version.

• Step 2accept_terms(wallet, version, signedAt, signature)Launch#

  Launch step 1b: record the wallet’s signed acceptance of the terms.

• Step 3prepare_launch(launch)Launch#

  Launch step 2 (free for a limited time; 5 an hour per wallet): validate and record a coin launch and get its unsigned transaction. `launch` is the same object as POST /api/v1/launch/prepare: { creator, mint, name, ticker, description?, socials?, image? (base64), mode: "holder" | "creator", feeBps, basket?, recipients?, buyBps?, rollIn?, hooks? }. SOL coins without a creator lock for now; `hooks` (live ids from list_hooks) make a Token-2022 coin. Sign `transaction` with the creator wallet (and the mint keypair when mintSource is "browser"), then call submit_launch.

• Step 4submit_launch(mint, transaction)Launch#

  Launch step 3: send the signed launch transaction (base64). Returns confirmed, or pending with a signature: then call confirm_launch. Never sign and send it again.

• Step 5prepare_pump_launch(launch)Launch#

  Launch a coin on pump.fun, step 2 (after get_launch_terms / accept_terms; free for a limited time; 5 an hour per wallet). `launch` is the same object as POST /api/v1/launch/pump/prepare: { creator, mint, name, ticker, image (base64), description?, quoteMint? (the pair: SOL by default, USDC or a token pump.fun lists), holdersPaid? ("pair" | "basket"), basket?, buyLamports? (SOL pairs only), socials? { website, x, telegram } }. Returns `transactions`: one or two unsigned v0 transactions. Sign every one with the creator wallet, sign the first with the mint keypair too, then call submit_pump_launch with all of them in order. When `sponsored` is true WeBall pays the launch costs: its sponsor is each transaction's fee payer and signs at submit, so sign only as the creator (and the mint) and leave its signature empty.

• Step 6submit_pump_launch(mint, transactions)Launch#

  Launch on pump.fun, step 3: send the signed transactions (base64, in the order prepare_pump_launch gave them). Returns confirmed, or pending: then poll pump_launch_status. Never sign and send them again.

• Step 7pump_launch_status(mint)Launch#

  Launch on pump.fun, step 4: where a launch is (prepared, sending, confirmed or abandoned) and, once confirmed, the coin’s page.

• Step 8confirm_launch(mint, signature)Launch#

  Launch step 4: confirm a pending launch by its signature.