# io.github.MoleCare/molecare-mcp (npm · molecare-mcp)

Educational dermatology knowledge and mole tracking. No credentials needed. Not a medical device.

- Trust score: 74/100 (medium)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `molecare-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/molecare-molecare-mcp/molecare-mcp.md), [page](https://verifymcp.io/servers/molecare-molecare-mcp/molecare-mcp)

## Channel facts

- Registry: `npm`
- Package: `molecare-mcp`
- Version: `1.1.0`
- 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-09-25.

- **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.
  - 34 of 109 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 (Apache-2.0).
  - Actively maintained (last published 15 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 912 tokens (~43/item across 21 items; 14 tools + 7 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability check failed: the tool surface changed between 1.0.2 and 1.1.0: 39 tool removals, 0 breaking changes, 0 additions.
- **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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 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 io.github.MoleCare/molecare-mcp server?

io.github.MoleCare/molecare-mcp runs locally as an npm package, launched with npx -y molecare-mcp. 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 molecare-molecare-mcp -- npx -y molecare-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "molecare-molecare-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "molecare-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "molecare-molecare-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "molecare-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add molecare-molecare-mcp -- npx -y molecare-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "molecare-molecare-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "molecare-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add molecare-molecare-mcp --command npx --arg -y --arg molecare-mcp
```

### Hermes

```yaml
mcp_servers:
  molecare-molecare-mcp:
    command: "npx"
    args: ["-y", "molecare-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "molecare-molecare-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "molecare-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add molecare-molecare-mcp -t stdio -c npx -a -y molecare-mcp
```

### Other

```json
{
  "mcpServers": {
    "molecare-molecare-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "molecare-mcp"
      ]
    }
  }
}
```

## 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-09-25 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 73, −3)

No change was recorded against any check on this day. Stability & Change Management went from 26 to 6.

### 2026-09-22 (score 76, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-20 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 16.

### 2026-09-18 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 6 to 10.

### 2026-09-16 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.

### 2026-09-10 (score 57, −23)

- [security regression] Malware scan: pass → unverified
- [security regression] Stability: 0.53 → fail
- [functional improvement] Schema quality: 2674 → 912
- [functional] Package version: 1.0.2 → 1.1.0

### 2026-09-09 (score 80, +1)

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

## MCP tools (14)

### `get_user_moles` (~42 tokens)

List a user's recorded moles and last photo dates. Educational records only — not a risk ranking.

Input parameters:

- `userId` (string, required): The user's unique identifier

### `get_mole_analysis` (~43 tokens)

Return recorded ABCDE feature measurements for a mole. Educational only — not a diagnosis or risk level.

Input parameters:

- `moleId` (string, required): The mole's unique identifier

### `get_mole_changes` (~42 tokens)

Return recorded appearance changes for a mole over time. Observations only — not a trend verdict.

Input parameters:

- `moleId` (string, required): The mole's unique identifier

### `get_user_risk_factors` (~42 tokens)

List named educational skin-health factors on a user profile. Does not calculate a risk score.

Input parameters:

- `userId` (string, required): The user's unique identifier

### `search_medical_info` (~66 tokens)

Search the medical knowledge base for skin health information. Use this to provide accurate educational content about skin conditions, ABCDE criteria, and prevention tips.

Input parameters:

- `query` (string, required): Search query (e.g., 'asymmetry', 'melanoma', 'sunscreen')

### `compare_moles` (~66 tokens)

Compare two recorded mole photos. Reports observed differences only — not a diagnosis.

Input parameters:

- `imageId1` (string, required): First image ID (older)
- `imageId2` (string, required): Second image ID (newer)
- `moleId` (string, required): The mole's unique identifier

### `lookup_medical_concept` (~67 tokens)

Look up a medical concept by SNOMED CT code. Returns detailed information about skin conditions including severity and category. Use this to provide accurate medical terminology.

Input parameters:

- `snomedCode` (string, required): SNOMED CT code (e.g., '372244006' for melanoma)

### `search_medical_concepts` (~57 tokens)

Search for medical concepts by name or description. Returns matching SNOMED CT concepts for dermatology conditions.

