Connect Cline & Roo Code 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 Cline & Roo Code 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.

• The Cline or Roo Code extension in VS Code. Both ship their own MCP panel rather than using VS Code's.
• Knowing which of the two you are configuring. They share an ancestor and diverge on exactly the fields below, so a config that works in one is a plausible-looking failure in the other.

Set it up

Cline & Roo Code 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.

{
  "mcpServers": {
    "alphaday": {
      "type": "streamableHttp",
      "url": "https://api.alphaday.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

{
  "mcpServers": {
    "alphaday": {
      "type": "streamable-http",
      "url": "https://api.alphaday.com/mcp",
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

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.

1. 1Open the MCP Servers panel in the extension sidebar
2. 2alphaday should show a green indicator, not amber or red
3. 3Expand the server — the tool list should be populated

Green, with tools listed. Amber generally means it is still retrying the handshake; red with a 406 in the output means type holds the wrong one of the two spellings.

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 the extension's chat panel. 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.