# com.mambabuilt/mcp-healthcare-provider-npi-enricher (npm · @mambalabsdev/mcp-healthcare-provider-npi-enricher)

Enrich NPIs or healthcare provider names from the official US NPI Registry

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@mambalabsdev/mcp-healthcare-provider-npi-enricher`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-healthcare-provider-npi-enricher/mambalabsdev-mcp-healthcare-provider-npi-enricher.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-healthcare-provider-npi-enricher/mambalabsdev-mcp-healthcare-provider-npi-enricher)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-healthcare-provider-npi-enricher`
- Version: `1.0.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 432 tokens (~432/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the com.mambabuilt/mcp-healthcare-provider-npi-enricher server?

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

### Claude

```bash
claude mcp add com-mambabuilt-mcp-healthcare-provider-npi-enric -- npx -y @mambalabsdev/mcp-healthcare-provider-npi-enricher
```

### Cursor

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-healthcare-provider-npi-enric": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-healthcare-provider-npi-enricher"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mambabuilt-mcp-healthcare-provider-npi-enric": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-healthcare-provider-npi-enricher"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-mambabuilt-mcp-healthcare-provider-npi-enric -- npx -y @mambalabsdev/mcp-healthcare-provider-npi-enricher
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-healthcare-provider-npi-enric": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-healthcare-provider-npi-enricher"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mambabuilt-mcp-healthcare-provider-npi-enric --command npx --arg -y --arg @mambalabsdev/mcp-healthcare-provider-npi-enricher
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-healthcare-provider-npi-enric:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-healthcare-provider-npi-enricher"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-mambabuilt-mcp-healthcare-provider-npi-enric": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mambalabsdev/mcp-healthcare-provider-npi-enricher"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mambabuilt-mcp-healthcare-provider-npi-enric -t stdio -c npx -a -y @mambalabsdev/mcp-healthcare-provider-npi-enricher
```

### Other

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-healthcare-provider-npi-enric": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-healthcare-provider-npi-enricher"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 75, +1)

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

### 2026-11-19 (score 74, +1)

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

### 2026-11-17 (score 73, +1)

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

### 2026-11-15 (score 72, +1)

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

### 2026-11-13 (score 71, +1)

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

### 2026-11-11 (score 70, 0)

- [functional] Package version: 1.0.1 → 1.0.2

### 2026-11-10 (score 70, +1)

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

### 2026-11-09 (score 69, +15)

- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.0.0 → 1.0.1

## MCP tools (1)

### `enrich_healthcare_providers_npi` (~432 tokens)

Enrich healthcare providers from the NPI Registry

Give NPIs, individual names, organization names, or a taxonomy with a state. Returns one row per provider from the official US NPI Registry with taxonomy, license, practice address and phone, and organization official. Invalid and unmatched lookups are free. Pay per event on Apify: 0.002 USD per provider row.

Input parameters:

- `city` (string): City filter. Applies to names and to the search.
- `individual_names` (array): People, as Jane Doe, Doe, Jane, or Dr. Jane Doe MD. The registry also matches common first name aliases. A trailing * after 2 or more letters is a wildcard. Add state to narrow common names.
- `max_charge_usd` (string): Optional. The run stops before a charge that would pass this amount. Summary rows are always returned.
- `max_results_per_lookup` (number): Provider rows per name or search, from 1 to 1200. Default 25. The registry serves at most 1200 records per search.
- `npis` (array): 10 digit NPIs. Each returns its record. An invalid NPI or one with no record is a free row.
- `organization_names` (array): Organizations. The registry matches whole words, so add a trailing *, such as kaiser*, to widen the match.
- `postal_code` (string): 5 or 9 digit postal code, with a trailing * after 2 or more digits as a wildcard.
- `provider_type` (string): For the taxonomy, city, or postal code search: both (default), individual, or organization.
- `state` (string): Two letter state code. Applies to names and to the search. The registry refuses state alone, so give it with a name, taxonomy, city, or postal code.
- `taxonomy` (string): Filter or search by the registry's taxonomy wording, such as cardiovascular disease, or cardio* as a wildcard. Cardiology alone matches only Pharmacist, Cardiology. Applies to names and to the search…

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-healthcare-provider-npi-enricher/mambalabsdev-mcp-healthcare-provider-npi-enricher#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 70
- 2026-11-11: 70
- 2026-11-10: 70
- 2026-11-09: 69
- 2026-11-08: 54

## Common questions

### What is the com.mambabuilt/mcp-healthcare-provider-npi-enricher server?

com.mambabuilt/mcp-healthcare-provider-npi-enricher is listed in the public MCP registry as com.mambabuilt/mcp-healthcare-provider-npi-enricher. Enrich NPIs or healthcare provider names from the official US NPI Registry. This page covers its npm package (@mambalabsdev/mcp-healthcare-provider-npi-enricher).

### Is the com.mambabuilt/mcp-healthcare-provider-npi-enricher server safe to use?

com.mambabuilt/mcp-healthcare-provider-npi-enricher scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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-healthcare-provider-npi-enricher server expose?

com.mambabuilt/mcp-healthcare-provider-npi-enricher exposes 1 tool: enrich_healthcare_providers_npi. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.

### Is the com.mambabuilt/mcp-healthcare-provider-npi-enricher server still maintained?

com.mambabuilt/mcp-healthcare-provider-npi-enricher is still listed as active in the MCP registry. We last reached this channel on 21 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-healthcare-provider-npi-enricher server under?

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

### What did VerifyMCP test on the com.mambabuilt/mcp-healthcare-provider-npi-enricher server?

VerifyMCP ran 16 checks on com.mambabuilt/mcp-healthcare-provider-npi-enricher, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-healthcare-provider-npi-enricher
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-healthcare-provider-npi-enricher
- Repository: https://github.com/mambalabsdev/mcp-healthcare-provider-npi-enricher
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-healthcare-provider-npi-enricher/mambalabsdev-mcp-healthcare-provider-npi-enricher.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-healthcare-provider-npi-enricher/mambalabsdev-mcp-healthcare-provider-npi-enricher/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-mambabuilt-mcp-healthcare-provider-npi-enricher/mambalabsdev-mcp-healthcare-provider-npi-enricher.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-healthcare-provider-npi-enricher/mambalabsdev-mcp-healthcare-provider-npi-enricher
