Connect ChatGPT to Alphaday

No config file — a UI flow. Note the naming has changed: what older guides call Connectors is now Apps, and the path runs through developer mode.

No API key No signup Remote HTTP, no local process

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 ChatGPT 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.

A Pro, Business, Enterprise or Edu plan. Custom MCP apps are not on the free or Plus tiers.
ChatGPT on the web. The mobile apps do not support custom MCP apps at all.
Developer mode switched on under Settings → Apps → Advanced Settings.

Set it up

Developer mode

Settings UI

1Settings → Apps → Advanced Settings → turn on Developer mode
2Settings → Apps → Create
3Enter the endpoint: https://api.alphaday.com/mcp
4Leave the authentication mechanism unset — the server needs none
5Scan Tools, then Create

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.

In ChatGPT

Composer

1Start a new chat
2Open the + menu in the composer
3alphaday should be listed among the available apps, and selectable

The app in the composer menu with its tools discovered. If Scan Tools returned nothing during setup, the app is created but inert — rescan rather than recreating it.

Or test the endpoint directly

This is the first message of the MCP protocol, sent by hand. If it answers, the server is reachable from your machine and every remaining problem is on the ChatGPT side.

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"}}}'

Expected response

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

The version number moves; "name":"alphaday" is the part to look for. The response also carries an mcp-session-id header, which is what a client reuses for every later call.

Try it

Ask these in a new chat with the app enabled from the `+` menu. 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.

Things that catch people out

Web only. MCP apps do not work in the ChatGPT mobile apps.
Agent mode will not use custom apps at all.
Available on Pro, Business, Enterprise and Edu; still labelled beta on the business plans. Read and fetch only on individual plans — fine here, since Alphaday exposes no write tools.
ChatGPT warns that third-party servers are unverified during setup. Expected, not a failure.
Search and fetch tools are no longer required, despite what older guides say.

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.

There is no Create option under Settings → Apps.

Developer mode is off, or the plan does not include custom apps.

Turn on Developer mode in Advanced Settings first. If that toggle is absent, the plan is the blocker.

Scan Tools finds nothing.

Usually a typo in the endpoint, or a trailing slash — /mcp/ is a different path and returns 404.

Re-enter the URL with no trailing slash, then rescan.

The app works in a normal chat but is ignored in agent mode.

Documented behaviour — agent mode does not use custom apps.

Use a standard chat. There is no setting that changes this.

A warning says the server is unverified.

Shown for every third-party MCP server.

Expected. Continue.

Opening the endpoint in a browser returns {"detail": "Bad Request"}.

A browser sends a GET. MCP is JSON-RPC over POST, so a 400 here is the server working correctly — there is no page to serve at an MCP endpoint.

Nothing. A 400 on a plain GET is the expected response, and it confirms the server is reachable.

404 {"detail": "Not Found"}.

The URL has a trailing slash, or a path appended. /mcp/ and /mcp/sse are both distinct routes from /mcp, and neither exists.

Use the endpoint exactly as written, with no trailing slash and nothing after it.

The server shows as connected, but the model never calls it.

Not a connection problem. Most clients only call tools in an agent mode, and several ship new tools unticked or capped.

Switch to the client's agent mode, confirm the Alphaday tools are enabled in its tool picker, and ask something that cannot be answered without live data.

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:

Security exploits

180+ on-chain exploits and hacks, each with a written incident record.

Developer activity

3,000+ GitHub activity snapshots — commits and contributors per coin.

Kasandra

AI-detected chart patterns with a bullish/bearish signal and confidence score.

TVL yields

32,000+ DeFi yield pools with base and reward APY, TVL and IL risk.

News

Real-time news from 49 crypto outlets — 440,000+ articles, tagged and deduped.

Forum

59 governance forums — 60,000+ posts — behind one endpoint.

Blogs

133 project blogs — 19,000+ posts — in one feed.

Podcasts

118 crypto podcast feeds — 22,000+ episodes, each with its audio URL and duration.

Videos

121 YouTube channels — 34,000+ videos — timestamped.

Market coins

Prices, metadata, history and trending movers for the top coins.

Coin categories

700+ token categories; about half carry a market-cap aggregate.

Exchanges

140+ centralized exchanges with trust scores and volume.

On-chain DEXes

700+ DEXes with the chains and protocols behind them.

TVL fees

2,000+ protocol fee and revenue records across DeFi.

TVL stablecoins

400+ stablecoins — peg type, mechanism and circulating supply.

DAO

Live Snapshot proposals across 51 DAOs.

Events

6,000+ conferences, meetups, hackathons and side events.