Exa MCP Hosted

Latest Audit Result

exa-mcp-server (hosted at mcp.exa.ai) declares exa-js ^2.8.0 in package.json while the latest published exa-js is 2.12.1, so the SDK pin is outdated by 4 minor versions. Endpoint coverage: /search (web_search_exa, web_search_advanced_exa, deepSearch, peopleSearch, linkedInSearch, companyResearch), /contents (web_fetch_exa), /research/v1 (deep_researcher_start/check), /context (get_code_context_exa). There is NO /answer endpoint usage anywhere in the codebase, so the declared 'answer' capability is not actually implemented as a tool — only the deprecated deep_search_exa returns synthesized answers via /search. find_similar is correctly listed as missing — confirmed: no findSimilar/find_similar usage. Search types in code are 'auto' / 'fast' / 'instant' (and 'deep'/'deep-reasoning' for deepSearch); the declared 'neural' type is not used anywhere. Content options actually passed: highlights (webSearch, max 2000 chars), text (webFetch, configurable maxCharacters), plus webSearchAdvanced exposes summary, livecrawl, includeDomains/excludeDomains, dateRanges, subpages — these are richer than the declared 'text, highlights' but webSearchAdvanced is gated off by default. Default-enabled tools (hosted): web_search_exa and web_fetch_exa only; all other tools (including deep researcher, deep_search, company_research, people_search, linkedin_search, exaCode, advanced search) are disabled by default and most are explicitly marked Deprecated. Recommendation: bump exa-js to 2.12.1, remove 'answer' and 'neural' from declared capabilities (or implement them), and update declared content options to include summary/livecrawl when web_search_advanced_exa is enabled.

Missing Features (3)

• find_similar
• answer endpoint (declared but no /answer call in code; deep_search synthesizes answers via /search and is deprecated/disabled by default)
• neural search type (declared but not implemented; code only uses auto/fast/instant)