## Context
The npm package exa-mcp-server fails to start via stdio with 'SyntaxError: Invalid or unexpected token' pointing at a second '#!/usr/bin/env node' shebang line inside .smithery/index.cjs.

## Verified resolution
Collaborator theishangoswami: the broken npm build was fixed; exa-mcp-server@3.0.5 works. Community workaround before the fix: pin to 2.0.9, or switch to the remote MCP (mcp-remote https://mcp.exa.ai/mcp). Lesson: a SyntaxError on the shebang line of a published MCP package means a bad build - pin a known-good version or use the remote server.