Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SOAPNoteAPI

NPM · SOAPNOTEAPI-MCP · SCANNED SEP 23

Generate clinical SOAP notes, billing codes, and visit summaries from transcripts or audio.

Available components

0 this week 80 Trust /100
Trust breakdown (7 categories)

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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 864 tokens (~144/item across 6 items; 6 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 Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the SOAPNoteAPI MCP server?

SOAPNoteAPI runs locally as an npm package, launched with npx -y soapnoteapi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · soapnoteapi-mcp

# add to Claude Code
claude mcp add com-soapnoteapi-soapnoteapi-mcp -- npx -y soapnoteapi-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-soapnoteapi-soapnoteapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "soapnoteapi-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-soapnoteapi-soapnoteapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "soapnoteapi-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-soapnoteapi-soapnoteapi-mcp -- npx -y soapnoteapi-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-soapnoteapi-soapnoteapi-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "soapnoteapi-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-soapnoteapi-soapnoteapi-mcp --command npx --arg -y --arg soapnoteapi-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-soapnoteapi-soapnoteapi-mcp:
    command: "npx"
    args: ["-y", "soapnoteapi-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-soapnoteapi-soapnoteapi-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "soapnoteapi-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-soapnoteapi-soapnoteapi-mcp -t stdio -c npx -a -y soapnoteapi-mcp
// mcp.json
{
  "mcpServers": {
    "com-soapnoteapi-soapnoteapi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "soapnoteapi-mcp"
      ]
    }
  }
}
Changelog

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.

  • 23 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 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

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 12 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.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 23 Sept 2026 · Analysed npm/soapnoteapi-mcp@0.1.1

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~741 tokens

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 →

Tool Tokens
generate_soap_note ~228

Generate a structured SOAP note (Subjective, Objective, Assessment, Plan) from a clinical transcript or shorthand. Optionally returns ICD-10/CPT/HCPCS billing-code suggestions and a plain-language patient summary. Billing codes are AI decision support and require clinician review.

NameTypeReqDescription
custom_instructionsstringFree-text instructions to steer formatting/content.
include_billing_codesbooleanReturn ICD-10/CPT/HCPCS billing-code suggestions.
include_icd11booleanAlso return advisory ICD-11 codes (not for US billing).
include_patient_summarybooleanReturn a plain-language patient-facing summary.
patientobjectOptional patient demographics & history to enrich the note.
patient_historystringFree-text prior history to enrich the note.
specialtystringyesMedical specialty. Call list_specialties for the full list.
templatestringOptional template within the specialty (default "standard").
transcriptstringyesClinical transcript or shorthand to expand into a SOAP note (min ~50 characters).

No output schema declared.

No examples provided.

get_audio_status ~49

Check the processing status of an asynchronous audio-to-SOAP job by noteId.

NameTypeReqDescription
noteIdstringyesThe noteId returned by transcribe_audio_to_soap for a long recording.

No output schema declared.

No examples provided.

get_note ~70

Retrieve a previously generated note by its noteId. Useful for fetching the result of an asynchronous audio job once status is 'completed'. Notes auto-expire (see expires_at).

NameTypeReqDescription
noteIdstringyesThe noteId returned by a generate/audio call (e.g. note_01jfg…).

No output schema declared.

No examples provided.

list_specialties ~45

List the medical specialties (and template variants) supported by SOAPNoteAPI. Use the returned specialty IDs as the `specialty` argument for note generation. No API key required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

summarize_visits ~102

Consolidate multiple past visits (SOAP notes and/or free-text summaries) into a longitudinal summary with key findings and active diagnoses. Useful for care coordination and chart prep.

NameTypeReqDescription
focusstringOptional focus area to bias the summary (e.g. 'diabetes management').
patientobjectOptional patient demographics & history to enrich the note.
visitsarrayyesChronological list of prior visits. Each needs a soap_note or a summary.

No output schema declared.

No examples provided.

transcribe_audio_to_soap ~247

Upload a local audio recording of a clinical encounter and get back a SOAP note. Short recordings return immediately; long ones process asynchronously — by default this tool waits and returns the finished note. Supported: mp3, m4a, wav, ogg, webm, flac.

NameTypeReqDescription
audio_pathstringyesAbsolute path to a local audio file (mp3/m4a/wav/ogg/webm/flac).
custom_instructionsstring
include_billing_codesboolean
include_icd11boolean
include_patient_summaryboolean
include_transcriptbooleanReturn the diarized, timestamped transcript.
patientobjectOptional patient demographics & history to enrich the note.
patient_historystring
specialtystringyesMedical specialty. Call list_specialties for the full list.
templatestring
timeout_secondsintegerMax seconds to wait when polling an async job (default 300).
wait_for_completionbooleanIf true (default), poll until the note is ready for long async recordings.

No output schema declared.

No examples provided.

Common questions

What is the SOAPNoteAPI MCP server?

SOAPNoteAPI is an MCP server listed in the public MCP registry as com.soapnoteapi/soapnoteapi-mcp. Generate clinical SOAP notes, billing codes, and visit summaries from transcripts or audio. This page covers its npm package (soapnoteapi-mcp).

Is the SOAPNoteAPI MCP server safe to use?

SOAPNoteAPI scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 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 SOAPNoteAPI MCP server expose?

SOAPNoteAPI exposes 6 tools: list_specialties, generate_soap_note, get_note, summarize_visits, transcribe_audio_to_soap, get_audio_status. Their descriptions and schemas cost roughly 741 tokens of context every time the server is loaded.

Is the SOAPNoteAPI MCP server still maintained?

SOAPNoteAPI is still listed as active in the MCP registry. We last reached this channel on 23 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 SOAPNoteAPI MCP server under?

SOAPNoteAPI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.