# 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

- Trust score: 62/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `mcp-ratchet-clinical-charting`: 62/100 (this document), [markdown](https://verifymcp.io/servers/m2ai-mcp-servers-mcp-ratchet-clinical-charting/mcp-ratchet-clinical-charting.md), [page](https://verifymcp.io/servers/m2ai-mcp-servers-mcp-ratchet-clinical-charting/mcp-ratchet-clinical-charting)

## Channel facts

- Registry: `npm`
- Package: `mcp-ratchet-clinical-charting`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 195 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add m2ai-mcp-servers-mcp-ratchet-clinical-charting -- npx -y mcp-ratchet-clinical-charting
```

### Codex

```bash
codex mcp add m2ai-mcp-servers-mcp-ratchet-clinical-charting -- npx -y mcp-ratchet-clinical-charting
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add m2ai-mcp-servers-mcp-ratchet-clinical-charting --command npx --arg -y --arg mcp-ratchet-clinical-charting
```

### Hermes

```yaml
mcp_servers:
  m2ai-mcp-servers-mcp-ratchet-clinical-charting:
    command: "npx"
    args: ["-y", "mcp-ratchet-clinical-charting"]
```

### Other

```json
{
  "mcpServers": {
    "m2ai-mcp-servers-mcp-ratchet-clinical-charting": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ratchet-clinical-charting"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 62, +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.

### 2026-08-02 (score 61, +42)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-08-01 (score 19, +5)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass

### 2026-07-31 (score 14, −6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 20, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 38)

First indexed and scored.

## MCP tools (3)

### `search_patient` (~176 tokens)

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"

Input parameters:

- `limit` (number): Maximum number of results to return (default: 10, max: 50)
- `query` (string, required): 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.

### `create_visit_note` (~306 tokens)

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

Input parameters:

- `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, required): 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, required): Time nurse arrived (HH:MM format, 24-hour)
- `timeOut` (string, required): Time nurse departed (HH:MM format, 24-hour)
- `visitDate` (string, required): Date of visit (YYYY-MM-DD format)
- `visitType` (string, required): Type of visit
- `vitalSigns` (object): Vital signs recorded during visit

### `get_patient_history` (~155 tokens)

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.

Input parameters:

- `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, required): 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

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/m2ai-mcp-servers-mcp-ratchet-clinical-charting/mcp-ratchet-clinical-charting#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 61
- 2026-08-01: 19
- 2026-07-31: 14
- 2026-07-30: 20
- 2026-07-28: 38
- 2026-07-27: 38

## Links

- npm package: https://www.npmjs.com/package/mcp-ratchet-clinical-charting
- Socket report: https://socket.dev/npm/package/mcp-ratchet-clinical-charting
- Changelog RSS feed: https://verifymcp.io/servers/m2ai-mcp-servers-mcp-ratchet-clinical-charting/mcp-ratchet-clinical-charting/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/m2ai-mcp-servers-mcp-ratchet-clinical-charting/mcp-ratchet-clinical-charting/changelog.json
- HTML version of this page: https://verifymcp.io/servers/m2ai-mcp-servers-mcp-ratchet-clinical-charting/mcp-ratchet-clinical-charting