io.github.Goingparabolic/painprep-mcp-server
NPM · PAINPREP-MCP-SERVER
Interventional pain medicine MCP: Medicare checklists, CPT/ICD-10, ASRA, prior-auth & appeals
Available components
Last scanned (14 hours ago)
Scores higher than 51% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. 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 169 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1065 tokens (~118/item across 9 items; 9 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 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.
- 9 Nov 26 −2
- Source repository: unverified → fail ▼ security
- Stability: pass → 0.90 functional
- 8 Nov 26 0
- Provenance: fail → unverified ▼ security
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 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 Nov 2026 · Analysed npm/painprep-mcp-server@0.1.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
check_documentation_completeness Check Documentation Completeness ~118
Given a procedure and the list of items already documented in the chart, audits the note against the Medicare required-documentation checklist and returns what is satisfied, what is still missing (with rationale and suggested wording), a spotlight on commonly-missed gaps, and an overall completeness score. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| documented | array | yes | Items already documented — checklist item ids or free-text phrases (e.g. "MRI findings", "conservative care 8 weeks"). |
| procedure | string | yes | Procedure name, id, or CPT code. |
No output schema declared.
No examples provided.
get_contraindications Get Contraindications & Anticoagulation Guidance ~84
Given a procedure, returns its bleeding-risk level and the ASRA-aligned anticoagulant/antiplatelet stop-and-restart guidance (per agent), special considerations, and general pre-procedure safety checks. Always verify against the current ASRA guidelines and institutional policy. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| procedure | string | yes | Procedure name, id, or CPT code. |
No output schema declared.
No examples provided.
get_cpt_codes Get CPT Codes ~73
Given a procedure (name, id, or CPT code), returns the primary CPT code(s), add-on codes, work RVUs, typical facility setting (office/ASC/hospital), and billing notes. FREE tier.
| Name | Type | Req | Description |
|---|---|---|---|
| procedure | string | yes | Procedure name, id, or a CPT code to look up. |
No output schema declared.
No examples provided.
get_denial_reasons Get Denial Reasons & Appeal Templates ~62
Given a procedure, returns the common payer denial reasons with their relative frequency, the concrete fix/remedy for each, and a ready-to-adapt appeal letter snippet. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| procedure | string | yes | Procedure name, id, or CPT code. |
No output schema declared.
No examples provided.
get_icd10_codes Get ICD-10 Codes ~63
Given a procedure, returns the approved/supportive ICD-10 diagnosis codes, codes to AVOID (common denial triggers), and coding tips for medical-necessity support. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| procedure | string | yes | Procedure name, id, or CPT code. |
No output schema declared.
No examples provided.
get_medicare_checklist Get Medicare Documentation Checklist ~71
Given a procedure, returns the full Medicare/LCD documentation checklist: required documentation items with rationale and suggested chart wording, top denial triggers, and pre-submission admin checks. Flags items that are commonly missed. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| procedure | string | yes | Procedure name, id, or CPT code. |
No output schema declared.
No examples provided.
get_prior_auth_letter Generate Prior Authorization Letter ~341
Generates a formal, payer-ready prior-authorization / medical-necessity letter for a procedure, merging supplied patient and clinical details with the procedure’s CPT codes, recommended primary ICD-10 code, evidence grade, and necessity rationale. Any field left unspecified is rendered as a clearly-marked fill-in blank. The structured medical-necessity worksheet is appended when available. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| conservativeCare | string | – | Failed conservative care with durations, e.g. "8 weeks PT, NSAIDs x6 weeks". |
| diagnosis | string | – | Primary diagnosis narrative (e.g. "left L5 radiculopathy"). |
| functionalLimitations | string | – | Functional limitations narrative. |
| icd10 | string | – | Primary ICD-10 code; defaults to the recommended primary code. |
| imagingFindings | string | – | Relevant MRI/CT/X-ray findings with date. |
| includeWorksheet | boolean | – | Append the structured medical-necessity worksheet template (default true). |
| memberId | string | – | Insurance member / Medicare beneficiary ID. |
| painScore | string | – | Pain score, e.g. "7/10 at rest, 9/10 with activity". |
| patientDOB | string | – | Patient date of birth. |
| patientName | string | – | Patient full name. |
| payer | string | – | Payer / insurance company name. |
| procedure | string | yes | Procedure name, id, or CPT code. |
| providerNPI | string | – | Ordering provider NPI. |
| providerName | string | – | Ordering provider name and credentials. |
| symptomDuration | string | – | Symptom duration, e.g. "5 months". |
No output schema declared.
No examples provided.
get_procedure_list List Pain Procedures ~89
Returns the full catalog of interventional pain medicine procedures, grouped by category. Each entry includes the procedure id (used by other tools), display name, short name, and headline CPT code(s). Optionally filter by a category id or name. FREE tier.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (id like "epidural" or label like "Epidural Injections"). |
No output schema declared.
No examples provided.
get_research_evidence Get Research Evidence ~69
Given a procedure, returns the overall evidence grade, a summary of the evidence base, and the key supporting studies (title, journal, year, and headline finding) for use in notes and appeals. PREMIUM tier.
| Name | Type | Req | Description |
|---|---|---|---|
| procedure | string | yes | Procedure name, id, or CPT code. |
No output schema declared.
No examples provided.
How do I install the io.github.Goingparabolic/painprep-mcp-server server?
io.github.Goingparabolic/painprep-mcp-server runs locally as an npm package, launched with npx -y painprep-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · painprep-mcp-server
claude mcp add goingparabolic-painprep-mcp-server -- npx -y painprep-mcp-server
What is the io.github.Goingparabolic/painprep-mcp-server server?
io.github.Goingparabolic/painprep-mcp-server is listed in the public MCP registry as io.github.Goingparabolic/painprep-mcp-server. Interventional pain medicine MCP: Medicare checklists, CPT/ICD-10, ASRA, prior-auth & appeals. This page covers its npm package (painprep-mcp-server).
Is the io.github.Goingparabolic/painprep-mcp-server server safe to use?
io.github.Goingparabolic/painprep-mcp-server scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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.Goingparabolic/painprep-mcp-server server expose?
io.github.Goingparabolic/painprep-mcp-server exposes 9 tools: get_procedure_list, get_cpt_codes, get_medicare_checklist, get_icd10_codes, get_contraindications, and 4 more. Their descriptions and schemas cost roughly 970 tokens of context every time the server is loaded.
Is the io.github.Goingparabolic/painprep-mcp-server server still maintained?
io.github.Goingparabolic/painprep-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 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.Goingparabolic/painprep-mcp-server server under?
io.github.Goingparabolic/painprep-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.Goingparabolic/painprep-mcp-server server?
VerifyMCP ran 15 checks on io.github.Goingparabolic/painprep-mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.Goingparabolic/painprep-mcp-server: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.