io.github.MoleCare/molecare-mcp
NPM · MOLECARE-MCP · SCANNED SEP 25
Educational dermatology knowledge and mole tracking. No credentials needed. Not a medical device.
Available components
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
- 34 of 109 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 (Apache-2.0).Pass
- Actively maintained (last published 15 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 912 tokens (~43/item across 21 items; 14 tools + 7 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability check failed: the tool surface changed between 1.0.2 and 1.1.0: 39 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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.
npm · molecare-mcp
claude mcp add molecare-molecare-mcp -- npx -y molecare-mcp
{
"mcpServers": {
"molecare-molecare-mcp": {
"command": "npx",
"args": [
"-y",
"molecare-mcp"
]
}
}
} {
"servers": {
"molecare-molecare-mcp": {
"command": "npx",
"args": [
"-y",
"molecare-mcp"
]
}
}
} codex mcp add molecare-molecare-mcp -- npx -y molecare-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"molecare-molecare-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"molecare-mcp"
],
"enabled": true
}
}
} openclaw mcp add molecare-molecare-mcp --command npx --arg -y --arg molecare-mcp
mcp_servers:
molecare-molecare-mcp:
command: "npx"
args: ["-y", "molecare-mcp"] {
"McpServers": {
"molecare-molecare-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"molecare-mcp"
]
}
}
} assistant mcp add molecare-molecare-mcp -t stdio -c npx -a -y molecare-mcp
{
"mcpServers": {
"molecare-molecare-mcp": {
"command": "npx",
"args": [
"-y",
"molecare-mcp"
]
}
}
} 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 26 to 6.
- 22 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 16.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 6 to 10.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.
- 10 Sept 26 −23
- Malware scan: pass → unverified ▼ security
- Stability: 0.53 → fail ▼ security
- Schema quality: 2674 → 912 ▲ functional
- Package version: 1.0.2 → 1.1.0 functional
- 9 Sept 26 +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.
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 25 Sept 2026 · Analysed npm/molecare-mcp@1.1.0
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 109 packages
| Packages resolved | 109 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
assess_risk_from_factors ~69
Describe named educational skin-health factors from a list of factor IDs. Does not calculate a risk score or recommend urgency.
| Name | Type | Req | Description |
|---|---|---|---|
| riskFactorIds | array | yes | Array of risk factor IDs (e.g., ['FAIR_SKIN', 'FAMILY_HISTORY', 'UV_EXPOSURE']) |
No output schema declared.
No examples provided.
classify_lesion_features ~103
Describe which ABCDE criteria were supplied for a lesion. Educational only — does not name a condition, assign a risk level, or recommend urgency.
| Name | Type | Req | Description |
|---|---|---|---|
| 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? |
No output schema declared.
No examples provided.
compare_moles ~66
Compare two recorded mole photos. Reports observed differences only — not a diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| imageId1 | string | yes | First image ID (older) |
| imageId2 | string | yes | Second image ID (newer) |
| moleId | string | yes | The mole's unique identifier |
No output schema declared.
No examples provided.
get_condition_progression ~52
Get information about how a skin condition can progress. Shows potential progression paths (e.g., dysplastic nevus to melanoma).
| Name | Type | Req | Description |
|---|---|---|---|
| snomedCode | string | yes | SNOMED CT code of the condition |
No output schema declared.
No examples provided.
get_condition_risk_factors ~50
Get risk factors associated with a specific condition. Returns factors like family history, skin type, UV exposure.
| Name | Type | Req | Description |
|---|---|---|---|
| snomedCode | string | yes | SNOMED CT code of the condition |
No output schema declared.
No examples provided.
get_malignant_conditions ~31
Get a list of all malignant skin conditions in the ontology. Use for educational purposes about skin cancers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mole_analysis ~43
Return recorded ABCDE feature measurements for a mole. Educational only — not a diagnosis or risk level.
| Name | Type | Req | Description |
|---|---|---|---|
| moleId | string | yes | The mole's unique identifier |
No output schema declared.
No examples provided.
get_mole_changes ~42
Return recorded appearance changes for a mole over time. Observations only — not a trend verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| moleId | string | yes | The mole's unique identifier |
No output schema declared.
No examples provided.
get_user_moles ~42
List a user's recorded moles and last photo dates. Educational records only — not a risk ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | The user's unique identifier |
No output schema declared.
No examples provided.
get_user_risk_factors ~42
List named educational skin-health factors on a user profile. Does not calculate a risk score.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | The user's unique identifier |
No output schema declared.
No examples provided.
lookup_medical_concept ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| snomedCode | string | yes | SNOMED CT code (e.g., '372244006' for melanoma) |
No output schema declared.
No examples provided.
map_snomed_to_icd10 ~51
Map a SNOMED CT code to ICD-10 diagnosis codes. Useful for understanding official diagnosis classifications.
| Name | Type | Req | Description |
|---|---|---|---|
| snomedCode | string | yes | SNOMED CT code to map |
No output schema declared.
No examples provided.
search_medical_concepts ~57
Search for medical concepts by name or description. Returns matching SNOMED CT concepts for dermatology conditions.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search term (e.g., 'melanoma', 'nevus', 'mole') |
No output schema declared.
No examples provided.
search_medical_info ~66
Search the medical knowledge base for skin health information. Use this to provide accurate educational content about skin conditions, ABCDE criteria, and prevention tips.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query (e.g., 'asymmetry', 'melanoma', 'sunscreen') |
No output schema declared.
No examples provided.
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.