Serverdex error reference · read 21 November 2026
MCP error -32001: Request timed out: what it means and how to fix it
MCP error -32001: Request timed outThe client sent a request (usually initialize, tools/list or a tools/call) and no response arrived within its timeout. The server is alive but slow, blocked, or never answered that particular request.
Shown by: Claude Code · Claude Desktop · Cursor · JSON-RPC code -32001
Causes, most likely first — and the fix for each
1First start is slow: `npx` or `uvx` downloads the package before the server can answer the handshake.
Fix: Run the command once in a terminal so the package is cached, or install it globally and point the config at the binary. Then retry.
2The tool call itself is long-running (a crawl, a large query) and exceeds the client's per-call timeout.
Fix: Raise the timeout where the client allows it (Claude Code: `MCP_TIMEOUT` / `MCP_TOOL_TIMEOUT` environment variables, per its docs), or make the tool return partial results.
3A remote server accepted the connection but never answered (overloaded or hung behind a proxy).
Fix: Check the endpoint with the Serverdex live check; if it answers there in under a few seconds, the problem is on your network path.
Hosted servers failing this way right now
The Serverdex live check calls every listed hosted MCP server about once a day with a credential-free handshake. 18 listed servers last answered with timeout / und_err_connect_timeout / tools_rpc_-32001. If the one you are adding is here, the error is on the server's side today.
- Award Travel FinderMaps, Travel & WeatherLive★ 16
- Kaiva BridgeAPIs & IntegrationsLive★ 1
- SlimaContent & PublishingLive★ 1
- Synlake — Cloud Infrastructure for AI AgentsCloud & DevOpsLive
- Threadlinqs IntelligenceSecurity & IdentityLive
- ChemistryHealth & ScienceLive
- Emitd MCP ServerCommunicationLive
- Clearly WorkspaceBusiness & CRMLive
- Game Industry LibraryGames & SportsLive
- MSPStuff SwitchboardBusiness & CRMLive
- Placement APIFinanceLive
- JapanFoldBusiness & CRMLive
Test any endpoint yourself: MCP server health check · full list of hosted servers: remote MCP servers.
Still failing?
Work through the twelve general causes in order in MCP server not working: the causes, in order, check the exact config file path and shape for your client in the client setup guides, or generate a known-good config with the config generator.
Sources (read 21 November 2026)
Other MCP errors: MCP error -32000: Connection closed · MCP error -32601: Method not found · MCP error -32602: Invalid params · MCP error -32603: Internal error · MCP error -32600: Invalid request · HTTP 406 Not Acceptable from an MCP server · spawn npx ENOENT · spawn uvx ENOENT (and uv, docker) · Server transport closed unexpectedly · Client closed (Cursor) · No tools, prompts, or resources (Cursor) · Unexpected token … is not valid JSON · SSE error: Invalid content type, expected text/event-stream · Could not attach to MCP server (Claude Desktop) · Failed to reconnect to an MCP server (Claude Code) · MCP server needs authentication (401 Unauthorized) · MCP OAuth loop (infinite sign-in tabs) · Tools limited to 40 total (Cursor) · executable file not found in $PATH (Antigravity) · MODULE_NOT_FOUND / No module named mcp.server.fastmcp.