MCP server timeout: no answer to initialize or tools/list

A timeout means the server process is running but never answers on stdin and stdout. In our tests it happened when a server started an HTTP server instead of stdio, and when a server installed without its install scripts never answered tools/list.

Short answer

Run the command in a terminal. If it prints a http://localhost URL, it is an HTTP server: connect to that URL as a remote server, or start it in stdio mode if its README offers one. If you installed with scripts off, rebuild the package. In our data a large tool list alone did not cause a timeout.

Last tested 2026-11-11

How we test: methodology. Context cost: lowest context cost MCP servers. Not tested by us: security, output quality, and behaviour with real credentials.

Symptom

The client waits, then reports a timeout or that the server did not respond. The process is still running.

The exact output we saw

Server	What it printed (verbatim)	Where we saw it	Tested
PDF (MCP) `@modelcontextprotocol/server-pdf 2.0.4`	`MCP server listening on http://localhost:3001/mcp`	stdout at launch (an HTTP server, not stdio)	2026-11-10
PDF (MCP) `@modelcontextprotocol/server-pdf 2.0.4`	`timeout 45s`	our stdio client: no answer to initialize	2026-11-10
REA: Reverse Engineer Anything `rea-agents 6.7.0`	`timeout 45s`	our stdio client: initialize answered, tools/list did not (installed with npm --ignore-scripts)	2026-11-03

timeout 45s is our own stdio client's message: it waits 45 seconds for each answer.

Cause

HTTP mode instead of stdio. PDF (MCP) printed a localhost URL and waited for HTTP connections, so nothing ever answered our initialize on stdin (MCP spec, transports).
Installed without its install scripts. REA: Reverse Engineer Anything answered initialize but not tools/list after we reinstalled it with npm --ignore-scripts. In our earlier run (2026-10-24) it listed tools.

Large tool lists. In our data a big tool list was not, by itself, a reason for a timeout. SmartBear MCP returned 316 tools (approx. 230507 tokens, cl100k estimate, measured 2026-11-11), and our whole probe, from launch to the tools/list answer, took 10.7 s. A list that size can still crowd your model's context: see which MCP servers use the most context.

Fix

Run the command yourself and watch stdout. A working stdio server prints nothing there and waits for input. If it prints a URL, add that URL to your client as a remote server, or use the stdio option from its README. not tested by us
Rebuild after a scripts-off install: npm rebuild <package> (npm rebuild). not tested by us
Slow first start: if your client has a startup timeout setting, raise it while a server downloads or indexes on first run. not tested by us

Affected listings

PDF (MCP) (@modelcontextprotocol/server-pdf, tested 2026-11-10, status failed)
REA: Reverse Engineer Anything (rea-agents, tested 2026-11-03, status failed)

More troubleshooting: all troubleshooting pages · MCP error -32000: Connection closed · MCP servers that need an API key or sign-in. Quotes are verbatim from our own test logs (colour codes removed; a trailing … marks a shortened line). We have not run these servers inside Claude Code, Claude Desktop or Cursor.

FAQ

Why does my MCP server time out?

In our tests, either the server started in HTTP mode and never answered on stdin and stdout, or it was installed without its install scripts and never answered tools/list.

Do large tool lists cause MCP timeouts?

Not in our data. SmartBear MCP returned 316 tools (approx. 230507 tokens, cl100k estimate), and our whole probe from launch to the tools/list answer took 10.7 s, inside our 45 s limit.