Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

CREW / CrewPay

by fxamsversion 1.2.14i★ –iComputer or cloud
Registry nameio.github.fxams/crewpay-mcp

Install

Overview

Description from the maker (original English)

Unsigned Pump/Bags/Zora/Clanker launches. mintPubkey required. Fees lock at launch.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Other
  • You need to fill in: CREW_AGENT_API_KEY, CREW_LAUNCHER_KEY, X402_EVM_PRIVATE_KEY, x-crew-api-key

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 3 of 3 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • Can do 22 things (tools) crew_build_unsigned, crew_submit_signed, crew_discover, crew_job_create_dry_run …
  • You fill in yourself: CREW_AGENT_API_KEY, CREW_LAUNCHER_KEY, CREW_API_URL, CREWPAY_REFERRAL_CODE, X402_EVM_PRIVATE_KEY, x-crew-api-key

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "crewpay": {
      "command": "npx",
      "args": [
        "-y",
        "crewpay-mcp"
      ],
      "env": {
        "CREW_AGENT_API_KEY": "your-value",
        "CREW_LAUNCHER_KEY": "your-value",
        "CREW_API_URL": "your-value",
        "CREWPAY_REFERRAL_CODE": "your-value",
        "X402_EVM_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http crewpay https://mcp.crewpay.dev/mcp --header 'x-crew-api-key: your-value'

Or run it on your computer

claude mcp add crewpay --env CREW_AGENT_API_KEY=your-value --env CREW_LAUNCHER_KEY=your-value --env CREW_API_URL=your-value --env CREWPAY_REFERRAL_CODE=your-value --env X402_EVM_PRIVATE_KEY=your-value -- npx -y crewpay-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "crewpay": {
      "url": "https://mcp.crewpay.dev/mcp",
      "headers": {
        "x-crew-api-key": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "crewpay": {
      "command": "npx",
      "args": [
        "-y",
        "crewpay-mcp"
      ],
      "env": {
        "CREW_AGENT_API_KEY": "your-value",
        "CREW_LAUNCHER_KEY": "your-value",
        "CREW_API_URL": "your-value",
        "CREWPAY_REFERRAL_CODE": "your-value",
        "X402_EVM_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "crewpay": {
      "type": "http",
      "url": "https://mcp.crewpay.dev/mcp",
      "headers": {
        "x-crew-api-key": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "crewpay": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "crewpay-mcp"
      ],
      "env": {
        "CREW_AGENT_API_KEY": "your-value",
        "CREW_LAUNCHER_KEY": "your-value",
        "CREW_API_URL": "your-value",
        "CREWPAY_REFERRAL_CODE": "your-value",
        "X402_EVM_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • CREW_AGENT_API_KEY secret required env
    crew_ak_… from crew_claim_key / POST /api/agent/keys/claim, or operator key
  • CREW_LAUNCHER_KEY secret env
    Dedicated low-SOL burner Solana secret for launch/wire/lock (local env only — never a tool arg). Not used by hosted remote.
  • CREW_API_URL env
    API base URL (default https://api.crewpay.dev)
  • CREWPAY_REFERRAL_CODE env
    Optional KOL referral code used by crew_claim_key when referral_code arg omitted
  • X402_EVM_PRIVATE_KEY secret env
    Optional hex private key for Base USDC x402 pay-per-call (alternative to CREW_AGENT_API_KEY). Local env only — never a tool arg. Not used by hosted remote.
  • x-crew-api-key secret HTTP header
    crew_ak_… from crew_claim_key / POST /api/agent/keys/claim (required for writes). Hosted MCP is publicMode and cannot hold a launcher secret.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

  • crew_build_unsigned

    The launching agent earns 15% of creator fees onchain. Creator fees follow trading volume and can be zero. Create UNSIGNED launch transactions. For Pump.fun, mintPubkey is required: generate a mint keypair locally and pass its public key so you can sign the create tx. The API doe

  • crew_submit_signed

    Submit signed transactions from crew_build_unsigned. Pump.fun: sign create + fee-share lock together (signAllTransactions / Jito bundle) — fees lock at launch; do not submit create alone. Bags: Solana base64 (fee-share then create). Zora: EIP-1559 hex (0xSplits then coin create).

  • crew_discover

    Load CREW / CrewPay discovery for crypto agents: Autohire KOLs, launch Pump.fun / Bags / Zora / Clanker coins, fee-shares, OpenAPI links. Use this first when working on Solana meme coins, KOLs, or CrewPay.

  • crew_job_create_dry_run

    Plan a paid campaign job (multichain, per-proof payouts). Includes flop-devnet + FLOP. Test/devnet only; no funds moved. Community flop-htlc adapter, no partnership.

  • crew_job_create

    Persist a campaign or content job. Use chainId=flop-devnet and asset=FLOP for the community flop-htlc rail. Non-custodial — fund separately. No partnership.

  • crew_job_fund

    POST /jobs/:id/fund. flop-devnet requires body.to (payee SS58) and from (funder SS58). Returns unsigned hasStation.openEscrow — sign locally. Never send keys or preimages. Fund the payee existential deposit first or claim fails PAYEE_DEAD_ACCOUNT.

  • crew_job_list

    List open/funded campaign jobs. Optional mint filter. Includes flop-devnet jobs when posted.

  • crew_job_payout

    POST /jobs/:id/payout after verify. flop-htlc returns unsigned hasStation.satisfyEscrow. Non-custodial — never send keys or preimages.

  • crew_job_refund

    POST /jobs/:id/refund after the deadline. flop-htlc returns unsigned hasStation.refundEscrow. Non-custodial.

  • crew_claim_key

    Mint a crew_ak_… agent API key with no operator signup (POST /api/agent/keys/claim). Optional referral_code (or CREWPAY_REFERRAL_CODE env) permanently binds a KOL referrer — referred launches use fee map 60/15/5/20. Returns the secret once — store it as CREW_AGENT_API_KEY or pass

  • crew_search_kols

    Search the CREW KOL / Pump profile directory by handle or wallet. Prefer manual crew selection from this directory; Autohire is a fallback/convenience.

  • crew_list_kols

    List/browse CREW KOL profiles (optionally filtered by q). Use this to select explicit crew wallets before launching on pumpfun, bags, or zora. Manual pick first; Autohire is a fallback. For Zora, prefer registered evm_wallet / pass Base addresses.

  • crew_autohire

    The launching agent earns 15% of creator fees onchain. Creator fees follow trading volume and can be zero. Preview convenience Autohire: match a token name/ticker/vibe to a candidate KOL pack. Prefer explicit crew selection via crew_list_kols; Autohire is a fallback. Works keyles

  • crew_notify_hired_crew

    DM hired KOLs via @CrewPay_Bot. Opt-in only: they must have linked Telegram, sent /start, and enabled alerts. Never uses channel member counts.

  • crew_launch_dry_run

    The launching agent earns 15% of creator fees onchain. Creator fees follow trading volume and can be zero. Dry-run a launch (default) or wire-fees (intent=wire-fees). platform defaults to pumpfun; bags/zora check enablement (BAGS_API_KEY / ZORA_ENABLED) without sending chain txs.

  • crew_status

    Check whether a CREW mint has fee-shares locked, Holder KOL open, and board presence. New launches lock fees at launch. Use after submit, or before repair (crew_wire_fees) / lock / crank.

  • crew_wire_fees

    Create and permanently lock Pump.fun fee-sharing shareholders on an existing mint (POST /api/agent/wire-fees). When to use: repair-only for older launches or crew_status showing no fee-sharing config / a failed lock (custodial HTTP 202 / feeShareLocked=false). Optional gated flow

  • crew_list_launches

    Return launches attributed to your crew_ak_… key (mint, ticker, feeShareLocked, pumpUrl). Operator env keys see recent board launches. Use after crew_launch or to recover mint state across retries.

  • crew_lock_holder_kol

    Scan top holders ∩ CREW KOL directory and permanently lock fee-shares (one-shot). Use when launch used holderKol=true. Requires CREW_LAUNCHER_KEY in MCP env.

  • crew_crank_remits

    Distribute accrued creator fees (sweep + distributeCreatorFeesV2). Permissionless on-chain — uses CREW_LAUNCHER_KEY if set, else server CREW_OPS_KEY. Prefers OnlinePumpSdk builder so unswept bonding-curve fees do not fail with CreatorFeesNotSwept.

  • crew_proof

    Read the public CrewPay proof tape (GET /api/proof): fee-share-locked launches, creator-fee remits, and buyback runs. When to use: after a launch or crew_crank_remits, to show public proof that remits posted, or to inspect tape totals. No API key. When not to use: do not use for

  • crew_launch

    The launching agent earns 15% of creator fees onchain. Creator fees follow trading volume and can be zero. MAINNET custodial launch: Prefer explicit crew[] (from crew_list_kols). Autohire is a fallback convenience. Creates a Pump.fun coin and locks fee-shares at launch (60/15/25

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account fxams, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 227 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 22 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 32712 servers in this category
  • Published to the registry more recently than 72% of the other 32712 servers in this category
  • Basic checks equal to or better than 100% of the other 32712 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is CREW / CrewPay safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CREW_AGENT_API_KEY, CREW_LAUNCHER_KEY, X402_EVM_PRIVATE_KEY, x-crew-api-key

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.2.14) reached the registry 14 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Aiterm MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Aiterm MCP

by kitepon

Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

CREW / CrewPay

AI agents hire KOLs. Humans get paid. Launch coins on Pump.fun, Bags.fm, Zora, and Clanker (Base) with on-chain creator fee-shares (60% KOL crew / 15% launching agent / 25% treasury, or 60/15/5/20 when the agent claimed a key with a KOL referral code).

Live: crewpay.dev · API api.crewpay.dev · MCP mcp.crewpay.dev/mcp

Features

  • Auto-hire a KOL crew (narrative match; prefer registered / opt-in KOLs)
  • Non-custodial unsigned launches — CrewPay never holds the launcher key
  • Dry-run plus a human approval link (dryRunId + approvalUrl)
  • KOL sign-up / opt-in at /register and referral codes (/r/ ). KOLs add a Solana payout wallet for Pump.fun / Bags.fm crews and an optional Base (0x) wallet on the desk for Clanker / Zora crews and Base referral payouts (signed with the Solana desk wallet).
  • Per-coin pages (/coin/{mint}) with a milestone timeline
  • Live coins (home) and All coins with live market data
  • Proof tape (including paid content-job receipts)
  • Jobs — paid content briefs (thread / meme / post). Agent picks the winner. Test/devnet only.
  • Agents earn — launching agents get 15% of creator fees onchain (fees follow volume and can be zero)
  • MCP: crewpay-mcp@1.2.14 on npm · hosted mcp.crewpay.dev/mcp
  • REST API + llms.txt
  • OpenClaw skill: openclaw skills install @fxams/crewpay
  • Official MCP Registry (io.github.fxams/crewpay-mcp) and Glama
  • x402 USDC on Base and Solana (when X402_SOLANA_PAY_TO is set) — Autohire $0.02, launch family $0.10 — listed on x402scan
  • Virtuals ACP offerings on Base (8453): Autohire $0.25, launch with crew $1.00
  • Jobs + escrow: testnet only (JOBS_ENABLED; production templates API is off). Paid content jobs reuse the same rails — no new escrow program, no mainnet.

For AI / crypto agents

GET  https://api.crewpay.dev/api/agent

GET https://crewpay.dev/llms.txt GET https://mcp.crewpay.dev/.well-known/mcp.json

Safe flow: discover → list_kols / autohire → build_unsigned (`mintPubkey` required for Pump) → signAllTransactions → submit_signed. Fees lock at launch. crew_wire_fees is repair-only. Custodial alternate: dry-run → launch. Prefer MCP:

npx -y crewpay-mcp@1.2.14

Env: CREWPAY_API_KEY (or CREW_AGENT_API_KEY) + dedicated low-SOL CREW_LAUNCHER_KEY in local MCP env — never as tool arguments or chat paste. Hosted: https://mcp.crewpay.dev/mcp

OpenClaw / ClawHub skill: skills/crewpay — openclaw skills install @fxams/crewpay — hire KOLs, dry-run first, open approvalUrl, then launch with dryRunId. Fee split 60/15/25 or 60/15/5/20 with a KOL referral.

Legacy alias: skills/crewpay-crypto-agent Discovery runbook: DISCOVERY.md · Framework plugins: packages/

Publish to ClawHub (maintainers)
npm i -g clawhub

clawhub login # GitHub device login — you do this interactively clawhub skill publish ./skills/crewpay \ --slug crewpay \ --name "CrewPay" \ --version 1.1.6 \ --changelog "Venues Pump.fun / Bags / Zora / Clanker; x402 Base + Solana" \ --categories integrations,finance,agents \ --topics "solana,pump-fun,kol,fee-share,mcp" \ --dry-run

When dry-run looks good, drop --dry-run to publish.

Official MCP Registry

See docs/mcp-registry-publish.md. Live name: io.github.fxams/crewpay-mcp (crewpay-mcp@1.2.14).

x402

Pay-per-call x402 v2 on Base mainnet USDC (eip155:8453) and optional Solana mainnet USDC (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp when X402_SOLANA_PAY_TO is set). Alternative to x-crew-api-key. Hosted MCP is not an x402 resource server.

Discovery

Listed on x402scan.

Paid routes (live prices)

MethodPathPrice
POST/api/agent/autohire$0.02
POST/api/agent/launch/unsigned$0.10
POST/api/agent/launch/submit$0.10
POST/api/agent/launch/dry-run$0.10
POST/api/agent/launch$0.10

Desk (humans)

cd agent/crew

npm install npm run dev

See agent/crew/DEPLOY.md · agent/crew/PRODUCT.md.

Packages

PathRole
agent/crewVite desk UI
agent/crew-apiAgent API + proof
agent/crew-mcpMCP server (crewpay-mcp)
services/acp-providerVirtuals ACP v2 provider worker (no-op unless ACP_ENABLED=1)

Virtuals ACP (agents hire CrewPay)

Live: GET https://api.crewpay.dev/api/platforms reports acp.enabled and x402.enabled. Production ACP is Base mainnet (chainId 8453). Listener: set ACP_INPROCESS=1 on crewpay-api or run services/acp-provider. Paying agent wallet = identity. Fee map unchanged. Launch jobs stay non-custodial (unsigned txs + crew_submit_signed). Hire UI: app.virtuals.io/acp.

This repo does not register an ACP agent, generate keys, or move funds.

Offerings
[

{ "name": "crewpay_autohire_kol_crew", "description": "Hire a KOL crew for an existing token via CrewPay Autohire. Deliverable is crew list JSON.", "priceUsd": 0.25, "requirements": { "required": ["mint", "platform", "budget"] } }, { "name": "crewpay_launch_with_crew", "description": "Unsigned launch txs (crew_build_unsigned) plus crew_submit_signed instructions. Non-custodial.", "priceUsd": 1.00, "requirements": { "required": ["name", "ticker"] } } ]

Operator setup
  1. Register a provider on app.virtuals.io/acp/new.
  2. Signers → + Add Signer. Put the Privy P-256 authorization key in ACP_SIGNER_KEY, the wallet id in ACP_WALLET_ID, and the 0x agent wallet in ACP_WALLET_ADDRESS (never logs, never commit). The signer is not a 32-byte hex key and does not derive the wallet.
  3. Add the two offerings (full JSON in services/acp-provider/README.md).
  4. ACP_ENABLED=1 ACP_CHAIN_ID=8453 and either ACP_INPROCESS=1 on crewpay-api, or npm start --prefix services/acp-provider.
Ask PopNx