Epstein Exposed MCP MCP Server

Connect Epstein Exposed MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Epstein files API MCP. The epstein exposed mcp mcp server is what makes that connection.

What the server does

Plug directly into any MCP-compatible client (Claude Desktop, Cursor, SmolAgents, etc.) to search persons, documents, flight logs, and emails from the Epstein case files.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• search_persons — Search/filter persons of interest by name and category
• get_person — Get full detail for a person by slug (bio, aliases, stats)
• search_documents — FTS5 full-text search across case documents
• search_flights — Search flight logs by passenger, year, origin, destination
• cross_search — Search across documents and emails simultaneously
• Cursor — The Cursor tool exposed by this server

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Epstein Exposed MCP's toolset — search_persons, get_person, search_documents and 3 more — is a fair guide to whether it matches your workflow. It is maintained by guilyx; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.