MCP Explained
- ID
- 43826
- Status
- summarized
- Published
- 05 Nov 2026, 10:08 PM
- Fetched
- 06 Nov 2026, 10:42 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://mcp-explained.com/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 06 Nov 2026, 10:42 PM
- Tags
- Audience
- developersvibe_codersai_ml_learnersai_agent_users
What happened
MCP Explained is an interactive lesson site for the Model Context Protocol, covering hosts, servers, and models, and stressing that MCP is not REST: it uses JSON-RPC over stdin/stdout or a single HTTP endpoint, and servers can talk back. It includes a spec 'time machine' and message-flow diagram referencing MCP spec 2025-11-25, with a note that token counts are illustrative. The site was made by Runlayer, described as 'the operating layer for AI,' and the Hacker News thread has 316 points and 133 comments.
Why it matters
Use this as an onboarding aid when explaining MCP to developers: the concrete point to carry into design reviews is that JSON-RPC is only the envelope, while MCP defines methods, capability negotiation, transports, and auth. Because the text does not describe what changed in spec 2025-11-25, verify implementation decisions against the official spec rather than treating this explainer as a changelog.
Discussion angle
Where should the auth boundary sit when an MCP server can call back into the host—inside the server, at the host, or in the transport—and what breaks first in a stdio versus HTTP setup?