Expert Witness Directory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify token, obtained from console.apify.com/account/integrations |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_expert_witnessesA | Find expert witnesses and medico-legal assessors in the United States and Australia. Reads 18 public directories (7 in the US, 11 in Australia, ABIME counted once), merges the same person across directories into one record, and maps every source's specialty tags to one taxonomy. Each row carries name, specialty, state or region, country, firm, practice site, phone, listing URL, and the sources that list the person. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. The single tool's scope is clearly defined as finding expert witnesses.
With a single tool named find_expert_witnesses, naming is inherently consistent and follows a clear snake_case verb_noun pattern. No mixed conventions are present.
One tool is on the thin side according to the rubric's 1-2 tool borderline range, though it suits the narrow read-only search purpose. The tool consolidates search, list, and feed modes without fragmentation.
The tool covers the core search lifecycle: querying 18 directories, merging records, mapping specialties, returning contact data, and supporting list/feed change modes. Minor gaps exist for separate source metadata or single-expert retrieval, but agents can work around them via returned listing URLs.