7IT Solutions
7MapsOverviewLive chartStateReliableMethodologyVerifyFor agentsFor ownersNews

Your stdio MCP server crashed at startup once. Claude Code may remember it for 7 days.

By Lior AharonovFounder, 7IT Solutions ·

What happened

Claude Code 2.1.318, published to npm on 3 November at 21:55 UTC, stops re-probing stdio MCP servers that quit during the version probe at every start. A server that dies in under 3 seconds for its own reason is now pinned to the legacy handshake for 7 days. A call to a tool before it loads now returns the tool input schema.

Why it matters

Picture the release that crashed on boot for one afternoon. Claude Code may keep using the legacy handshake with your server on those machines for up to a week, even after you ship the fix.

What to do

Test your stdio server on 2.1.318 from a cold start, and make sure it never quits within 3 seconds of launch for a missing config or env value; log the error and keep running instead.

My take

Lior Aharonov
Founder, 7IT Solutions

A crash at startup used to cost you one launch. Now it can cost you a week. Fail loudly, but stay up.

Sources

Claude Code CHANGELOG, version 2.1.318raw.githubusercontent.com
npm: @anthropic-ai/claude-code 2.1.318registry.npmjs.org
claude-codemcpstdio

Researched with AI tools; every fact is checked against the linked sources.

7Maps news

Every 7Maps day is signed and chained to the day before.Verify in your browser