Skip to main content
Glama
releasetheepsteinfiles

epsteinexposed-mcp

by releasetheepsteinfiles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_personsA

Search the Epstein files for persons of interest.

Args:
    name: Full or partial name to search for.
    category: Filter by category (politician, business, royalty, celebrity,
              associate, legal, academic, socialite, military-intelligence, other).
    page: Page number (default 1).
    per_page: Results per page, max 100 (default 20).

Returns:
    JSON with matching person records including stats (flights, documents, etc.).
get_personA

Get full detail for a specific person by their URL slug.

Returns biographical info, aliases, black book entry status, and aggregate stats
(flights, documents, connections, emails).

Args:
    slug: The person's URL slug (e.g. "bill-clinton", "ghislaine-maxwell").

Returns:
    JSON with full person detail.
search_documentsA

Search Epstein case documents using full-text search (FTS5).

Args:
    query: Full-text search query (e.g. "little st james", "flight log").
    source: Filter by document source (court-filing, doj-release, fbi, efta).
    category: Filter by document category (deposition, testimony, correspondence).
    page: Page number (default 1).
    per_page: Results per page, max 100 (default 20).

Returns:
    JSON with matching documents including title, date, source, summary, tags.
search_flightsA

Search Epstein's flight logs (~1997-2006) across all known aircraft.

Args:
    passenger: Filter by passenger name.
    year: Filter by year (e.g. 2002).
    origin: Filter by departure location (e.g. "TIST", "Palm Beach").
    destination: Filter by arrival location (e.g. "Teterboro", "CYUL").
    page: Page number (default 1).
    per_page: Results per page, max 100 (default 20).

Returns:
    JSON with flight records including date, route, aircraft, pilot, and passengers.
cross_searchA

Search across documents AND emails simultaneously using full-text search.

Args:
    query: Search query (required).
    type: Limit to "documents" or "emails". Omit to search both.
    limit: Max results per type, max 100 (default 20).

Returns:
    JSON with separate result arrays for documents and emails.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose targeting different data types: cross_search covers both documents and emails, get_person retrieves detailed person info, search_documents focuses on documents, search_flights handles flight logs, and search_persons finds person records. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case: cross_search, get_person, search_documents, search_flights, and search_persons. The naming is predictable and readable, with no deviations in style or convention.

Tool Count5/5

With 5 tools, the server is well-scoped for its purpose of exploring Epstein-related data. Each tool serves a specific and necessary function (searching across data types, retrieving person details, and searching documents, flights, and persons), with no redundant or missing tools for the domain.

Completeness5/5

The tool surface provides complete coverage for the domain of investigating Epstein case data. It includes search capabilities across all key data types (documents, emails, flights, persons) and detailed retrieval for persons, enabling comprehensive exploration without obvious gaps or dead ends.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources