# mcp-expert-witness-directory [Health: Active]

**Category:** ⚖️ Legal  
**Repository:** https://github.com/mambalabsdev/mcp-expert-witness-directory  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-expert-witness-directory

## Description
Expert witness and medico-legal directory records for the US and Australia, one row per person.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-expert-witness-directory": {
    "command": "npx",
    "args": ["-y","@mambalabsdev/mcp-expert-witness-directory"],
    "env": {
      "APIFY_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `APIFY_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What mcp-expert-witness-directory does

The mcp-expert-witness-directory MCP server exposes Mamba Labs' Expert Witness Directory actor on Apify through one MCP tool: `find_expert_witnesses`. It searches records for expert witnesses and medico-legal assessors in the United States and Australia.

Records are deduplicated by person across the supported directories. Each source's specialty labels are mapped into a shared taxonomy, allowing related labels to be queried together. The directory includes 18 implemented public sources: seven in the US and 11 in Australia. A record can identify all sources where the person appeared.

Coverage is restricted to `US` and `AU`. UK and Canadian records are not available. Australian panel listings may contain the panel's contact details instead of the doctor's details, so some Australian records have a name, specialty, and state but no email.

## How it works

The tool accepts optional filters for specialty, region, country, and source. Specialty values are taxonomy codes, such as `medicine.psychiatry` or `engineering.structural`; selecting a parent code also includes its child codes. Region matching ignores letter case and accents. With no filters, the actor reads all 18 implemented sources and returns up to 100 records.

The default `list` mode returns every matching record subject to `maxItems`. The `feed` mode uses a persistent Apify key-value store to return records that are new, changed, returned, or removed since the previous run. Reusing the same `persistStoreName` is necessary for continuity. A capped run does not mark listings as removed.

The mcp-expert-witness-directory MCP server can optionally check US records against the free NPPES monthly file. This adds an NPI and NPPES status where applicable, but NPPES does not provide email addresses. Email values are returned only when a source page published them; the actor does not infer or guess addresses.

## Setup and configuration

Install the package with:

```bash
npx -y @mambalabsdev/mcp-expert-witness-directory
```

Configure an MCP client to launch it with `npx` and provide an `APIFY_TOKEN` environment variable. The token is obtained from the Apify account integrations page. The README documents a Claude Desktop configuration using the package command and token.

Calls can set `maxItems` to limit output; the default is 100, while `0` removes the cap. Reading every listing with no cap may exceed the wrapper's 3,600-second run limit because requests are spaced at one per two seconds per host. Interactive callers should normally set a limit.

## Tools and capabilities

- Search expert witness and medico-legal assessor records.
- Filter by 55 specialty taxonomy codes, including parent-child matches.
- Filter by US or Australian state and region.
- Restrict results to selected implemented sources.
- Return a full list or an incremental change feed.
- Optionally verify US records through NPPES.
- Reuse a named persistent store for feed mode.

## Limitations and notes

The mcp-expert-witness-directory MCP server depends on Apify and uses pay-per-event pricing. Charges can apply per deduplicated record, published email, NPPES check, and actor start. The listed source terms may restrict automated collection, reproduction, commercial use, or solicitation. The actor reports those terms but does not determine whether a planned use is permitted; review them for the intended use and obtain legal advice where appropriate.

The `sources` input may contain values that are planned or not covered. Those values are skipped and reported in the run summary. Only the 18 implemented source identifiers listed by the actor produce source data.

_Full upstream README: https://allmcps.com/mcp/mcp-expert-witness-directory/readme_