Painprep Mcp Server

io.github.GoingparabolicPublished by GitHub account Goingparabolicv0.1.2Updated Oct 24, 2026

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

Overview

AI-generated overview

A local MCP server for interventional pain medicine that gives an assistant Medicare checklists, CPT/ICD-10 coding, ASRA guidance, and prior-auth and appeals.

What you can do
Provide Medicare documentation checklists for interventional pain procedures, per the registry description. Look up CPT and ICD-10 codes. Reference ASRA guidance. Help with prior authorization and appeals. No individual tools are listed, so exact operations are not documented.
When to use it
Useful for clinicians, coders or practice staff working on interventional pain medicine documentation, coding, prior authorization or appeal letters who want an assistant to reference Medicare checklists and ASRA guidance.
Requirements
Runs as a local process on the user's machine via the npm package painprep-mcp-server (stdio), so Node.js and a desktop setup are needed. No authentication is declared. An optional PAINPREP_LICENSE_KEY environment variable unlocks the PREMIUM tier; the free tier works without it.
Before you install
The optional PAINPREP_LICENSE_KEY is a secret and should be supplied only through the environment, never pasted into chat. Coding, checklist and appeal output is reference material for clinical and billing decisions and should be verified by a qualified professional; no tool list is published, so review what it can do before relying on it.

Installation

In SourceWeft

  1. Open Painprep Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.