# Epstein (npm · @pipeworx/mcp-epstein)

The Epstein investigation document corpus — the documents themselves, plus (phase 2) Epstein's own…

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-epstein/epstein-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-epstein/epstein-mcp)
- npm · `@pipeworx/mcp-epstein`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-epstein/pipeworx-mcp-epstein.md), [page](https://verifymcp.io/servers/pipeworx-io-epstein/pipeworx-mcp-epstein)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-epstein`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-epstein).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 796 tokens (~199/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Epstein MCP server?

Epstein runs locally as an npm package, launched with npx -y @pipeworx/mcp-epstein. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-epstein -- npx -y @pipeworx/mcp-epstein
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-epstein": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-epstein"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-epstein": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-epstein"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-epstein -- npx -y @pipeworx/mcp-epstein
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-epstein": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-epstein"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-epstein --command npx --arg -y --arg @pipeworx/mcp-epstein
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-epstein:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-epstein"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-epstein": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-epstein"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-epstein -t stdio -c npx -a -y @pipeworx/mcp-epstein
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-epstein": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-epstein"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +2)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `epstein_search_documents` (~156 tokens)

Full-text search across the House Oversight Committee documents from the Jeffrey Epstein investigation — transcribed interviews, subpoenas and letters the committee published as PDFs. Returns the matching page with a snippet, the document title and the committee URL, so every result can be checked at source. Use it to find what a named witness said under questioning, which institutions were subpoenaed, or where a topic appears in the record.

Input parameters:

- `doc_type` (string): Restrict to one kind of document.
- `limit` (number): Max matching pages, default 10, max 50.
- `query` (string, required): Words to find in the document text, e.g. "Metropolitan Correctional Center" or "non-prosecution agreement".

### `epstein_list_documents` (~103 tokens)

Inventory of every document held from the House Oversight Epstein investigation: title, kind, page count, publication date and the committee URL. Says which documents are scans with no searchable text. Use it to see what the corpus contains before searching it, or to get a document id for epstein_get_document.

Input parameters:

- `doc_type` (string): Restrict to one kind of document.
- `limit` (number): Max documents, default 50, max 200.

### `epstein_get_document` (~109 tokens)

Read the full text of one document from the House Oversight Epstein investigation, a page at a time, given the document id from epstein_list_documents or a search result. Returns page text with the page numbers needed to cite it.

Input parameters:

- `doc_id` (string, required): Document id from epstein_list_documents or a search result.
- `page` (number): First page to return, default 1.
- `pages` (number): How many pages, default 5, max 25.

### `epstein_flight_log_search` (~375 tokens)

Structured search over Epstein's pilot flight logbook (Government Exhibit 662-RR, USA v. Ghislaine Maxwell, 20-cr-330, S.D.N.Y.) — date, aircraft, tail number, route and the pilot's own passenger/remarks entry for each leg. Passenger initials and names are returned EXACTLY as the pilot wrote them ('JE, GM, SK') — never resolved to a full identity, per design decision C on this build. A token the transcriber could read but not confirm carries a trailing '[?]'; a wholly unreadable token is '[illegible]' — neither stands in for a guessed identity. Only 397 of an estimated 3,000+ logged legs are ingested (23 of 118 exhibit pages, spanning 1991-2005) because the rest requires further page-by-page visual transcription — call epstein_flight_log_search with no filters to see exactly which pages are covered before concluding an absence. Use it to find who is logged on a given tail number, route or date range, or to search the remarks text for a name or initials.

Input parameters:

- `date_from` (string): Earliest flight date, YYYY-MM-DD.
- `date_to` (string): Latest flight date, YYYY-MM-DD.
- `from` (string): Departure identifier as printed, e.g. "TEB".
- `limit` (number): Max rows, default 20, max 100.
- `passenger` (string): Substring to find in the remarks/passenger entry, e.g. "GM" or "Clinton". Case-insensitive.
- `tail_number` (string): Aircraft registration as printed, e.g. "N908JE".
- `to` (string): Arrival identifier as printed, e.g. "PBI".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-epstein/pipeworx-mcp-epstein#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Epstein MCP server?

Epstein is an MCP server listed in the public MCP registry as io.github.pipeworx-io/epstein. The Epstein investigation document corpus, the documents themselves, plus (phase 2) Epstein's own… This page covers its npm package (@pipeworx/mcp-epstein).

### Is the Epstein MCP server safe to use?

Epstein scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Epstein MCP server expose?

Epstein exposes 4 tools: epstein_search_documents, epstein_list_documents, epstein_get_document, epstein_flight_log_search. Their descriptions and schemas cost roughly 743 tokens of context every time the server is loaded.

### Is the Epstein MCP server still maintained?

Epstein is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Epstein MCP server under?

Epstein declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-epstein
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-epstein
- Repository: https://github.com/pipeworx-io/mcp-epstein
- Website: https://pipeworx.io/packs/epstein
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-epstein/pipeworx-mcp-epstein.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-epstein/pipeworx-mcp-epstein.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-epstein/pipeworx-mcp-epstein