Every morning · X, Substack & more
The yield strategies DeFi community recommends, collected in one place.
MorningYield reads a hand-picked list of DeFi yield accounts and newsletters every morning, pulls out each vault and strategy they recommend, and lists it here with who recommended it and when. Vote on the ones you'd use, and save the ones worth keeping. But don't forget to DYOR!
How it works
- 1
Read
Every morning the scout reads new posts from DeFi yield accounts on X and from newsletters on Substack and elsewhere. Replies and reposts are skipped.
- 2
Extract
It keeps only concrete yield opportunities — a vault, an automated strategy, or a recipe you run yourself — with the claimed APY and a link to the post. Token picks, trading calls and airdrop quests are left out.
- 3
You decide
Vote 👍 or 👎 on what you'd actually use, and save favourites to come back to.
What it collects
Most liked
Latest finds
Discovered
Yield strategies that DeFi writers on X, Substack and more are recommending — all of them, or one morning's scan at a time. Vote on the ones you'd use, and star the ones to keep.
Favorites
Strategies you've starred. They're saved in this browser only — no account needed.
Sources
The X accounts, newsletters and Telegram channels MorningYield reads every morning, and how much each one actually finds.
Request a source
Know an X account, newsletter or Telegram channel that posts yield strategies worth reading? Suggest it. If someone already asked for it, your request counts as a +1.
Requested sources
MCP & API
Read MorningYield from your own tools: connect an AI assistant over MCP and ask it about the strategies, or call the JSON API. Both are free and read-only, and both take a key, which you get right here.
Get a key
Tell us who you are and how to reach you, and your key appears here straight away.
Your key. Copy it now: we keep only a fingerprint of it, so we can't show it again. If you lose it, get a new one here.
The examples below now carry it.
Only we see what you write here. We use it to know who holds a key and to reach you about it. Privacy notice
Connect an AI assistant
MorningYield is a remote MCP server at this address. Put your key where the examples say YOUR_KEY.
{origin}/mcpClaude
On claude.ai or in the Claude app, open Settings → Connectors → Add custom connector and paste the address with your key at the end:
{origin}/mcp?api_key=YOUR_KEYClaude Code
Run in a terminal:
claude mcp add --transport http morningyield {origin}/mcp --header "Authorization: Bearer YOUR_KEY"Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"morningyield": {
"url": "{origin}/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}VS Code
Add to .vscode/mcp.json:
{
"servers": {
"morningyield": {
"type": "http",
"url": "{origin}/mcp",
"headers": {
"Authorization": "Bearer YOUR_KEY"
}
}
}
}Any other MCP client works the same way. The transport is Streamable HTTP, and the key goes in an Authorization: Bearer header or, for a client that takes only an address, in ?api_key= at its end. A client that only runs local servers can bridge with npx mcp-remote {origin}/mcp --header "Authorization: Bearer YOUR_KEY".
Things to ask
- What new stablecoin vaults did MorningYield find this week?
- Which strategies on Base were recommended by more than one source?
- What did yesterday's scan find, and which posts recommended each strategy?
- Which vaults claim the highest APY, and what caveats did their posts note?
- List the delta-neutral and lending strategies on Solana, newest first.
JSON API
The same data as JSON over HTTPS, from any language or straight from a browser. Everything is a GET under this address, with your key in an Authorization header:
{origin}/api/v1For example, the five most-mentioned vaults on Base:
curl -H "Authorization: Bearer YOUR_KEY" "{origin}/api/v1/strategies?type=vault&chain=Base&sort=most_mentioned&limit=5"For code generators and API clients there is an OpenAPI description, which needs no key.
What you can read
Each of these is both an MCP tool and an API endpoint, with the same parameters and the same answer.
Good to know
- The data changes once a day, after the morning scan, so there is no point in polling: keep a copy on your side.
- Your key is yours: don't publish it or share it. If it gets out, tell us to switch it off and get a new one here.
apy_claimedis the yield the author stated in the post. It is not measured or verified.- The collection is automated and can be wrong. It is not investment advice.
- If you publish something built on this data, credit MorningYield with a link.
- Missing a field, or something looks off? Tell @MorningYield on X.
Privacy notice
Last updated 15 October 2026 · version 2
Who we are
MorningYield (morningyield.com) is responsible for the personal data described here. Questions and requests: privacy@morningyield.com.
Your data on this device
What we collect, why, and for how long
- Votes
- When you press 👍 or 👎, your browser sends a random voter ID it created (not linked to your name, email or wallet), the strategy and your vote. We store them with a salted hash of your IP address to spot vote-stuffing, and clear that hash after 90 days. Legal basis: our legitimate interest in running fair community votes (Art. 6(1)(f) GDPR). Kept until you remove the vote.
- Source requests
- When you request a source, we store the source, your optional note, your browser's random voter ID and a salted hash of your IP address (to limit abuse; cleared after 90 days). The public list shows only the source, how many people asked and its status — never your note. New requests and their notes are posted to our team's Slack. Legal basis: our legitimate interest in running the feature you use (Art. 6(1)(f)). Kept until you remove it (the button above removes your requests too) or we decline the source.
- API keys
- When you get an API key, we store the name, the contact and the note you give us, a fingerprint of the key (not the key itself) and a salted hash of your IP address (to limit abuse; cleared after 90 days). Only we see them; each new key is reported to our team's Slack. We use the contact only to reach you about your key. Legal basis: our legitimate interest in running the feature you use (Art. 6(1)(f)). Kept while your key is active; write to us to have them deleted, which switches the key off.
- API and MCP use
- When your key is used, we record the time of its first and latest call, a running count of its calls, and how many calls it made in each hour, to see which keys are in use. We don't store what was asked. Legal basis: our legitimate interest in running the service (Art. 6(1)(f)). Kept with the key; the hourly counts are deleted after 13 months.
- Favourites and view settings
- Kept in your browser's local storage. They never leave your device.
- Analytics — on unless you turn it off
- Unless you turn it off, Google Analytics 4 records page views and usage data such as device, browser and approximate location, and sets the cookies
_gaand_ga_Z0SSDPL1C7(up to 2 years). It starts when you open the site, before you answer the cookie banner. Google Signals and ad personalisation are off. Turning it off in stops it and deletes these cookies. Legal basis: our legitimate interest in understanding how the site is used (Art. 6(1)(f)); you can object at any time by turning it off. Kept by Google for at most 14 months. - Visit notifications
- When a page opens, our server posts the page name and your country to our team's Slack, plus the campaign tag (
utm_campaign) of the link you followed if it carries one. The country comes from your IP address at our host; the address itself isn't stored or passed on. No cookies, no identifiers. Legal basis: legitimate interest in knowing how the site is used (Art. 6(1)(f)). Kept in our Slack workspace. - Consent records
- When you choose in the cookie banner, we store your choice, the version of this notice and the time, under a random consent ID kept in your browser — no IP address — so we can show what you chose. Legal basis: legal obligation (Art. 6(1)(c)). Kept for 3 years.
- Server logs
- Our hosting provider processes IP addresses and request details to deliver the site and protect it from abuse. Legal basis: legitimate interest (Art. 6(1)(f)). Kept briefly, under the provider's policy.
Who processes data for us
- Vercel — hosting (USA)
- Supabase — database, hosted in the EU (Ireland)
- Google — analytics, unless you turn it off (Ireland / USA)
- Slack — visit notifications (USA)
Transfers to the USA rely on the EU–US Data Privacy Framework or the European Commission's standard contractual clauses. We don't sell data, show ads, or make automated decisions about you.
Your rights
You can ask to access, correct or delete your data, to restrict or object to its use, and to receive it in a portable format. You can turn analytics off at any time; that doesn't affect what happened before. You can also complain to your data protection authority. We don't know who you are, so include your voter ID or consent ID (shown above) when you write to us — or remove your votes yourself with the button above.
Changes
If this notice changes in a way that affects your choice, the cookie banner asks you again.