Molecare Mcp

io.github.MoleCare由 GitHub 帳號 MoleCare 發布v1.2.0更新於 Oct 30, 2026

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

已驗證STDIO僅桌面知識與記憶開發者工具

概覽

AI 產生的概覽

本機 MCP 伺服器，為助理提供內建的皮膚科教育知識庫、SNOMED CT/ICD-10 輔助工具，以及選用的 MoleCare 痣追蹤 API 工具。

可以做什麼
  • 搜尋並閱讀皮膚科教育知識：ABCDE 準則、Fitzpatrick 膚色類型、預防建議、何時就醫
  • 查詢與搜尋 SNOMED CT 概念，並對應到 ICD-10 類別，附上來源中繼資料
  • 以 ABCDE 方式描述病灶特徵，列出教育性的風險因子與疾病進展階段
  • 提供可重複使用的提示詞：說明 ABCDE、準備皮膚科就診、解釋 SNOMED 代碼
  • 在設定後端後查詢 MoleCare 產品資料（痣、分析、變化紀錄、風險概況、比較），否則回傳標示為模擬的資料
適用情境
適合讓助理說明皮膚健康術語、ABCDE 概念或 SNOMED/ICD-10 代碼，或針對相容於 MoleCare 的 API 先做助理流程原型。它是教育輔助工具，不用於診斷。
執行需求
透過 npx 在本機執行，需要 Node.js；知識類工具不需憑證、資料庫或網路。選用的 MOLECARE_API_URL 與 MOLECARE_API_KEY 可連接真實的 MoleCare 相容後端；LOG_LEVEL 控制日誌詳細程度。另有獨立的 molecare-ops-mcp 執行檔提供內部維運工具。
安裝前請注意
明確聲明不是醫療器材：輸出僅供教育，不得用於診斷或治療決策。連接真實後端時，接受 userId 的工具可能回傳 PHI，應視為正式環境處理，並避免把 MOLECARE_API_KEY 放進會同步到雲端硬碟的設定檔。內建的 SNOMED/ICD-10 子集為近似對應，並非經授權的術語散布。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Molecare Mcp，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

MoleCare MCP Server

[npm version] [npm downloads] [License] [Node] [MCP] [Contributors]

Model Context Protocol (MCP) server that gives Claude and other MCP clients access to:

  1. Dermatology knowledge — ABCDE education, SNOMED CT / ICD-10 helpers, risk-factor prompts
  2. Optional MoleCare API tools — moles, trends, analysis (your backend + API key)
  3. Optional MLOps / ops tools — shipped as a separate binary, molecare-ops-mcp (mock-first)

Not a medical device. Outputs are educational and operational aids only. Do not use for diagnosis or treatment decisions.

Product site: molecare.co.uk · App: iOS · Android

[npx -y molecare-mcp answering a SNOMED CT to ICD-10 lookup with no credentials configured]

One command, no API key, no database. Real output from the published package.

Why this exists

MoleCare helps people track moles over time and prepare for clinician visits. This MCP server lets developers and operators:

  • Query educational skin-health knowledge from Claude Desktop / Cursor
  • Prototype assistant flows against a MoleCare-compatible API
  • Explore MLOps tooling with safe mock data when no credentials are set

Quick start

No credentials, no database, no cloud account. Add this to your MCP client config and restart it:

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

For Claude Desktop on macOS that file is ~/Library/Application Support/Claude/claude_desktop_config.json.

The dermatology knowledge tools work immediately — they read from a knowledge base bundled in the package. Everything that talks to a backend returns clearly-labelled mock data until you configure it, so you can explore the whole tool surface before deciding whether you want any of it.

To try it without a client at all:

bash
npx -y molecare-mcp

It starts and waits on stdio. No output means it is working.

Claude Code plugin

This repository is also a Claude Code plugin: the same server, plus a skill that tells Claude when to use it and to never diagnose.

