Exa MCP hosted SSE endpoint (mcp.exa.ai/mcp) down?
I'm trying to connect to the Exa MCP server using the hosted SSE endpoint https://mcp.exa.ai/mcp (opens external site) and the endpoint appears to be down. Other users also reported the websets MCP failing at the same time on 2025-12-17. What caused the outage and is there anything I need to do on the client side? The thread doesn't state a client, OS, or version.
Originally asked on GitHub: https://github.com/exa-labs/exa-mcp-server/issues/101
3 answers
Status: fixed. The outage on 2025-12-17 was caused by an upstream provider issue. A collaborator (Exa maintainer) confirmed on 2025-12-18 that both the regular exa MCP and the websets MCP were fixed and can be used normally again. The thread contains no client-side workaround or configuration change; the resolution was applied on Exa's side.
As general advice: if a hosted endpoint like https://mcp.exa.ai/mcp (opens external site) stops responding again, retry it after a short wait or restart/reconnect your MCP client session. During an upstream provider outage the endpoint itself is the problem, so there is nothing to change in your MCP client configuration.
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
Reported that https://mcp.exa.ai/mcp (opens external site) appeared to be down and attached a screenshot of the failure.
Source: https://github.com/exa-labs/exa-mcp-server/issues/101 (opens external site)
Did this work for you?What @prompted365 tried on GitHub (Outcome unclear)
Reported experiencing issues with both the websets MCP and the regular exa MCP at the same time.
Source: https://github.com/exa-labs/exa-mcp-server/issues/101#issuecomment-3667545788 (opens external site)
Did this work for you?
Related questions
- exa-mcp-server stdio fails with SyntaxError: Invalid or unexpected token on shebang line
- exa-mcp-server crashes with "SyntaxError: Invalid or unexpected token" — how to fix?
- exa-mcp-server ignores --tools option after update: how to select enabled tools?
- Exa MCP server returns HTTP 400 on remote setup (Smithery / mcp-remote)
- Exa MCP server unable to connect in KiloCode: remote URL vs npx config