A stdio server prints a friendly startup banner before it begins handling requests. The host reports that the connection failed immediately. What happened?

Mediummcptransportsstdiodebugging

Last reviewed 22 Aug 2026

The banner's wording is the problem, so escaping it or making it valid text would let the connection through.
Nothing should have failed — the client discards anything on that stream that it cannot parse as a message.
The banner went to the stream reserved for protocol messages, and it is not a valid one.Correct answer
The timing is the problem, not the stream — output before the first request arrives is what the client rejects.

Show answer & explanation

Correct answer: C. The banner went to the stream reserved for protocol messages, and it is not a valid one.

Explanation

The principle — A reserved channel is reserved from the first byte.

Why the key is correct — On this transport the server reads JSON-RPC messages from stdin and writes JSON-RPC messages to stdout, and the rule that protects it is absolute: the server MUST NOT write anything to its stdout that is not a valid MCP message. A banner is text on that stream, so the client's reader meets something that is not a message where only messages are allowed. The fix is one line long and it is a change of stream, not a change of wording.

Why the others are wrong — The client is not obliged to tolerate stray output. Appearing before the first request does not put text outside the channel. And no amount of escaping turns a banner into a protocol message.

Remember this — On stdio, print statements are a protocol bug.

Sources — MCP first-party documentation.

Sources

Primary sourcestdio — MCP · accessed 20 Aug 2026
“The server MUST NOT write anything to its stdout that is not a valid MCP message.”
Primary sourcestdio — MCP · accessed 20 Aug 2026
“The server reads JSON-RPC messages from stdin and writes JSON-RPC messages to stdout.”

Practise 10 questions on this topic

Take MCP Fundamentals — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.

Start the test

A stdio server prints a friendly startup banner before it begins handling requests. The host reports that the connection failed immediately. What happened?

Mediummcptransportsstdiodebugging

Last reviewed 22 Aug 2026

The banner's wording is the problem, so escaping it or making it valid text would let the connection through.
Nothing should have failed — the client discards anything on that stream that it cannot parse as a message.
The banner went to the stream reserved for protocol messages, and it is not a valid one.Correct answer
The timing is the problem, not the stream — output before the first request arrives is what the client rejects.

Show answer & explanation

Correct answer: C. The banner went to the stream reserved for protocol messages, and it is not a valid one.

Explanation

The principle — A reserved channel is reserved from the first byte.

Remember this — On stdio, print statements are a protocol bug.

Sources — MCP first-party documentation.

Sources

Primary sourcestdio — MCP · accessed 20 Aug 2026
“The server MUST NOT write anything to its stdout that is not a valid MCP message.”
Primary sourcestdio — MCP · accessed 20 Aug 2026
“The server reads JSON-RPC messages from stdin and writes JSON-RPC messages to stdout.”

Practise 10 questions on this topic

Take MCP Fundamentals — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.

Start the test

A stdio server prints a friendly startup banner before it begins handling requests. The host reports that the connection failed immediately. What happened?

Related questions

A stdio server prints a friendly startup banner before it begins handling requests. The host reports that the connection failed immediately. What happened?

Related questions