io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting
NPM · MCP-RATCHET-CLINICAL-CHARTING
MCP server for clinical charting with Claude - document patient visits to EMR
Available components
Last scanned (2 hours ago)
Scores higher than 55% of npm servers
Category Health and Science
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
- 30 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
- 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 289 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.93 functional
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 15 Oct 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 5 Nov 2026 · Analysed npm/mcp-ratchet-clinical-charting@0.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 101 packages
| Packages resolved | 101 |
|---|---|
| Stale | 30 |
| 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 →
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.
How do I install the io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting server?
io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting runs locally as an npm package, launched with npx -y mcp-ratchet-clinical-charting. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-ratchet-clinical-charting
claude mcp add m2ai-mcp-servers-mcp-ratchet-clinical-charting -- npx -y mcp-ratchet-clinical-charting
What is the io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting server?
io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting is listed in the public MCP registry as io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting. MCP server for clinical charting with Claude - document patient visits to EMR. This page covers its npm package (mcp-ratchet-clinical-charting).
Is the io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting server safe to use?
io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.m2ai-mcp-servers/mcp-ratchet-clinical-charting server expose?
io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting exposes 3 tools: search_patient, create_visit_note, get_patient_history. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.
Is the io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting server still maintained?
io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting is still listed as active in the MCP registry. We last reached this channel on 5 November 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.m2ai-mcp-servers/mcp-ratchet-clinical-charting server under?
io.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.