ai.exa/exa
REMOTE · MCP.EXA.AI
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Available components
Last scanned (3 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 451 tokens (~150/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- Server version: 3.4.2 → 3.5.0 functional
- Tool “web_fetch_exa” changed its title: Fetch Web Pages cosmetic
- Tool “web_search_exa” changed its title: Web Search cosmetic
- 12 Oct 26 +4
- Stability: fail → pass ▲ security
- 10 Oct 26 +1
- Server version: 3.2.1 → 3.4.2 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 3.2.1 ▼ security
- Schema quality: 105 → 116 ▼ functional
- “web_search_exa” added a required parameter “objective”, so existing callers break ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.exa.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.exa.ai | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 581044880f45208c0ef677ecc79e3501 |
| SANs: mcp.exa.ai, *.mcp.exa.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.exa.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| exa.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.exa.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.exa.ai/mcp | HTTPS enforced | 301 | https://mcp.exa.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
web_fetch_exa Fetch Web Pages ~103
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).
| Name | Type | Req | Description |
|---|---|---|---|
| maxCharacters | number | – | Maximum characters to extract per page (default: 3000) |
| urls | array | yes | URLs to read. Batch multiple URLs in one call. |
No output schema declared.
No examples provided.
web_search_exa Web Search ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| numResults | number | – | Number of search results to return (default: 10). |
| objective | string | yes | Goal for this search turn; say which documents should rank first, which should be excluded, and what specific facts or figures to pull from them. |
| query | string | yes | Natural language search query. Should be a semantically rich description of the ideal page, not just keywords. Optionally include category:<type> (company, people) to focus results — e.g. 'category:p… |
No output schema declared.
No examples provided.
How do I install the ai.exa/exa MCP server?
ai.exa/exa is a hosted endpoint at https://mcp.exa.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.exa.ai
claude mcp add --transport http ai-exa-exa 'https://mcp.exa.ai/mcp'
What is the ai.exa/exa MCP server?
ai.exa/exa is an MCP server listed in the public MCP registry as ai.exa/exa. Connect AI agents to Exa for web search, content fetching, and multi-step research. This page covers its hosted endpoint (https://mcp.exa.ai/mcp).
Is the ai.exa/exa MCP server safe to use?
ai.exa/exa scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ai.exa/exa MCP server expose?
ai.exa/exa exposes 2 tools: web_search_exa, web_fetch_exa. Their descriptions and schemas cost roughly 335 tokens of context every time the server is loaded.
Does the ai.exa/exa MCP server require authentication?
No. We connected to ai.exa/exa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ai.exa/exa MCP server still maintained?
ai.exa/exa is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.