io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting
NPM · MCP-RATCHET-CLINICAL-CHARTING · SCANNED AUG 3
MCP server for clinical charting with Claude - document patient visits to EMR
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 195 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 637 tokens (~212/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · mcp-ratchet-clinical-charting
claude mcp add m2ai-mcp-servers-mcp-ratchet-clinical-charting -- npx -y mcp-ratchet-clinical-charting
codex mcp add m2ai-mcp-servers-mcp-ratchet-clinical-charting -- npx -y mcp-ratchet-clinical-charting
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"m2ai-mcp-servers-mcp-ratchet-clinical-charting": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-ratchet-clinical-charting"
],
"enabled": true
}
}
} openclaw mcp add m2ai-mcp-servers-mcp-ratchet-clinical-charting --command npx --arg -y --arg mcp-ratchet-clinical-charting
mcp_servers:
m2ai-mcp-servers-mcp-ratchet-clinical-charting:
command: "npx"
args: ["-y", "mcp-ratchet-clinical-charting"] {
"mcpServers": {
"m2ai-mcp-servers-mcp-ratchet-clinical-charting": {
"command": "npx",
"args": [
"-y",
"mcp-ratchet-clinical-charting"
]
}
}
} 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.
- 3 Aug 26 +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.
- 2 Aug 26 +42
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 38
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 103 packages
103 packages in the resolved dependency tree · 102 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
create_visit_note ~306
Create a visit note for a patient in the PointCare EMR system. This tool documents a home health visit including vital signs, assessment, and care plan. Use search_patient first to get the patient ID. Required fields: patientId, visitType, visitDate, timeIn, timeOut Recommended fields: vitalSigns, subjective, objective, assessment, plan
| Name | Type | Req | Description |
|---|---|---|---|
| assessment | string | — | Clinical assessment and interpretation of findings |
| education | array | — | Patient education topics covered |
| interventions | array | — | List of interventions performed during visit |
| nextVisitDate | string | — | Scheduled next visit date (YYYY-MM-DD) |
| notes | string | — | Additional notes or comments |
| objective | string | — | Nurse's observations and physical assessment findings |
| patientId | string | yes | Patient ID from search_patient (e.g., PT-10001) |
| patientResponse | string | — | How patient responded to care/interventions |
| plan | string | — | Care plan and next steps |
| subjective | string | — | Patient's reported symptoms, concerns, and statements |
| timeIn | string | yes | Time nurse arrived (HH:MM format, 24-hour) |
| timeOut | string | yes | Time nurse departed (HH:MM format, 24-hour) |
| visitDate | string | yes | Date of visit (YYYY-MM-DD format) |
| visitType | string | yes | Type of visit |
| vitalSigns | object | — | Vital signs recorded during visit |
No output schema declared.
No examples provided.
get_patient_history ~155
Retrieve visit history for a patient from the PointCare EMR system. Returns a list of previous visits with dates, types, and key information. Use this to review patient history before creating a new visit note. Use search_patient first to get the patient ID.
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | — | Filter visits on or before this date (YYYY-MM-DD) |
| limit | number | — | Maximum number of visits to return (default: 10, max: 50) |
| patientId | string | yes | Patient ID from search_patient (e.g., PT-10001) |
| startDate | string | — | Filter visits on or after this date (YYYY-MM-DD) |
| visitType | string | — | Filter by visit type |
No output schema declared.
No examples provided.
search_patient ~176
Search for a patient in the PointCare EMR system by name, ID, or phone number. Returns matching patient records with basic information. Use this tool to find patients before creating visit notes or retrieving history. Examples: - Search by name: "Eleanor Thompson" - Search by ID: "PT-10001" - Search by phone: "555-0101"
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Maximum number of results to return (default: 10, max: 50) |
| query | string | yes | Search term: patient name, ID (e.g., PT-10001), or phone number |
| searchType | string | — | Type of search to perform. Defaults to "all" which searches across all fields. |
| status | string | — | Filter by patient status. If not specified, returns all statuses. |
No output schema declared.
No examples provided.