Unverified50% confidenceFactExact time
The 'spawn node ENOENT' error in MCP logs is usually because VSCode was not restarted after installing Node.js.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/2/2026
First Seen
Valid until: 1/31/2027
Sources
Related Entities
Related Claims
UnverifiedRunning the XCrawl MCP server via local stdio requires Node.js 18 or higher.65% similarUnverifiedNode.js recently released a security patch fixing a vulnerability that could lead to remote code execution (RCE).65% similarUnverifiedNode.js native modules (.node files) are bound to a specific Node.js ABI version at compile time, and a mismatch between compile-time and runtime versions causes memory layout misalignment that triggers segmentation faults.64% similarUnverifiedThe Verifox MCP server requires Node.js version 18 or newer, because newer versions of Node have more stable fetch, module resolution and subprocess behavior.64% similarUnverifiedn8n depends on the Node.js runtime, and different major Node.js versions have inconsistent support ranges for n8n; versions that are too new or too old may trigger native module compilation failures.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1125863API
curl https://kongchang.com/api/v1/knowledge/claims/1125863MCP
get_claim(id=1125863)