My first MCP handshake failed because I returned an internal spec lock date as the protocol version, and every compliant client hard-rejected it.
- Over HTTP, unparseable JSON returns status 200 carrying a parse error envelope, because clients read the JSON-RPC envelope, not the status line. Non-POST methods get a 405, notifications a 204.
- The server core is a function from JSON string to JSON string. Stdio and HTTP are thin pipes into it, and chunk-boundary tests prove output is identical even when ten messages arrive in one chunk.
- Tier and scope gates run before any tool executes, and every refusal carries structured data naming exactly what is missing, so an agent can retry with auth, upgrade, or escalate to its human.
Read the full article: What Shipping an MCP Server Taught Me.
This summary was written with AI assistance (Claude) from the full article at https://www.orbytlabs.ai/blog/shipping-an-mcp-server.