bash
claude plugin marketplace add MoleCare/molecare-mcpclaude plugin install molecare@molecare

Then ask things like "what does the E in ABCDE mean?" or "help me prepare for a dermatology appointment". The plugin runs npx -y molecare-mcp with no keys, so the account tools return example data marked "dataSource": "mock".

Connecting a real backend

Only needed if you are running a MoleCare-compatible API:

json
{  "mcpServers": {    "molecare": {      "command": "npx",      "args": ["-y", "molecare-mcp"],      "env": {        "MOLECARE_API_URL": "http://localhost:8080/api",        "MOLECARE_API_KEY": "your-local-api-key"      }    }  }}

Use localhost (or your own deployment). Do not paste production keys into config files that sync to cloud drives.

Environment variables

Every setting is optional. The public server falls back to mock product data without API credentials, and its knowledge tools continue to work offline. For the operations server, use NODE_ENV=development (the .env.example default) to keep integrations in mock mode.

Shared by both binaries

VariablePurposeExample
MOLECARE_API_URLMoleCare-compatible HTTP APIhttp://localhost:8080/api
MOLECARE_API_KEYAPI bearer/key; required with a real MoleCare APIlocal-dev-key
LOG_LEVELLogging verbosity: debug, info, warn, or errorinfo
MCP_HEALTH_PORTPreferred port for the optional HTTP /health endpoint3000
PORTFallback health port, useful for container platforms3000
PRIVACY_GATE_URLOptional local sidecar that checks tool results before egresshttp://localhost:8231
PRIVACY_GATE_TIMEOUT_MSPrivacy-gate request timeout in milliseconds4000

Public server (molecare-mcp)

The public server has no additional settings. Its dermatology knowledge works without configuration; the shared MoleCare API variables enable its optional mole and profile tools.

Operations server (molecare-ops-mcp)

The operations binary also accepts the shared settings above. These additional variables only configure its infrastructure, monitoring, and CI/CD tools:

VariablePurposeExample
NODE_ENVdevelopment forces mock mode; use production only with configured servicesdevelopment
MLFLOW_TRACKING_URIMLflow tracking serverhttp://localhost:5000
MLFLOW_API_KEYOptional MLflow API key—
ML_SERVING_URLModel-serving health endpointhttp://localhost:5000/health
FEAST_SERVER_URLFeast feature serverhttp://localhost:6566
FEAST_PROJECTFeast project namemolecare
WEB_APP_URLMoleCare web applicationhttp://localhost:3000
MOBILE_API_URLMoleCare mobile APIhttp://localhost:8080/api
ADMIN_API_URLMoleCare admin APIhttp://localhost:8080
BACKEND_URLBackend health endpointhttp://localhost:8080
METRICS_API_URLApplication metrics API; leaving it empty keeps app monitoring mocked—
GITHUB_OWNERRepository owner used by CI/CD toolsMoleCare
GITHUB_REPORepository name used by CI/CD toolsMoleCare-ML
GITHUB_TOKENGitHub token used by CI/CD tools—
AWS_REGIONAWS region used by EC2 and CloudWatch toolsus-east-1
AWS_PROFILENamed AWS credential profile—
AWS_ACCESS_KEY_IDAWS SDK credential-chain access key; prefer a role or profile—
EC2_INSTANCE_IDSComma-separated EC2 instance IDs—
DB_HOSTPostgreSQL host used by database health checkslocalhost
DB_PORTPostgreSQL port5432
DB_NAMEPostgreSQL database namemolecare
REDIS_HOSTRedis host and portlocalhost:6379
ES_HOSTElasticsearch host and portlocalhost:9200

See .env.example for the copyable source-of-truth list.

Tools

Dermatology knowledge — no setup required

These are the reason most people install this. They answer from a bundled knowledge base and need no API, no key, and no network.

ToolDescription
search_medical_infoSearch the dermatology knowledge base
lookup_medical_conceptLook up a SNOMED CT concept
search_medical_conceptsSearch conditions by name or description
map_snomed_to_icd10Map a SNOMED CT code to ICD-10
classify_lesion_featuresABCDE-style feature descriptors for a lesion
assess_risk_from_factorsNamed educational risk factors (no score)
get_condition_risk_factorsKnown risk factors for a condition
get_condition_progressionTypical progression stages for a condition
get_malignant_conditionsMalignant skin conditions with codes

Resources: molecare://knowledge/* — ABCDE criteria, Fitzpatrick skin types, prevention, when to see a dermatologist. molecare://ontology/* — SNOMED CT and ICD-10 reference lists, the full snomed-icd10-map mapping table, and risk factors, all with provenance metadata.

Educational prompts

The server also exposes three reusable MCP prompts: walk_through_abcde, prepare_dermatology_appointment, and explain_snomed_code. They help a client organize observations or explain terminology without diagnosing a condition, assigning urgency, or producing a risk score. Every rendered prompt includes the non-diagnostic educational disclaimer; the terminology prompt requires a SNOMED CT code argument.

What the terminology actually covers

Bundled
SNOMED CT concepts7 — melanoma, melanoma in situ, BCC, SCC, actinic keratosis, dysplastic naevus, melanocytic naevus
WHO ICD-10 categories25 — malignant, in situ, benign, precancerous, inflammatory and pigmentation, across Chapters II and XII
SNOMED → ICD-10 mappings9 rows covering all 7 concepts — some concepts have more than one plausible target

Every SNOMED concept the server advertises resolves through lookup_medical_concept and maps through map_snomed_to_icd10. Ask for a code outside the subset and the response carries a coverage block listing what is bundled, rather than an empty result. Browse the whole table with the molecare://ontology/snomed-icd10-map resource.

