# CREW / CrewPay (remote · mcp.crewpay.dev)

CrewPay MCP: Pump.fun/Bags/Zora unsigned launches with KOL Autohire and on-chain fee-shares.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mcp.crewpay.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/fxams-crewpay-mcp/mcp.md), [page](https://verifymcp.io/servers/fxams-crewpay-mcp/mcp)
- npm · `crewpay-mcp`: 70/100, [markdown](https://verifymcp.io/servers/fxams-crewpay-mcp/crewpay-mcp.md), [page](https://verifymcp.io/servers/fxams-crewpay-mcp/crewpay-mcp)

## Channel facts

- Endpoint: `https://mcp.crewpay.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.11`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (crew_submit_signed).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2582 tokens (~143/item across 18 items; 16 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 52% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CREW / CrewPay MCP server?

CREW / CrewPay is a hosted endpoint at https://mcp.crewpay.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http fxams-crewpay-mcp 'https://mcp.crewpay.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fxams-crewpay-mcp": {
      "url": "https://mcp.crewpay.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fxams-crewpay-mcp": {
      "type": "http",
      "url": "https://mcp.crewpay.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fxams-crewpay-mcp]
url = "https://mcp.crewpay.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fxams-crewpay-mcp": {
      "type": "remote",
      "url": "https://mcp.crewpay.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fxams-crewpay-mcp --url 'https://mcp.crewpay.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fxams-crewpay-mcp:
    url: "https://mcp.crewpay.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fxams-crewpay-mcp": {
      "Transport": "http",
      "Url": "https://mcp.crewpay.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fxams-crewpay-mcp -t streamable-http -u 'https://mcp.crewpay.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fxams-crewpay-mcp": {
      "type": "http",
      "url": "https://mcp.crewpay.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 65, +1)

- [security] Tool “crew_build_unsigned” rewrote its description, which is the text the model reads
- [functional] Server version: 1.2.8 → 1.2.9

### 2026-10-14 (score 64, +1)

- [functional] New tool “crew_notify_hired_crew”

### 2026-10-13 (score 63, 0)

- [security] Tool “crew_build_unsigned” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 63)

First indexed and scored.

## MCP tools (16)

### `crew_build_unsigned` (~421 tokens)

Build UNSIGNED launch transactions

Create UNSIGNED launch transactions. platform defaults to pumpfun (Solana v0 messages). bags = Bags.fm Solana fee-claimers (needs BAGS_API_KEY). zora = Zora content coins on Base (EIP-1559; needs ZORA_ENABLED). clanker = Clanker v4 on Base (EIP-1559; needs CLANKER_ENABLED). vibevibe = vibe/vibe on Robinhood Chain (EIP-1559; needs VIBEVIBE_ENABLED). sui = Memez.gg / Blast.fun on Sui testnet (sui-tx; needs SUI_ENABLED, two steps publish+pool, optional treasuryCapObjectId). Prefer explicit crew[] from crew_list_kols; Autohire is fallback. optInOnly default off. Fee map: 60% to the KOL crew, 15% to the launching agent, 25% to the treasury (5% referrer when bound). Optional treasuryBps 2000–3000.

Input parameters:

- `crew` (array)
- `description` (string)
- `imageBase64` (string)
- `imageUrl` (string)
- `initialBuySol` (number)
- `launcherKey` (string): FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
- `launcherPubkey` (string, required)
- `mintPubkey` (string)
- `mode` (string)
- `name` (string, required)
- `optInOnly` (boolean)
- `platform` (string): Launch venue. Default pumpfun. bags=Bags.fm (Solana). zora=Zora coins (Base).
- `privateKey` (string): FORBIDDEN — rejected if set.
- `seats` (integer)
- `secretKey` (string): FORBIDDEN — rejected if set.
- `ticker` (string, required)
- `treasuryBps` (integer)
- `twitter` (string)
- `website` (string)

### `crew_submit_signed` (~75 tokens)

Submit signed CREW launch transactions

Submit signed transactions from crew_build_unsigned. Pump.fun/Bags: Solana base64 (create then lock / fee-share then create). Zora: EIP-1559 hex (0xSplits then coin create). Pass platform to match the builder.

Input parameters:

- `platform` (string)
- `signed` (array, required)

### `crew_discover` (~59 tokens)

Discover CREW Agent API

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

### `crew_claim_key` (~203 tokens)

Claim a self-serve CREW API 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 as x-crew-api-key. Rate-limited 5/hour/IP. Default 5 launches/hour. Use before autohire/launch when you have no key.

Input parameters:

- `agentName` (string): Your agent name for the label
- `label` (string): Key label (default agent)
- `model` (string): Model id e.g. claude, gpt, grok
- `referral_code` (string): KOL referral code (crewpay.dev/r/<code>). Bound permanently on this key. Falls back to CREWPAY_REFERRAL_CODE env.

### `crew_search_kols` (~71 tokens)

Search CREW KOL directory

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

Input parameters:

- `limit` (integer): Max results (default 20)
- `q` (string, required): Handle, pump username, or wallet substring

### `crew_list_kols` (~113 tokens)

Browse CREW KOL directory

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.

Input parameters:

- `limit` (integer): Max results (default 50)
- `offset` (integer): Offset for pagination (default 0)
- `q` (string): Optional: handle, pump username, or wallet substring

### `crew_autohire` (~127 tokens)

Narrative Autohire KOLs

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 keyless for previews.

Input parameters:

- `description` (string): Narrative / vibe (≤204 — leaves room for “Launched from CrewPay.dev platform”)
- `name` (string): Token name (2–32 on launch)
- `seats` (integer): Crew seats 1–8 (default 5)
- `ticker` (string): Token ticker (2–13 on launch)

### `crew_notify_hired_crew` (~92 tokens)

Notify hired crew on Telegram

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

Input parameters:

- `handles` (array): Optional hired handles if mint is omitted
- `message` (string): Optional short note (≤500)
- `mint` (string): Coin mint — notifies that launch’s hired crew

### `crew_launch_dry_run` (~337 tokens)

Dry-run a CREW launch (no chain tx)

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. Prefer explicit crew[] from crew_list_kols; Autohire is a fallback. Returns dryRunId + approvalUrl. Requires CREW_AGENT_API_KEY.

Input parameters:

- `agentModel` (string)
- `agentName` (string)
- `agentObjective` (string)
- `crew` (array)
- `description` (string): ≤204 chars; attribution appended to reach ≤240 final
- `holderKol` (boolean)
- `imageBase64` (string)
- `imageUrl` (string): Public image URL (or use imageBase64)
- `initialBuySol` (number)
- `intent` (string): launch (default) or wire-fees
- `launcherKey` (string): FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
- `launcherPubkey` (string): Optional public launcher address for balance check (never a secret)
- `mint` (string): Required when intent=wire-fees
- `mode` (string)
- `name` (string)
- `platform` (string)
- `privateKey` (string): FORBIDDEN — rejected if set.
- `seats` (integer)
- `secretKey` (string): FORBIDDEN — rejected if set.
- `ticker` (string)
- `twitter` (string)
- `website` (string)

### `crew_status` (~55 tokens)

Mint / fee-share status

Check whether a CREW mint has fee-shares locked, Holder KOL open, and board presence. Use after launch (HTTP 202) or before wire/lock/crank.

Input parameters:

- `mint` (string, required): Pump mint address

### `crew_wire_fees` (~179 tokens)

Wire / repair CREW fee-shares

Create + lock fee-sharing for an existing mint. Approval is optional. Operators can require human approval per key (then pass dryRunId from intent=wire-fees after approvalUrl). Requires CREW_LAUNCHER_KEY in MCP env.

Input parameters:

- `crew` (array): Optional — omit to reuse board crew from launch
- `dryRunId` (string): Optional unless the API key has requireApproval=true
- `launcherKey` (string): FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
- `mint` (string, required)
- `mode` (string)
- `name` (string)
- `privateKey` (string): FORBIDDEN — rejected if set.
- `secretKey` (string): FORBIDDEN — rejected if set.
- `ticker` (string)

### `crew_list_launches` (~60 tokens)

List launches for this agent key

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.

Input parameters:

- `limit` (integer)

### `crew_lock_holder_kol` (~137 tokens)

Lock Holder-KOL fee-shares

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.

Input parameters:

- `launcherKey` (string): FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
- `mint` (string, required)
- `mode` (string)
- `name` (string)
- `privateKey` (string): FORBIDDEN — rejected if set.
- `secretKey` (string): FORBIDDEN — rejected if set.
- `ticker` (string)

### `crew_crank_remits` (~139 tokens)

Crank creator fee 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.

Input parameters:

- `launcherKey` (string): FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
- `mint` (string, required)
- `privateKey` (string): FORBIDDEN — rejected if set.
- `secretKey` (string): FORBIDDEN — rejected if set.

### `crew_proof` (~74 tokens)

Public CREW proof tape

Load public proof tape: launches, remit totals, and buyback runs if any. Fee-shares lock 25% to CrewPay treasury (20% when the launching agent is referred); market buyback cron is not live yet — empty buyback rows ≠ failed fee-shares.

Input parameters:

- `limit` (integer)

### `crew_launch` (~383 tokens)

Launch Pump coin via CrewPay (MAINNET)

MAINNET launch: Prefer explicit crew[] (from crew_list_kols). Autohire is a fallback convenience. Creates a Pump.fun coin with on-chain fee-shares (60/15/25 default; 60/15/5/20 with referral). Approval optional; requires CREW_AGENT_API_KEY + CREW_LAUNCHER_KEY. Check feeShareLocked.

Input parameters:

- `agentModel` (string): e.g. claude, gpt, gemini, grok
- `agentName` (string)
- `agentObjective` (string)
- `crew` (array): Explicit crew (shares must total 100%) overrides Autohire when provided
- `description` (string): ≤204 chars; attribution appended to reach ≤240 final
- `dryRunId` (string): Optional unless the API key has requireApproval=true
- `holderKol` (boolean): Open Holder-KOL (fees unlocked until crew_lock_holder_kol)
- `idempotencyKey` (string): Retry-safe key; replays cached launch for 15m
- `imageBase64` (string)
- `imageUrl` (string): Public image URL (or use imageBase64)
- `initialBuySol` (number): Dev buy 0–10 SOL (site+API aligned)
- `launcherKey` (string): FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
- `mode` (string)
- `name` (string, required)
- `privateKey` (string): FORBIDDEN — rejected if set.
- `seats` (integer): Autohire seats when crew omitted
- `secretKey` (string): FORBIDDEN — rejected if set.
- `ticker` (string, required)
- `twitter` (string): X / Twitter handle or URL
- `website` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fxams-crewpay-mcp/mcp#diagnostics

## Score history

- 2026-10-18: 66
- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 63
- 2026-10-12: 63

## Common questions

### What is the CREW / CrewPay MCP server?

CREW / CrewPay is an MCP server listed in the public MCP registry as io.github.fxams/crewpay-mcp. CrewPay MCP: Pump.fun/Bags/Zora unsigned launches with KOL Autohire and on-chain fee-shares. This page covers its hosted endpoint (https://mcp.crewpay.dev/mcp).

### Is the CREW / CrewPay MCP server safe to use?

CREW / CrewPay scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the CREW / CrewPay MCP server expose?

CREW / CrewPay exposes 16 tools: crew_build_unsigned, crew_submit_signed, crew_discover, crew_claim_key, crew_search_kols, and 11 more. Their descriptions and schemas cost roughly 2,525 tokens of context every time the server is loaded.

### Does the CREW / CrewPay MCP server require authentication?

No. We connected to CREW / CrewPay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CREW / CrewPay MCP server still maintained?

CREW / CrewPay is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.crewpay.dev/mcp
- Repository: https://github.com/fxams/crew
- Changelog RSS feed: https://verifymcp.io/servers/fxams-crewpay-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/fxams-crewpay-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/fxams-crewpay-mcp/mcp