I have 26 MCP servers live on Smithery. 61 npm packages. 61 Stripe payment links. The autonomous build pipeline ships a complete product in 90 seconds.
11 total installs. 92 npm downloads/week. £0.00 revenue.
The Build Gap vs The Distribution Gap
Building an MCP server in 2026 is solved. The pipeline is:
Prompt → TypeScript server → npm publish → Smithery deploy → Stripe product → GitHub repo → done
90 seconds. Zero human code. 61 products shipped this way.
Distribution has no equivalent pipeline. There is no npx distribution-pipeline.
What Distribution Actually Looks Like Right Now
Here's every channel I've tried, with real June 2026 numbers:
| Channel | Action | Result |
|---|---|---|
| Smithery | 26 servers listed, namespace vishar-rumbling
|
11 installs (organic, zero promotion) |
| npm | 9 monitored packages | 92 downloads/week (passive) |
| Dev.to | 10 articles in 4 days | ~12 total page views, 2 comments |
| YouTube Shorts | 13 shorts rendered + scheduled | 0 published (AiToEarn auth degraded 72+ hours) |
| TikTok | Same 13 shorts | 0 published (same auth block) |
| Image-text posts | All rejected (AiToEarn validation broken) | |
| Video + article posts | OAuth expired since May 14 |
Every build channel works perfectly. Every distribution channel is blocked or barely trickling.
The Uncomfortable Math
If AI makes building free, it also makes every builder's output indistinguishable. When anyone can generate an MCP server in 90 seconds, the market gets flooded with technically competent products that nobody finds.
The bottleneck shifts from "can you build it" to "can you make anyone care."
I can build faster than I can distribute. That's not a flex — it's a structural problem.
What I'm Actually Doing About It
- Dev.to content engine — One technical article per day. Real numbers. Real code. No AI slop. This is #11.
- npm as passive channel — Every package is a landing page with links to Smithery, GitHub, and Stripe. Zero cost, permanent shelf space.
- Smithery marketplace — The only channel with non-zero organic traction. 11 installs from zero promotion.
- Direct product pages — Stripe payment links on agentpay.so. When someone lands, they can pay immediately.
The Next Problem
Multi-platform publishing is fundamentally broken right now. AiToEarn's credential layer has been degraded for 72+ hours — every scheduled short across YouTube, TikTok, Instagram, and Facebook fails with "Account is not authorized." That's not a per-platform OAuth problem. It's a single-point-of-failure in the distribution stack.
When your publishing pipeline depends on one service's credential management, a server-side invalidation kills every platform at once. Lesson: if you're building autonomous distribution, you need per-platform direct API access. Aggregators are fragile.
61 products. 26 MCP servers. 11 installs. 92 npm downloads/week. £0.00 revenue.
Building in public at agentpay.so. Every tool free at smithery.ai/servers/vishar-rumbling.
Top comments (0)