Skip to main content
Glama
mambalabsdev

Expert Witness Directory MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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. country accepts US and AU only: the public actor covers the United States and Australia and refuses a UK or Canadian request, so the run stops with an error on any other value. published_email is filled only when a source page printed an address; the actor never guesses an email. Several sources publish terms that restrict automated collection, reproduction, commercial use, or solicitation; the actor README lists each source's terms posture, and the use decision is yours. mode list returns every matching expert; mode feed returns only experts new, changed, returned, or removed since the last run on the same persistent store. Charges $0.004 per expert record, $0.01 per row with a published email, $0.002 per US row checked against NPPES when verifyNppes is on, and $0.00005 per actor start per GB of memory (one event at the 1024 MB default). Requires an APIFY_TOKEN and consumes Apify credits. Read only against the directories; it writes only to the named key-value store in your own Apify account.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues