io.github.dingdawg/dingdawg-healthcare-agent
NPM · DINGDAWG-HEALTHCARE-AGENT · SCANNED SEP 21
HIPAA-aware healthcare AI. Clinical documentation, compliance checks, audit prep. Free local tier.
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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 76 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 307 tokens (~76/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.dingdawg/dingdawg-healthcare-agent MCP server?
io.github.dingdawg/dingdawg-healthcare-agent runs locally as an npm package, launched with npx -y dingdawg-healthcare-agent. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dingdawg-healthcare-agent
claude mcp add dingdawg-dingdawg-healthcare-agent -- npx -y dingdawg-healthcare-agent
{
"mcpServers": {
"dingdawg-dingdawg-healthcare-agent": {
"command": "npx",
"args": [
"-y",
"dingdawg-healthcare-agent"
]
}
}
} {
"servers": {
"dingdawg-dingdawg-healthcare-agent": {
"command": "npx",
"args": [
"-y",
"dingdawg-healthcare-agent"
]
}
}
} codex mcp add dingdawg-dingdawg-healthcare-agent -- npx -y dingdawg-healthcare-agent
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dingdawg-dingdawg-healthcare-agent": {
"type": "local",
"command": [
"npx",
"-y",
"dingdawg-healthcare-agent"
],
"enabled": true
}
}
} openclaw mcp add dingdawg-dingdawg-healthcare-agent --command npx --arg -y --arg dingdawg-healthcare-agent
mcp_servers:
dingdawg-dingdawg-healthcare-agent:
command: "npx"
args: ["-y", "dingdawg-healthcare-agent"] {
"McpServers": {
"dingdawg-dingdawg-healthcare-agent": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"dingdawg-healthcare-agent"
]
}
}
} assistant mcp add dingdawg-dingdawg-healthcare-agent -t stdio -c npx -a -y dingdawg-healthcare-agent
{
"mcpServers": {
"dingdawg-dingdawg-healthcare-agent": {
"command": "npx",
"args": [
"-y",
"dingdawg-healthcare-agent"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 16 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
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 21 Sept 2026 · Analysed npm/dingdawg-healthcare-agent@2.0.7
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
appointment_scheduler ~85
AI-powered appointment scheduling with conflict detection and optimization. Requires DINGDAWG_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| appointment_id | string | – | Appointment ID (for cancel) |
| date | string | – | Appointment date (YYYY-MM-DD) |
| patient_name | string | – | Patient name |
| time | string | – | Appointment time (HH:MM) |
No output schema declared.
No examples provided.
clinical_summary ~66
Summarize clinical notes into structured format. Extracts chief complaint, HPI, assessment, plan. Requires DINGDAWG_API_KEY for LLM-powered summarization.
| Name | Type | Req | Description |
|---|---|---|---|
| clinical_notes | string | yes | Free-text clinical notes to summarize |
| format | string | – | Output format |
No output schema declared.
No examples provided.
hipaa_check ~75
Free HIPAA compliance quick check for processes and systems. Returns basic compliance gaps locally. Deep LLM-powered audit with API key.
| Name | Type | Req | Description |
|---|---|---|---|
| data_types | string | – | Types of data handled (PHI, ePHI, etc.) |
| process_description | string | yes | Describe the process or system to assess for HIPAA compliance |
No output schema declared.
No examples provided.
patient_intake ~81
Free AI patient intake form with triage priority and symptom analysis. Returns structured intake locally. Deep LLM-powered ICD-10 coding and clinical reasoning with API key.
| Name | Type | Req | Description |
|---|---|---|---|
| age | number | – | Patient age |
| gender | string | – | Patient gender |
| medical_history | string | – | Relevant medical history |
| symptoms | string | yes | Patient symptoms description |
No output schema declared.
No examples provided.
What is the io.github.dingdawg/dingdawg-healthcare-agent MCP server?
io.github.dingdawg/dingdawg-healthcare-agent is an MCP server listed in the public MCP registry as io.github.dingdawg/dingdawg-healthcare-agent. HIPAA-aware healthcare AI. Clinical documentation, compliance checks, audit prep. Free local tier. This page covers its npm package (dingdawg-healthcare-agent).
Is the io.github.dingdawg/dingdawg-healthcare-agent MCP server safe to use?
io.github.dingdawg/dingdawg-healthcare-agent scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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.dingdawg/dingdawg-healthcare-agent MCP server expose?
io.github.dingdawg/dingdawg-healthcare-agent exposes 4 tools: patient_intake, clinical_summary, hipaa_check, appointment_scheduler. Their descriptions and schemas cost roughly 307 tokens of context every time the server is loaded.
Is the io.github.dingdawg/dingdawg-healthcare-agent MCP server still maintained?
io.github.dingdawg/dingdawg-healthcare-agent is still listed as active in the MCP registry. We last reached this channel on 21 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.dingdawg/dingdawg-healthcare-agent MCP server under?
io.github.dingdawg/dingdawg-healthcare-agent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.