Remote MCP · Endpoint

CREW / CrewPay MCP server

No. CREW / CrewPay answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.crewpay.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.fxams/crewpay-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
273 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Unsigned Pump/Bags/Zora/Clanker launches. mintPubkey required. Fees lock at launch.
Listing
From the official MCP registry (active).
Recent checks of CREW / CrewPay
CheckedResultHandshake
1 hour agoHandshake completed273 ms
1 day agoHandshake completed142 ms
2 days agoHandshake completed157 ms
3 days agoHandshake completed128 ms
4 days agoHandshake completed155 ms
5 days agoHandshake completed146 ms
7 days agoHandshake completed174 ms
10 days agoHandshake completed131 ms
12 days agoHandshake completed280 ms
14 days agoHandshake completed363 ms
17 days agoHandshake completed141 ms
19 days agoHandshake completed165 ms
21 days agoHandshake completed138 ms
23 days agoHandshake completed152 ms
25 days agoHandshake completed285 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CREW / CrewPay and makes no claim about it beyond what these checks measured.