Exa MCP server
2 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Exa's own remote MCP server gives an agent web search and page fetching, free and rate-limited with no sign-in. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 2 tools
| Tool | Counted as |
|---|---|
web_fetch_exa | Said to only read |
web_search_exa | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
13 of the last 13 checks passed
A check passes when the server lists its tools. Checked at https://mcp.exa.ai/mcp.
Recent changes
No change seen across the last 13 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Exa's tools change.
One email when Exa's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- With a sign-in or an API key, it also turns on agent_run, which free use does not offer. Exa's MCP documentation
- Search results and fetched pages come from the open web, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Exa's own settings, as its documentation describes them. Stackduke has not tested them.
- List exactly the tools you want in the tools parameter of the address. A list replaces the defaults. Exa's MCP documentation
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.