Remote MCP · Endpoint

Exa MCP server

No. Exa answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/exa/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/exa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Exa MCP — neural/semantic web search + content retrieval (exa.ai)
Listing
From the official MCP registry (active).
Recent checks of Exa
CheckedResultHandshake
1 hour agoHandshake completed150 ms
2 days agoHandshake completed67 ms
4 days agoHandshake completed56 ms
5 days agoHandshake completed154 ms
7 days agoHandshake completed51 ms
8 days agoHandshake completed209 ms
9 days agoHandshake completed106 ms
12 days agoHandshake completed40 ms
14 days agoHandshake completed69 ms
15 days agoHandshake completed229 ms
17 days agoHandshake completed43 ms
18 days agoHandshake completed36 ms
19 days agoHandshake completed37 ms
20 days agoHandshake completed57 ms
20 days agoHandshake completed54 ms
22 days agoHandshake completed60 ms
23 days agoHandshake completed45 ms

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

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.

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