io.github.daedalus/mcp-exa
PYPI · MCP-EXA
MCP server exposing Exa websearch API
Available components
Last scanned (1 day ago)
Scores higher than 96% of PyPI servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 4 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency96
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to daedalus/mcp-exa). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 218 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1012 tokens (~112/item across 9 items; 9 tools + 0 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 17 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 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 4 Nov 2026 · Analysed pypi/mcp-exa@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | daedalus/mcp-exa |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/daedalus/mcp-exa/.github/workflows/pypi-publish.yml@refs/tags/v0.1.1 |
| Rekor log index | 1201791593 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:23e191399224fa60440b2083bc74c6ac2e9a61de33667de502ab0e599e611894 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 33 packages
| Packages resolved | 33 |
|---|---|
| Stale | 2 |
| No linked repository | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
answer Answer ~104
Generate an answer to a query using Exa's search and LLM capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| model | – | – | The model to use for answering (default: exa). |
| output_schema | – | – | JSON schema for structured output. |
| query | string | yes | The query to answer. |
| system_prompt | – | – | A system prompt to guide the LLM's behavior. |
| text | – | – | Whether to include full text in the results. |
| user_location | – | – | Two-letter ISO country code for user location. |
Structured output declared, but exposes no named fields.
No examples provided.
find_similar Find Similar ~221
Find pages similar to a given URL using Exa.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | Data category to focus on. |
| contents | – | – | Options for retrieving page contents. Use False to disable. |
| end_crawl_date | – | – | Only links crawled before this date (YYYY-MM-DD). |
| end_published_date | – | – | Only links published before this date (YYYY-MM-DD). |
| exclude_domains | – | – | Domains to exclude from the search. |
| exclude_source_domain | – | – | Whether to exclude the source domain. |
| exclude_text | – | – | Strings that must not appear in the page text. |
| flags | – | – | Experimental flags for Exa usage. |
| include_domains | – | – | Domains to include in the search. |
| include_text | – | – | Strings that must appear in the page text. |
| num_results | – | – | Number of results to return. |
| start_crawl_date | – | – | Only links crawled after this date (YYYY-MM-DD). |
| start_published_date | – | – | Only links published after this date (YYYY-MM-DD). |
| url | string | yes | The URL to find similar pages for. |
Structured output declared, but exposes no named fields.
No examples provided.
get_contents Get Contents ~35
Retrieve contents for a list of URLs using Exa.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | – | yes | A single URL or list of URLs to retrieve contents from. |
Structured output declared, but exposes no named fields.
No examples provided.
research_create Research Create ~68
Create a new research request using Exa.
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | yes | The research instructions describing what to research. |
| model | – | – | The model to use ('exa-research-fast', 'exa-research', 'exa-research-pro'). |
| output_schema | – | – | JSON schema for structured output format. |
Structured output declared, but exposes no named fields.
No examples provided.
research_get Research Get ~60
Get a research request by ID using Exa.
| Name | Type | Req | Description |
|---|---|---|---|
| events | – | – | Whether to include events in the response. |
| output_schema | – | – | Optional Pydantic model for typed output validation. |
| research_id | string | yes | The unique identifier of the research task. |
Structured output declared, but exposes no named fields.
No examples provided.
research_list Research List ~37
List research requests using Exa.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | Pagination cursor from a previous response. |
| limit | – | – | Maximum number of results to return. |
Structured output declared, but exposes no named fields.
No examples provided.
research_poll_until_finished Research Poll Until Finished ~96
Poll until research is finished using Exa.
| Name | Type | Req | Description |
|---|---|---|---|
| events | – | – | Whether to include events in the response. |
| output_schema | – | – | Optional Pydantic model for typed output validation. |
| poll_interval | – | – | Milliseconds between polling attempts (default: 1000). |
| research_id | string | yes | The unique identifier of the research task. |
| timeout_ms | – | – | Maximum time to wait in milliseconds (default: 600000). |
Structured output declared, but exposes no named fields.
No examples provided.
search Search ~298
Perform a web search using Exa.
| Name | Type | Req | Description |
|---|---|---|---|
| additional_queries | – | – | Alternative query formulations for deep search. |
| category | – | – | Data category to focus on (e.g., 'company', 'news', 'research_paper'). |
| contents | – | – | Options for retrieving page contents. Use False to disable. |
| end_crawl_date | – | – | Only links crawled before this date (YYYY-MM-DD). |
| end_published_date | – | – | Only links published before this date (YYYY-MM-DD). |
| exclude_domains | – | – | Domains to exclude from the search. |
| exclude_text | – | – | Strings that must not appear in the page text. |
| flags | – | – | Experimental flags for Exa usage. |
| include_domains | – | – | Domains to include in the search. |
| include_text | – | – | Strings that must appear in the page text. |
| moderation | – | – | If True, moderate search results for safety. |
| num_results | – | – | Number of search results to return (default: 10). |
| output_schema | – | – | JSON schema for deep search structured output. |
| query | string | yes | The search query string. |
| start_crawl_date | – | – | Only links crawled after this date (YYYY-MM-DD). |
| start_published_date | – | – | Only links published after this date (YYYY-MM-DD). |
| type | – | – | Search type - 'auto', 'fast', 'deep', 'deep-reasoning', or 'instant'. |
| user_location | – | – | Two-letter ISO country code for user location. |
Structured output declared, but exposes no named fields.
No examples provided.
stream_answer Stream Answer ~93
Generate a streaming answer response using Exa.
| Name | Type | Req | Description |
|---|---|---|---|
| model | – | – | The model to use for answering. |
| output_schema | – | – | JSON schema for structured output. |
| query | string | yes | The query to answer. |
| system_prompt | – | – | A system prompt to guide the LLM's behavior. |
| text | – | – | Whether to include full text in the results. |
| user_location | – | – | Two-letter ISO country code for user location. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the io.github.daedalus/mcp-exa server?
io.github.daedalus/mcp-exa runs locally as a PyPI package, launched with uvx mcp-exa. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-exa
claude mcp add daedalus-mcp-exa -- uvx mcp-exa
What is the io.github.daedalus/mcp-exa server?
io.github.daedalus/mcp-exa is listed in the public MCP registry as io.github.daedalus/mcp-exa. MCP server exposing Exa websearch API. This page covers its PyPI package (mcp-exa).
Is the io.github.daedalus/mcp-exa server safe to use?
io.github.daedalus/mcp-exa scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 io.github.daedalus/mcp-exa server expose?
io.github.daedalus/mcp-exa exposes 9 tools: search, find_similar, get_contents, answer, stream_answer, and 4 more. Their descriptions and schemas cost roughly 1,012 tokens of context every time the server is loaded.
Is the io.github.daedalus/mcp-exa server still maintained?
io.github.daedalus/mcp-exa is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.daedalus/mcp-exa server under?
io.github.daedalus/mcp-exa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.