👀🧠💰🤝 BEST STRATEGY FOR GAINS - Lower your IQ - Buy narratives early - Identify the leaders - Buy everything in that narrative & all new launches - Derisk your initial capital - Let the winners run - Don't sell the bottom of the 1st dip - Sell/take profits when leaders top/lose hype

Channel
MCP Crypto Updates
@mcp_crypto
On this record: Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
938subscribers
-11 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001312991014 |
|---|---|
| Type | Channel |
| Username | @mcp_crypto |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/mcp_crypto |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 13:52 | 938 | -9 |
| 14 Aug 2026, 12:56 | 947 | -2 |
| 6 Aug 2026, 23:00 | 949 | no change |
| 6 Aug 2026, 22:55 | 949 | first reading |
Engagement
20 posts held, back to 9 November 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 February 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
Getting into some small caps and launches Think 2023 small caps will be good to us while large caps figure out what they are going to do
BTC flips 21.5, alts send New micro cap launches will rip Risk on, but still high risk for new launches, b/c devs might hold out longer before dumping/rugging = safer/more time to take capital and profits out Need to focus on 2-3 chains for micro caps (Tier 1: ETH, SOL, ARB / Tier 2: BSC AVAX FTM ATOM MATIC) And pickup the free money on large/mid caps in top 100 that will go 50-100% if market stays up and BTC fl…
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
$BTC & $ETH What to do here? Buy here? Dumps 15% Don't buy here? Miss another 100% move up Up only no stops or pullback? Rally or fake out? Mini altszn soon? Simple: - Play it lvl by lvl - Find what starts trending - It's best to ride momentum & not think too hard about it
Plan Buy Q1 heavy (liquid / majors) Sell for 2-3x Q2-summer Stables up Then play small caps / micro trends till 2024 halving Load up on a Q1 pre-halving correction and let it ride and play new narratives
Set an alert & read this again when we're in peak bull season "I'm up 50x from my bear market bottom. Feels good. (*Screenshots portfolio balance.) I'm taking huge % into cash/stables now, so I can be rich 12-18 months into the next bear market & not feel like depressed shit."
SHI Took profits Hold and flip blue to continue or back down to fill low bids again
Spaces right now! Join 👇 📢🔥💰🔥💰🔥💰🔥💰🔥 Bullish on $ECC @EmpireCapital_ - Cross chain Dex - DeFi products - New L1 Blockchain - Roundable app (App store & product for the mass public) - Working products & revenue generating Will be huge this cycle 🤝 https://twitter.com/EmpireCapital_/status/1598440938657009668?t=4SNfXwwabd035pwdY6E_4A&s=19
I think buying the next dump and holding for a rally will be key to building capital to spread into small caps for next cycle ETH MATIC and a few others.. sell for 2-4x and wait correction and cheap prices again before BTC halving People want so bad to flip into a new bull so fast, I just want a pre-halving rally One step at a time If you're not preparing for a rally, you probably won't take profits and give back…
Showing the 12 most recent of 20 posts we hold for @mcp_crypto. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@mcp_crypto named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 22 August 2026 — this entry's latest reading, not the date you are reading this.
“MCP Crypto Updates” (@mcp_crypto), 938 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/mcp_crypto.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.