3.4.1 → 3.4.2
patch release, 6 October 2026No tool definition changed.
MCP servers / exa-mcp-server
exa-mcp-server
3 of its last 5 updates changed what the agent reads: 4 tool descriptions rewritten, up to 3.4.2.
npm package · npm page · recorded on 24 October 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. Method and limits.
Release by release
3.4.0 → 3.4.1
patch release, 18 August 2026No tool definition changed.
3.2.1 → 3.4.0
minor release, 1 August 2026web_fetch_exa: input schema changed
web_search_exa: description and input schema changed
Before (3.2.1)
Search the web for any topic and get clean, ready-to-use content.
Best for: Finding current information, news, facts, people, companies, or answering questions about any topic.
Returns: Clean text content from top search results.
Query tips:
describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue".
Use category:people / category:company to search through Linkedin profiles / companies respectively.
If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
After (3.4.0)
Search the web for any topic and get clean, ready-to-use content.
Best for: Finding current information, news, facts, people, companies, or answering questions about any topic.
Returns: Clean text content from top search results.
Query tips:
describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue".
Use category:people / category:company to search through Linkedin profiles / companies respectively.
If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
3.2.0 → 3.2.1
patch release, 23 April 2026Added: web_fetch_exa
Removed: crawling_exa, get_code_context_exa
web_search_exa: description and input schema changed; arguments removed: freshness, includeDomains, type
Before (3.2.0)
Search the web for any topic and get clean, ready-to-use content.
Best for: Finding current information, news, facts, or answering questions about any topic.
Returns: Clean text content from top search results, ready for LLM use.
Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue".
If highlights are insufficient, follow up with crawling_exa on the best URLs.
After (3.2.1)
Search the web for any topic and get clean, ready-to-use content.
Best for: Finding current information, news, facts, people, companies, or answering questions about any topic.
Returns: Clean text content from top search results.
Query tips:
describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue".
Use category:people / category:company to search through Linkedin profiles / companies respectively.
If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
3.1.9 → 3.2.0
minor release, 27 March 2026Added: crawling_exa
get_code_context_exa: description and input schema changed; new arguments: numResults; arguments removed: tokensNum
Before (3.1.9)
Find code examples, documentation, and programming solutions. Searches GitHub, Stack Overflow, and official docs.
Best for: Any programming question - API usage, library examples, code snippets, debugging help.
Returns: Relevant code and documentation, formatted for easy reading.
After (3.2.0)
Find code examples, documentation, and programming solutions.
Best for: Any programming question - API usage, library examples, code snippets, debugging help.
Returns: Relevant code and documentation.
Query tips: describe what you're looking for specifically. "Python requests library POST with JSON body" not "python http".
If highlights are insufficient, follow up with crawling_exa on the best URLs.
web_search_exa: description and input schema changed; new arguments: freshness, includeDomains; arguments removed: category, contextMaxCharacters, livecrawl
Before (3.1.9)
Search the web for any topic and get clean, ready-to-use content.
Best for: Finding current information, news, facts, or answering questions about any topic.
Returns: Clean text content from top search results, ready for LLM use.
After (3.2.0)
Search the web for any topic and get clean, ready-to-use content.
Best for: Finding current information, news, facts, or answering questions about any topic.
Returns: Clean text content from top search results, ready for LLM use.
Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue".
If highlights are insufficient, follow up with crawling_exa on the best URLs.
Releases tried: 3.1.9 (2026-03-06); 3.2.0 (2026-03-27); 3.2.1 (2026-04-23); 3.4.0 (2026-08-01); 3.4.1 (2026-08-18); 3.4.2 (2026-10-06).
Tools in 3.4.2
The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition.
| Tool | Description | Pin |
|---|---|---|
| web_search_exa | Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs. | 5a37fde7510a |
| web_fetch_exa | Read a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL. Best for: Extracting full content from known URLs. Batch multiple URLs in one call. Returns: Clean text content and metadata from the page(s). | 044d0b579cd0 |
Lock these tools
Pin what exa-mcp-server serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.
$ pip install verfy
$ verfy lock check --update # shows each tool, then writes verfy.lock
$ git add verfy.lock# .github/workflows/verfy.yml, after actions/checkout
- uses: anvarbekovjavohir277-dot/verfy-action@v1Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.