MCP.Market

CREW / CrewPay MCP server

online · 100% uptime
by fxams·io.github.fxams/crewpay-mcp·v1.2.14

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

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed CREW / CrewPay yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

CREW / CrewPay tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How CREW / CrewPay compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
203 ms
faster than 63% of 30,031 servers

Release history: 4 versions in the registry since 2026-10-08, latest 2026-10-23, typically one every 4 days.

Install CREW / CrewPay in Claude Code, Cursor or VS Code

claude mcp add --transport http crewpay-mcp https://mcp.crewpay.dev/mcp
Add to Cursor

CREW / CrewPay: common questions

Is CREW / CrewPay MCP server safe?
Mostly: it is graded B (83/100). Read the CREW / CrewPay safety report
How do I install CREW / CrewPay?
It runs remotely at mcp.crewpay.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does CREW / CrewPay need an API key?
Yes. The registry entry asks for CREW_AGENT_API_KEY, CREW_LAUNCHER_KEY, X402_EVM_PRIVATE_KEY, x-crew-api-key.
Is CREW / CrewPay maintained?
The last commit was 26 days ago (2026-10-09). The latest release is v1.2.14.
Is CREW / CrewPay up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does CREW / CrewPay compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 203 ms (faster than 63% of 30,031 servers). Full comparison.