Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mambabuilt/mcp-expert-witness-directory

NPM · @MAMBALABSDEV/MCP-EXPERT-WITNESS-DIRECTORY

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

+1 this week 83 Trust /100

Last scanned (52 minutes ago)

Scores higher than 76% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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 Security98
  • 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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 662 tokens (~662/item across 1 items; 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
Changelog

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.

  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1
    • Package version: 1.1.1 → 1.1.2 functional
Diagnostics

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/@mambalabsdev/mcp-expert-witness-directory@1.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~662 tokens

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 →

Tool Tokens
find_expert_witnesses ~662

Find expert witnesses and medico-legal assessors in the United States and Australia. Reads 18 public directories, 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. Coverage is the United States and Australia only: the public actor refuses a UK or Canadian request. published_email is filled only when a source page printed an address; the actor never guesses one. Several sources restrict automated collection or solicitation in their terms; the actor README lists each source's posture, and the use decision is yours. Use it to shortlist experts by specialty and region, or run mode feed on a schedule to see new, changed, and removed listings. Requires an APIFY_TOKEN; charges per expert record, per published email, and per NPPES check, as the README pricing table lists. Writes only to the named key-value store in your own Apify account.

NameTypeReqDescription
countryarray–US, AU, or both. Empty returns both. United States and Australia only: the public actor refuses a UK or Canadian request and stops the run with an error, so no other value is accepted.
maxItemsinteger–Stop after this many output rows (one row per deduplicated expert). 0 means no cap. A capped run never marks listings as removed. Default: 100.
modestring–list returns every matching expert. feed returns only experts that are new, changed, or returned since the last run on the same persistent store, plus removed rows; unchanged experts are not emitted…
persistStoreNamestring–Named key-value store in your account that keeps expert records between runs. Reuse the same name for feed mode. Default: expert-witness-directory-store.
regionarray–State or region as the source prints it, for example Queensland, California, New South Wales. Case and accents are ignored. Empty returns every region.
sourcesarray–Directories to read. Empty reads every implemented source. Sources that are not implemented yet, or that the actor does not cover, are skipped and named in the RUN_SUMMARY record. The 18 implemented…
specialtyarray–Taxonomy codes. A parent code also matches its children: medicine.psychiatry includes medicine.psychiatry.forensic. Empty returns every specialty.
verifyNppesboolean–Check each US record against the free NPPES monthly file (name, state, and specialty). Adds npi and nppes_status. NPPES carries no email. Charged per checked record. Default: false.

No output schema declared.

No examples provided.

Install

How do I install the com.mambabuilt/mcp-expert-witness-directory server?

com.mambabuilt/mcp-expert-witness-directory runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-expert-witness-directory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @mambalabsdev/mcp-expert-witness-directory

# add to Claude Code
claude mcp add com-mambabuilt-mcp-expert-witness-directory -- npx -y @mambalabsdev/mcp-expert-witness-directory
Common questions

What is the com.mambabuilt/mcp-expert-witness-directory server?

com.mambabuilt/mcp-expert-witness-directory is listed in the public MCP registry as com.mambabuilt/mcp-expert-witness-directory. Expert witness and medico-legal directory records for the US and Australia, one row per person. This page covers its npm package (@mambalabsdev/mcp-expert-witness-directory).

Is the com.mambabuilt/mcp-expert-witness-directory server safe to use?

com.mambabuilt/mcp-expert-witness-directory 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. 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 com.mambabuilt/mcp-expert-witness-directory server expose?

com.mambabuilt/mcp-expert-witness-directory exposes 1 tool: find_expert_witnesses. Their descriptions and schemas cost roughly 662 tokens of context every time the server is loaded.

Is the com.mambabuilt/mcp-expert-witness-directory server still maintained?

com.mambabuilt/mcp-expert-witness-directory 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 com.mambabuilt/mcp-expert-witness-directory server under?

com.mambabuilt/mcp-expert-witness-directory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.