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.

io.github.Goingparabolic/painprep-mcp-server

NPM · PAINPREP-MCP-SERVER · SCANNED SEP 21

Interventional pain medicine MCP: Medicare checklists, CPT/ICD-10, ASRA, prior-auth & appeals

Available components

0 this week 79 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 & 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 108 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 Management93
  • Stability observed for 28 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
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
Install

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

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

  • 21 Sept 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.

  • 19 Sept 26 +1

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

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

  • 12 Sept 26 +1

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

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

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~970 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
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.

NameTypeReqDescription
documentedarrayyesItems already documented — checklist item ids or free-text phrases (e.g. "MRI findings", "conservative care 8 weeks").
procedurestringyesProcedure name, id, or CPT code.

No output schema declared.

No examples provided.

get_contraindications ~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.

NameTypeReqDescription
procedurestringyesProcedure name, id, or CPT code.

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
procedurestringyesProcedure name, id, or a CPT code to look up.

No output schema declared.

No examples provided.

get_denial_reasons ~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.

NameTypeReqDescription
procedurestringyesProcedure name, id, or CPT code.

No output schema declared.

No examples provided.

get_icd10_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.

NameTypeReqDescription
procedurestringyesProcedure name, id, or CPT code.

No output schema declared.

No examples provided.

get_medicare_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.

NameTypeReqDescription
procedurestringyesProcedure name, id, or CPT code.

No output schema declared.

No examples provided.

get_prior_auth_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.

NameTypeReqDescription
conservativeCarestringFailed conservative care with durations, e.g. "8 weeks PT, NSAIDs x6 weeks".
diagnosisstringPrimary diagnosis narrative (e.g. "left L5 radiculopathy").
functionalLimitationsstringFunctional limitations narrative.
icd10stringPrimary ICD-10 code; defaults to the recommended primary code.
imagingFindingsstringRelevant MRI/CT/X-ray findings with date.
includeWorksheetbooleanAppend the structured medical-necessity worksheet template (default true).
memberIdstringInsurance member / Medicare beneficiary ID.
painScorestringPain score, e.g. "7/10 at rest, 9/10 with activity".
patientDOBstringPatient date of birth.
patientNamestringPatient full name.
payerstringPayer / insurance company name.
procedurestringyesProcedure name, id, or CPT code.
providerNPIstringOrdering provider NPI.
providerNamestringOrdering provider name and credentials.
symptomDurationstringSymptom duration, e.g. "5 months".

No output schema declared.

No examples provided.

get_procedure_list ~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.

NameTypeReqDescription
categorystringOptional category filter (id like "epidural" or label like "Epidural Injections").

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
procedurestringyesProcedure name, id, or CPT code.

No output schema declared.

No examples provided.

Common questions

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 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 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 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 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.