Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CREW / CrewPay

REMOTE · MCP.CREWPAY.DEV · 2 COMPONENTS

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

66 Trust /100

Last scanned (13 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 52% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 +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.

  • 16 Oct 26 +1
    • Tool “crew_build_unsigned” rewrote its description, which is the text the model reads security
    • Server version: 1.2.8 → 1.2.9 functional
  • 14 Oct 26 +1
    • New tool “crew_notify_hired_crew” functional
  • 13 Oct 26 0
    • Tool “crew_build_unsigned” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://mcp.crewpay.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.crewpay.dev CN=WE1,O=Google Trust Services,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA256 65a72758519691c41307fda9cfac8044
SANs: mcp.crewpay.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.crewpay.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
crewpay.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.crewpay.dev/mcp Verified 200
http (plaintext) http://mcp.crewpay.dev/mcp HTTPS enforced 301 https://mcp.crewpay.dev/mcp
MCP tools · 16 exposed · ~2,525 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
crew_autohire ~127

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.

NameTypeReqDescription
descriptionstring–Narrative / vibe (≤204 — leaves room for “Launched from CrewPay.dev platform”)
namestring–Token name (2–32 on launch)
seatsinteger–Crew seats 1–8 (default 5)
tickerstring–Token ticker (2–13 on launch)

No output schema declared.

No examples provided.

crew_build_unsigned ~421

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.

NameTypeReqDescription
crewarray––
descriptionstring––
imageBase64string––
imageUrlstring––
initialBuySolnumber––
launcherKeystring–FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
launcherPubkeystringyes–
mintPubkeystring––
modestring––
namestringyes–
optInOnlyboolean––
platformstring–Launch venue. Default pumpfun. bags=Bags.fm (Solana). zora=Zora coins (Base).
privateKeystring–FORBIDDEN — rejected if set.
seatsinteger––
secretKeystring–FORBIDDEN — rejected if set.
tickerstringyes–
treasuryBpsinteger––
twitterstring––
websitestring––

No output schema declared.

No examples provided.

crew_claim_key ~203

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.

NameTypeReqDescription
agentNamestring–Your agent name for the label
labelstring–Key label (default agent)
modelstring–Model id e.g. claude, gpt, grok
referral_codestring–KOL referral code (crewpay.dev/r/<code>). Bound permanently on this key. Falls back to CREWPAY_REFERRAL_CODE env.

No output schema declared.

No examples provided.

crew_crank_remits ~139

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.

NameTypeReqDescription
launcherKeystring–FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
mintstringyes–
privateKeystring–FORBIDDEN — rejected if set.
secretKeystring–FORBIDDEN — rejected if set.

No output schema declared.

No examples provided.

crew_discover ~59

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crew_launch ~383

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.

NameTypeReqDescription
agentModelstring–e.g. claude, gpt, gemini, grok
agentNamestring––
agentObjectivestring––
crewarray–Explicit crew (shares must total 100%) overrides Autohire when provided
descriptionstring–≤204 chars; attribution appended to reach ≤240 final
dryRunIdstring–Optional unless the API key has requireApproval=true
holderKolboolean–Open Holder-KOL (fees unlocked until crew_lock_holder_kol)
idempotencyKeystring–Retry-safe key; replays cached launch for 15m
imageBase64string––
imageUrlstring–Public image URL (or use imageBase64)
initialBuySolnumber–Dev buy 0–10 SOL (site+API aligned)
launcherKeystring–FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
modestring––
namestringyes–
privateKeystring–FORBIDDEN — rejected if set.
seatsinteger–Autohire seats when crew omitted
secretKeystring–FORBIDDEN — rejected if set.
tickerstringyes–
twitterstring–X / Twitter handle or URL
websitestring––

No output schema declared.

No examples provided.

crew_launch_dry_run ~337

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.

NameTypeReqDescription
agentModelstring––
agentNamestring––
agentObjectivestring––
crewarray––
descriptionstring–≤204 chars; attribution appended to reach ≤240 final
holderKolboolean––
imageBase64string––
imageUrlstring–Public image URL (or use imageBase64)
initialBuySolnumber––
intentstring–launch (default) or wire-fees
launcherKeystring–FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
launcherPubkeystring–Optional public launcher address for balance check (never a secret)
mintstring–Required when intent=wire-fees
modestring––
namestring––
platformstring––
privateKeystring–FORBIDDEN — rejected if set.
seatsinteger––
secretKeystring–FORBIDDEN — rejected if set.
tickerstring––
twitterstring––
websitestring––

No output schema declared.

No examples provided.

crew_list_kols ~113

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.

NameTypeReqDescription
limitinteger–Max results (default 50)
offsetinteger–Offset for pagination (default 0)
qstring–Optional: handle, pump username, or wallet substring

No output schema declared.

No examples provided.

crew_list_launches ~60

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.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

crew_lock_holder_kol ~137

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.

NameTypeReqDescription
launcherKeystring–FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
mintstringyes–
modestring––
namestring––
privateKeystring–FORBIDDEN — rejected if set.
secretKeystring–FORBIDDEN — rejected if set.
tickerstring––

No output schema declared.

No examples provided.

crew_notify_hired_crew ~92

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

NameTypeReqDescription
handlesarray–Optional hired handles if mint is omitted
messagestring–Optional short note (≤500)
mintstring–Coin mint — notifies that launch’s hired crew

No output schema declared.

No examples provided.

crew_proof ~74

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.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

crew_search_kols ~71

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

NameTypeReqDescription
limitinteger–Max results (default 20)
qstringyesHandle, pump username, or wallet substring

No output schema declared.

No examples provided.

crew_status ~55

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.

NameTypeReqDescription
mintstringyesPump mint address

No output schema declared.

No examples provided.

crew_submit_signed ~75

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.

NameTypeReqDescription
platformstring––
signedarrayyes–

No output schema declared.

No examples provided.

crew_wire_fees ~179

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.

NameTypeReqDescription
crewarray–Optional — omit to reuse board crew from launch
dryRunIdstring–Optional unless the API key has requireApproval=true
launcherKeystring–FORBIDDEN — rejected if set. Use CREW_LAUNCHER_KEY in MCP env only.
mintstringyes–
modestring––
namestring––
privateKeystring–FORBIDDEN — rejected if set.
secretKeystring–FORBIDDEN — rejected if set.
tickerstring––

No output schema declared.

No examples provided.

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.

remote · mcp.crewpay.dev

# add to Claude Code
claude mcp add --transport http fxams-crewpay-mcp 'https://mcp.crewpay.dev/mcp'
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.