ICD-10 coverage is deliberately broader than SNOMED coverage. Expanding the bundled SNOMED concept set is on hold pending a redistribution question with SNOMED International: free use in a member country is not the same as free redistribution via npm to non-member territories (#49). WHO licenses ICD-10 more permissively at this level, so that side can grow in the meantime.

Terminology provenance

Bundled SNOMED CT / ICD-10 helpers are an educational subset, not a licensed terminology distribution. Named sources live in src/resources/terminology-provenance.ts and are returned on map_snomed_to_icd10 and the ontology resources:

SystemWhat this package reflects
SNOMED CTInternational Edition concept IDs / FSNs checked against the SNOMED International browser (last checked 2026-09-03). Plain-English search aliases are written for this package and are not SNOMED descriptions
ICD-10WHO ICD-10 category-level codes (e.g. C43, D22), with four-character subcategories only where the category alone would mislead (L57.0, D18.0). Not ICD-10-CM — codes such as C4A are deliberately absent
SNOMED → ICD-10Approximate category-level mappings — not certified one-to-one map rows. Each row carries a rationale

The dataset itself lives in src/resources/terminology-data.ts and is the single source for both the src/api/ontology-client.ts mock paths and the ontology resources. Educational prose without clinical codes lives in src/resources/medical-kb.ts.

MoleCare product data — needs an API

Returns labelled mock data until MOLECARE_API_URL is set.

ToolDescription
get_user_molesList moles for a user id
get_mole_analysisAnalysis payload for a mole
get_mole_changesChange history for a mole
get_user_risk_factorsA user's risk profile
compare_molesCompare two moles
Operations and MLOps tooling (39 tools — separate molecare-ops-mcp binary)

These exist because MoleCare operates this stack from an assistant. They are of little use outside that context, and all of them return mock data unless the matching backend is configured.

They are not part of the molecare-mcp tool list. Loading 39 infrastructure tools that nobody outside MoleCare can use made it measurably harder for a model to pick the right dermatology tool, so they live in their own server:

json
{  "mcpServers": {    "molecare-ops": {      "command": "npx",      "args": ["-y", "-p", "molecare-mcp", "molecare-ops-mcp"]    }  }}
AreaTools
Healthget_system_health, check_server_health, get_service_health, clear_cache
MLflowget_mlflow_experiments, get_mlflow_runs, get_registered_models, get_model_version, compare_model_runs, get_training_runs
Feature storeget_feature_views, get_feature_view_details, get_feature_freshness, get_online_features, get_feature_store_stats
CI/CDget_pipeline_runs, get_pipeline_summary, get_deployments, get_deployment_status, get_releases
AWSget_ec2_instances, get_ec2_instance, get_ec2_health, get_ec2_metrics
Appsget_app_status, get_web_app_status, get_mobile_api_status, get_all_apps_status, get_app_metrics, get_app_errors, get_app_versions, get_app_store_status
Databaseget_database_status, get_database_metrics, get_slow_queries, get_table_stats, get_backup_history, get_connection_pools
Kubernetesget_kubernetes_status

The AWS tools need @aws-sdk/client-ec2 and @aws-sdk/client-cloudwatch, which are optional peer dependencies — they are not installed by default, because they add 33 MB that nobody wanting the dermatology tools should have to download. Install them yourself if you want live AWS data:

bash
npm i @aws-sdk/client-ec2 @aws-sdk/client-cloudwatch

Architecture

Claude / Cursor / MCP client        │ stdio (JSON-RPC)        ▼  molecare-mcp                    molecare-ops-mcp   ├─ medical KB (local)           ├─ MLflow / Feast clients   ├─ MoleCare API client          ├─ AWS / CI / K8s clients   └─ ontology client              └─ database / app clients        │    (14 tools)                 │   (39 tools, internal)        │                               │        └───────────┬───────────────────┘                    └─ optional HTTP GET /health  (Docker / ECS)

Docker

bash
docker build -t molecare-mcp .docker run --rm -p 3000:3000 molecare-mcpcurl http://localhost:3000/health

Security

  • Never commit .env files or API keys — see SECURITY.md to report a vulnerability
  • Prefer mock mode for demos and screenshots
  • Tools that accept userId can return PHI only if you point them at a real backend with real auth — treat that as production
  • Rate-limit and auth belong on your API, not only on the MCP process

Medical disclaimer

MoleCare MCP provides educational information and developer tooling. It does not diagnose melanoma or any disease. Always consult a qualified clinician for medical concerns.

Development

bash
git clone https://github.com/MoleCare/molecare-mcp.gitcd molecare-mcpnpm installnpm run buildnpm run dev      # auto-reloadnpm run inspect  # browse tools in MCP Inspector

Contributions are welcome. Read CONTRIBUTING.md first — it covers the mock-first rule, the clinical-safety boundary for anything touching medical content, and how to pick up a good first issue.

Please keep secrets out of examples and prefer localhost defaults.

Related

Environment variables: .env.example is the authoritative list. CI compares it with the variables reachable from both server entrypoints and checks the public/operations grouping above.

Where it is listed

  • npm, as molecare-mcp
  • Glama and MCP Servers Live, which index MCP servers
  • mcprush, a marketplace for MCP servers and agent skills: free, installed from the npm package, nothing hosted by mcprush

If you use it somewhere, or wrote about it, open an issue and it goes here.

Contributors

Thank you to everyone who has helped molecare-mcp.

[Yauhen Bichel] [Komal Singh] [Amirreza Hosseini] [Awokoya Olawale Davidson] [ADITYA] [Huangshuo Kuang] [Elkero]

The list is filled by Contributors from GitHub commits, bots omitted — never hand-maintained, because a stale list is worse than none. Contributor graph · good first issue

License

Apache-2.0 © Yauhen Bichel

來源：README.md，提交 d8344eb

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

2
  1. v1.2.0最新Oct 9, 2026
  2. v1.1.0Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分