Connect Claude to Alphaday

What you're connecting to

One endpoint exposing 22 data capabilities across 57 pre-described tools — news, governance, DeFi, security and market data. It is a remote server, so there is no package to install, no process to keep alive and no key to obtain. That matters for Claude setup specifically: almost every MCP example online is command + args spawning a local binary, and none of it applies here.

https://api.alphaday.com/mcp

Before you start

The config below assumes all of this is already true. Most failed setups are one of these rather than a wrong field.

• For Claude Code: the claude CLI on your PATH, and a terminal open anywhere — servers added without --scope project are available in every directory.
• For Claude Desktop: a Connectors section under Settings → Customize. Custom connectors are plan-gated, so if that section is missing, the plan is the reason rather than the config.
• Nothing for the server itself. Alphaday is remote: no package, no local process, no key to obtain.

Set it up

Claude has more than one route in, and they are genuinely different rather than alternatives to the same thing. Use the one that matches the surface you work in.

claude mcp add --transport http alphaday https://api.alphaday.com/mcp

Check it worked

Confirm the connection before you go looking for a bug in your prompt. A server that is listed but not connected looks identical to a model that chose not to call it.

claude mcp list

alphaday listed with a connected status. Inside a session, /mcp shows the same thing plus the tool count. In Desktop, the connector appears in the composer's tool menu once the app has been fully restarted.

curl -s -X POST https://api.alphaday.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{
        "protocolVersion":"2025-06-18","capabilities":{},
        "clientInfo":{"name":"curl","version":"1"}}}'

{"jsonrpc":"2.0","id":1,"result":{
  "protocolVersion":"2025-06-18",
  "capabilities":{"tools":{"listChanged":false}, ...},
  "serverInfo":{"name":"alphaday","version":"1.30.0"}
}}

Try it

Ask these in any Claude Code session, or a new Desktop chat. Each one needs data the model cannot have — a live feed, an incident record, a yield table — so a good answer is proof the tools fired, not just that the server is listed.

• What's trending in crypto news right now, and what changed in the last 24 hours?
• Which DeFi pools are paying over 20% APY, and which of them carry real impermanent-loss risk?
• Summarise the three most recent on-chain exploits and what was taken.
• Compare GitHub developer activity for Solana and Sui over the last month.

When it doesn't connect

Symptom first, because that is what you have. The status codes below were produced against the live server rather than copied from elsewhere — if yours does not appear here, it is worth trusting that difference.

What you get once it's connected

22 datasets, reached by 57 tools — most datasets have a list form, a detail form and a trending form, which is why the two numbers differ. These four are the ones a general crypto API does not have:

All 22 capabilities are listed on the MCP overview, with the tool count behind each.