Epstein
NPM · @PIPEWORX/MCP-EPSTEIN · 2 COMPONENTS
The Epstein investigation document corpus — the documents themselves, plus (phase 2) Epstein's own…
Available components
Last scanned (2 hours ago)
Scores higher than 76% of npm servers
Category Education and Research
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-epstein). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +2
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-epstein@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-epstein |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-epstein/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635926534 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:74912d7fe3a806ec62098311cb52cf78de86871c261fccb0d2790f275fb60404dc6220490ba761d9299e931cca2938e24166ebc28ff9197a9d6c0bdcf |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
epstein_flight_log_search ~375
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
epstein_get_document ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | 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. |
No output schema declared.
No examples provided.
epstein_list_documents ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | – | Restrict to one kind of document. |
| limit | number | – | Max documents, default 50, max 200. |
No output schema declared.
No examples provided.
epstein_search_documents ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_type | string | – | Restrict to one kind of document. |
| limit | number | – | Max matching pages, default 10, max 50. |
| query | string | yes | Words to find in the document text, e.g. "Metropolitan Correctional Center" or "non-prosecution agreement". |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-epstein
claude mcp add pipeworx-io-epstein -- npx -y @pipeworx/mcp-epstein
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.