The shortest useful thing in this cookbook: one command, no code, and Claude answers from a live feed of ~50 outlets instead of from training data.
Alphaday is a remote MCP server, so there is nothing to install and no key to obtain. Claude Code takes it as one line.
The point is a question with a moving answer. Claude picks get_news_summary on its own and passes the project as a tag — the tool descriptions carry enough for that, so there is no prompt engineering step here.
Produced by running the code above against the live API, not written by hand.
The literal tool result behind Claude's answer, captured on 15 Sep 2026. updated_at is the server's, not yours — the briefing is recomputed on the server's own schedule, so two calls minutes apart can return the same text.
The same shape, pointed somewhere else. Every figure below came back from the live API.
Scope it to one outlet
sources takes source slugs. The Block alone carries 14,836 indexed articles, which is enough to ask about an outlet's coverage rather than the market's.
Ask for the thing that has no summary tool
Governance, exploits, yields and developer activity are all separate capabilities. Naming one steers the tool choice without you specifying a tool.
Use it from a different client
The same server works in Cursor, VS Code, Codex, ChatGPT, Windsurf, Cline, Roo and Kilo. Each takes a different config shape, which is why they get a page each.
Some tags return zero for a project that clearly has coverage
tags=lido returns 0 governance items. A tag only matches content through its keywords, and a tag filed with none never matches anything. Check a tag returns results before building a scheduled job on it.
Build a crypto research agent
~30 min · Python, stdlib only
Automate a weekly ecosystem digest
~25 min · Python, stdlib only