@nithin_k_anil@DrAIExpert the tell within the tell is which surface they shipped first. analytics, not ads, not search console. read-heavy query workloads. that tells you exactly where MCP has proven out and where the gaps still are.
Just published a deep dive on why AI reasoning has no addresses.
Every other system you debug has coordinates. Stack traces, span IDs, flame graphs. AI reasoning? You re-read an essay and hope the bug jumps out.
I built the fix. Here's what it looks like in practice.
๐ https://t.co/GOLmbqRQ8E
@freeCodeCamp Shipped a couple of MCP servers to npm & can confirm the gap is real.
No tutorial covers what happens when 3 agents hit the same state file or how schema validation fails silently. We need more of this.
@levelsio Half of the people saying MCP is dead are now putting tool lists in their Claude.md. That is a discovery manifest. It is less standardized MCP.
@rafalwilinski Correct for remote MCPs. Most deployments today are local stdio with zero auth in play. The OAuth case is real but not the majority use case yet. Yes, new paradigm be "shakey", but that doesn't mean we won't converge to something useful.
@TheGeorgePu Not just a wrapper. The distribution moat is real short-term. The question is whether Anthropic and OpenAI keep tolerating that margin compression.
@nicbstme@firecrawl@p0 CLI vs MCP conflates two problems: discovery (what tools exist?) vs invocation efficiency. CLI wins on efficiency. MCP wins on discovery. The bottleneck depends on your use case.
@harshbhatt7585@karpathy Reward specification is the bottleneck here, not the RL algo. Getting incremental returns in 24 experiments means the env modeling is actually decent and that's harder to build than the agent itself.
@Chris_Worsey@karpathy Killing the worst-Sharpe agent without regime weighting is the wrong selection pressure. Under drawdown, high-Sharpe agents look terrible. You're pruning the ones right about regime shifts.
@const_reborn Your constraint isn't compute cost, it's signal quality. Hyperliquid's order book is unusually clean. That edge disappears if the data layer degrades.
@aakashgupta Perplexity hosts an MCP server so Claude Desktop and Cursor can discover them. Internally, they run tight APIs which is rational for a production stack at $656M ARR. Two separate problems: developer discovery vs. internal execution. The CTO spoke to one of them.