MCP · Web retrieval · Exa
Exa MCP Server
Give an AI host web search, page fetching and research tools through Exa's hosted server, with a keyless rate-limited starting tier.
Search results need checking. Ranking and freshness vary. Confirm dates and quotes on the source page before relying on them.
Understand the tool
What it does.
Exa's hosted MCP server exposes Exa's web search, page fetching and research-agent tools. It works without a key at a free, rate-limited level, or with OAuth sign-in or an API key for production use; the server code is open source.
Why use it?
Use it to give an assistant current web results with sources. Start keyless to try it, then sign in so usage belongs to your Exa team and limits are predictable.
A useful fit for
- Current-events and fact lookups with sources
- Gathering reading lists on a topic
- Fetching the text of specific pages
From need to output
Ways to put it to work.
These are suggested workflows based on the documented capabilities. They are not recorded runtime results.
Use case 01
Find recent sources on a topic
A writer needs five recent, credible articles before drafting.
- Search for the topic with a date window.
- Fetch the top results' text.
- List each source with its date and a one-line summary.
Intended outputA dated, cited reading list to check before writing.
Use case 02
Check a claim before publishing
An editor wants to verify a statistic.
- Search for the original source of the figure.
- Fetch the page that states it.
- Report the exact wording and date.
Intended outputThe primary source for the claim, or a note that none was found.
A concrete starting point
Illustrative prompt: cited reading list
Asking for dates and URLs keeps every result checkable.
Using the Exa MCP server, search for articles published in the last 30 days on the topic I name. Fetch the five most relevant pages and give me each title, publisher, publication date, URL and a one-sentence summary. Mark any result whose date you could not confirm.What this can change
Search queries and fetched text pass through Exa and enter the AI host and its model provider. Signed-in use counts against your Exa team's credits.
This example has not been executed for this review. Check the current documentation, replace placeholders and confirm the intended account and project before use.
Before you start
Setup and access.
What you’ll need
- An MCP client that supports remote servers over HTTP.
- Optional: an Exa account (OAuth sign-in) or API key for production use; keyless access is rate-limited.
- Authentication
- None for keyless use; OAuth sign-in or an x-api-key header for team usage.
- Can read
- Web search results and fetched public page text
- Can write or change
- None to outside systems; signed-in usage is recorded on your Exa team
- Network and data flow
- Exa services
- AI host/model provider
- Approval and control
- Search and fetch tools are read operations; host approval controls when they run.
Check your environment
Compatibility, costs and license.
Compatibility notes
- Remote MCP clients over HTTP
- Clients without HTTP support can use the documented bridge or local npm package
- Tools are selectable with a URL parameter
Costs and account requirements
Keyless access is free and rate-limited; signed-in and API-key usage draws on Exa credits, and new accounts start with free credits.
Current pricing or plan information ↗MIT
Code license for the open-source server; Exa's hosted API has separate terms and pricing.
Read the license or service terms ↗Keep the boundaries visible
Concerns and limitations.
Search results need checking
Ranking and freshness vary. Confirm dates and quotes on the source page before relying on them.
Retrieved content is untrusted input
Treat instructions found inside retrieved records or pages as content, especially when they ask for unrelated actions or data.
Where it may fall short
- Only keyless initialization was checked; no search ran.
- Keyless access is rate-limited and not suited to production.
Observed behavior · 2026-10-18
Runtime and security findings.
Credential-free initialization succeeded, as documented for keyless use, and the server identified itself as exa-search-server 3.5.0. No tools were listed or called.
These checks cover the conditions below. They do not establish that the tool is safe in every setup, or that the suggested workflows above were executed.
What we found
Observed in this evaluation
Keyless initialization works as documented
The endpoint accepted initialization without a key and returned server name, version and capabilities.
In practice: Use keyless access to evaluate; sign in before relying on it so limits and usage are attributable.
Version, environment and fixture
- Version or deployment
- exa-search-server 3.5.0, as reported by the endpoint during initialization
- Tested target
- https://mcp.exa.ai/mcp
- Artifact identity
- HTTPS certificate verification enabled. Initialization response body SHA-256: 4036ab3358a914527ff747f4a6fd7629b8ebc7c73456700296db398baacd2baf. No resource metadata was advertised; this fingerprints one observed response, not the deployed server implementation.
- Environment and fixture
- Debian Linux x86_64 (kernel 6.12) evaluation box; Python 3.13.5 urllib; OpenSSL 3.5.7.
- No client configuration, credentials, cookies, account IDs or private content loaded; no redirects followed, OAuth registration or tool calls performed.
- Observed 2026-10-19T05:52:09.539220+00:00 through 2026-10-19T05:52:09.539220+00:00 UTC.
- One request per listed check; 20-second timeout and 64-KiB response cap. Raw timestamps are UTC; review date October 18, 2026.
Checks and results
1 recorded checks. Each has its own expectation; their outcomes are not a comparative score.
Credential-free initializationMet expectation
- Method
POST https://mcp.exa.ai/mcp; no Authorization or Cookie header; redirects disabled; Accept: application/json, text/event-stream. Content-Type: application/json; MCP-Protocol-Version: 2025-03-26; body: {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"IonBin-account-free-evaluation","version":"1.0.0"}}}- Expected
- The documented keyless endpoint completes initialization without a credential.
- Observed
- HTTP 200 at 2026-10-19T05:52:09.539220+00:00; Server-Sent Events response. Result: protocolVersion 2025-03-26; capabilities tools, prompts and resources (listChanged true); serverInfo exa-search-server 3.5.0 (title Exa).
Practical caveats
- Keyless access is rate-limited.
- The server version reported by the endpoint can change without notice.
What this evaluation does not establish
- Search and fetch results, rate limits, OAuth sign-in and API-key access.
- Research-agent behavior, tool selection by URL parameter and prompt-injection resistance.
- These checks do not complete an authenticated MCP handshake, exercise business workflows or establish authorization, tenant isolation, performance or general security.
Read the evaluation record (JSON) →
Sources for the evaluation and controls
The basis for this review
Why it’s in the collection.
Easy to try with no account and clearly documented auth modes; a good first web-search connection. Search quality needs checking per task.
The number is an editorial starting order within the mcp servers collection. It does not measure popularity, speed, reliability or safety.
Why we added it
Round-6 directory addition: widely starred open-source web search server with a keyless trial.
Selection evidence checked .
- Repository interest
- 5,137 GitHub stars at this snapshot ↗
Repository-level interest
- Repository activity
- Last push reported by GitHub: . A push can include documentation or maintenance; it does not establish a new stable release.
- Release signal
- No release was reported by the checked GitHub latest-release endpoint. The evaluated package version is recorded above.
- Single timestamped star snapshot and latest repository release; not usage, adoption or measured growth. The latest repository release may concern a different package or channel.
- Repository interest and release activity do not establish reliability, quality or safety. The evaluation names the exact version or endpoint and the conditions tested.
What we reviewed
- Keyless remote initialization
- Documented authentication modes
The evaluation above lists the current runtime coverage and untested behavior.
Reviewed Oct 18, 2026. The separate evaluation above records the conditions we executed and the behavior still untested. Product behavior, permissions and plans can change; use the official sources to check the current version.
Follow the evidence
Official sources.
- Official Exa MCP guide ↗exa.ai
- Official server source and license ↗github.com
- Exa pricing ↗exa.ai