Remote MCP · Endpoint

ai.exa/exa MCP server

No. ai.exa/exa answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.exa.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.exa/exa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
116 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Repository
https://github.com/exa-labs/exa-mcp-server
Listing
From the official MCP registry (active).
Recent checks of ai.exa/exa
CheckedResultHandshake
2 hours agoHandshake completed116 ms
1 day agoHandshake completed107 ms
3 days agoHandshake completed106 ms
3 days agoHandshake completed95 ms
4 days agoHandshake completed110 ms
5 days agoHandshake completed106 ms
7 days agoHandshake completed130 ms
10 days agoHandshake completed110 ms
12 days agoHandshake completed118 ms
14 days agoHandshake completed137 ms
17 days agoHandshake completed117 ms
19 days agoHandshake completed275 ms
21 days agoHandshake completed130 ms
23 days agoHandshake completed138 ms
25 days agoHandshake completed99 ms
26 days agoHandshake completed111 ms
28 days agoHandshake completed133 ms
29 days agoHandshake completed106 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with ai.exa/exa and makes no claim about it beyond what these checks measured.