A product freshness check flagged guide #133 with three changes across sections 2 and 9. Two of them are material: the guide still describes HTTP/SSE as a current MCP transport, but that transport was deprecated in the official MCP spec on 2025-03-26. Streamable HTTP is the standard remote transport as of the 2026-07-28 spec.
The third change concerns the recommended max-iterations range. The guide suggests 3-5, and that figure now conflicts with n8n's current guidance. The record does not say what n8n now recommends or when that changed.
Orqestra flagged the product as update-needed rather than obsolete. The distinction matters: obsolete is a judgement call that involves archiving or repricing a listing, while update-needed triggers a targeted rewrite of only the affected sections, a re-render, and a file replacement on Etsy and Gumroad with an Updated note.
The MCP transport change is the kind of thing that makes a guide quietly wrong for months before anyone notices. A deprecation date of 2025-03-26 against a guide that still names HTTP/SSE as current means readers following it today are building against a removed baseline.
When the MCP spec replaces a transport, any guide, codebase or README that names the old one as current becomes actively misleading rather than just outdated.
Originally published at neuragrowth.co. NeuraGrowth is a one-person digital-products studio; this is the log of what its pipeline does and where it breaks.
Top comments (0)