Input parameters:

- `query` (string, required): Search term (e.g., 'melanoma', 'nevus', 'mole')

### `get_condition_progression` (~52 tokens)

Get information about how a skin condition can progress. Shows potential progression paths (e.g., dysplastic nevus to melanoma).

Input parameters:

- `snomedCode` (string, required): SNOMED CT code of the condition

### `map_snomed_to_icd10` (~51 tokens)

Map a SNOMED CT code to ICD-10 diagnosis codes. Useful for understanding official diagnosis classifications.

Input parameters:

- `snomedCode` (string, required): SNOMED CT code to map

### `get_condition_risk_factors` (~50 tokens)

Get risk factors associated with a specific condition. Returns factors like family history, skin type, UV exposure.

Input parameters:

- `snomedCode` (string, required): SNOMED CT code of the condition

### `assess_risk_from_factors` (~69 tokens)

Describe named educational skin-health factors from a list of factor IDs. Does not calculate a risk score or recommend urgency.

Input parameters:

- `riskFactorIds` (array, required): Array of risk factor IDs (e.g., ['FAIR_SKIN', 'FAMILY_HISTORY', 'UV_EXPOSURE'])

### `classify_lesion_features` (~103 tokens)

Describe which ABCDE criteria were supplied for a lesion. Educational only — does not name a condition, assign a risk level, or recommend urgency.

Input parameters:

- `asymmetry` (boolean): Is the lesion asymmetric?
- `diameterMm` (number): Diameter in millimeters
- `hasChanged` (boolean): Has it changed over time?
- `irregularBorder` (boolean): Does it have irregular borders?
- `multipleColors` (boolean): Does it have multiple colors?

### `get_malignant_conditions` (~31 tokens)

Get a list of all malignant skin conditions in the ontology. Use for educational purposes about skin cancers.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/molecare-molecare-mcp/molecare-mcp#diagnostics

## Score history

- 2026-09-25: 74
- 2026-09-24: 73
- 2026-09-23: 76
- 2026-09-22: 76
- 2026-09-21: 60
- 2026-09-20: 60
- 2026-09-19: 59
- 2026-09-18: 59
- 2026-09-17: 58
- 2026-09-16: 58
- 2026-09-15: 57
- 2026-09-14: 57
- 2026-09-13: 57
- 2026-09-12: 57
- 2026-09-11: 57
- 2026-09-10: 57
- 2026-09-09: 80
- 2026-09-08: 79
- 2026-09-07: 79
- 2026-09-06: 79
- 2026-09-05: 78
- 2026-09-04: 78
- 2026-09-03: 77
- 2026-09-02: 77
- 2026-09-01: 76
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 72
- 2026-08-28: 72
- 2026-08-27: 72

## Common questions

### What is the io.github.MoleCare/molecare-mcp server?

io.github.MoleCare/molecare-mcp is listed in the public MCP registry as io.github.MoleCare/molecare-mcp. Educational dermatology knowledge and mole tracking. No credentials needed. Not a medical device. This page covers its npm package (molecare-mcp).

### Is the io.github.MoleCare/molecare-mcp server safe to use?

io.github.MoleCare/molecare-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 io.github.MoleCare/molecare-mcp server expose?

io.github.MoleCare/molecare-mcp exposes 14 tools: get_user_moles, get_mole_analysis, get_mole_changes, get_user_risk_factors, search_medical_info, and 9 more. Their descriptions and schemas cost roughly 781 tokens of context every time the server is loaded.

### Is the io.github.MoleCare/molecare-mcp server still maintained?

io.github.MoleCare/molecare-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 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 io.github.MoleCare/molecare-mcp server under?

io.github.MoleCare/molecare-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/molecare-mcp
- Socket report: https://socket.dev/npm/package/molecare-mcp
- Repository: https://github.com/MoleCare/molecare-mcp
- Changelog RSS feed: https://verifymcp.io/servers/molecare-molecare-mcp/molecare-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/molecare-molecare-mcp/molecare-mcp.json
- HTML version of this page: https://verifymcp.io/servers/molecare-molecare-mcp/molecare-mcp