Automatedrcm Billing Mcp

io.github.laureennicholson635Published by GitHub account laureennicholson635v1.0.0Updated Oct 24, 2026

Medical-billing tools for AI agents: prior-auth checks, denial decoding, claim triage, appeals.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

A local MCP server giving AI assistants medical-billing tools: prior-auth checks, denial decoding, claim triage, appeal assessment and text de-identification, a

What you can do
Look up the endpoint catalog and free sample outputs before paying for anything, with no configuration needed. Check prior authorization for a CPT code and payer, returning requirement, criteria, documentation checklist, portal and turnaround. Decode claim denial CARC codes into plain-English meaning, appealability, next action and prevention. Triage unpaid claims into work buckets with risk flags, priority score, next action and deadline. Assess denied claims for appeal, fix or write-off, with deadline math, evidence checklist and a draft appeal letter. De-identify free text or healthcare text, masking names, emails, phones, SSNs, cards, IPs and addresses while preserving a date timeline.
When to use it
Useful for billing staff, RCM teams or developers building agents that need quick, deterministic answers on prior authorization, denial codes, unpaid-claim prioritization or appeal decisions, and for scrubbing text before it goes to a third-party model. Free tools let you evaluate it first.
Requirements
Runs locally via npx or from source, so Node.js and npm are needed. Free tools (catalog, free_samples) need no configuration. Paid tools require the X402_PRIVATE_KEY environment variable: a wallet private key holding USDC on Base mainnet, with no account or API key. Network access to the payment endpoint is required.
Before you install
Paid tools charge per call in USDC ($0.01–$1.50) from the wallet behind X402_PRIVATE_KEY; use a dedicated low-balance wallet, never a main one. The server asks for a wallet private key, a high-value secret. Never send real PHI: paid endpoints take codes and numbers, and phi_scrub_demo is for synthetic or test text only. Determinations reflect typical published payer policy, so verify plan-specific requirements before final decisions.

Installation

In SourceWeft

  1. Open Automatedrcm Billing Mcp 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

AutomatedRCM Billing Tools — MCP Server

Give your AI agent medical-billing intelligence in five minutes: prior-authorization determinations, claim-denial decoding, unpaid-claim triage, appeal assessments, and a PHI de-identification demo.

Built by AutomatedRCM — an AI-powered medical billing company run by a biller with 10 years in the field. The rules engines run server-side; every answer is deterministic (no LLM on the paid path, no PHI accepted). Also listed on Coinbase's x402 Bazaar.

Tools

ToolWhat it doesPrice
catalogList endpoints, prices, input shapesFree
free_samplesReal sample outputs on fixed inputs — try before you buyFree
pa_checkPrior-auth determination: CPT + payer → requirement, criteria, documentation checklist, portal, turnaround$0.05
denial_decodeCARC code (CO-50, PR-204, …) → plain-English meaning, appealability, next action, prevention$0.02
claim_triageUnpaid claim → work bucket, risk flags, priority score, next action + deadline$0.03
appeal_assessmentDenied claim → appeal/fix/write-off verdict, deadline math, evidence checklist, structured appeal-letter draft$1.50
pii_scrubDe-identify ANY text before it reaches a third-party LLM/API — names, emails, phones, SSNs, credit cards (Luhn), IPs, addresses, IDs; interval-preserving date timeline; token map for local restore$0.01
phi_scrub_demoDe-identify healthcare text (synthetic/test data ONLY) with interval-preserving date timeline$0.01

Payments use the x402 protocol — USDC on Base, settled per call, no account or API key.

Setup

Easiest — no install, straight from npm:

json
{  "mcpServers": {    "automatedrcm-billing": {      "command": "npx",      "args": ["-y", "automatedrcm-billing-mcp"],      "env": { "X402_PRIVATE_KEY": "0x..." }    }  }}

Or from source:

bash
git clone https://github.com/laureennicholson635/automatedrcm-billing-mcpcd automatedrcm-billing-mcpnpm install
json
{  "mcpServers": {    "automatedrcm-billing": {      "command": "node",      "args": ["/path/to/automatedrcm-billing-mcp/index.js"],      "env": { "X402_PRIVATE_KEY": "0x..." }    }  }}
  • Free tools (catalog, free_samples) work with no configuration.
  • Paid tools need X402_PRIVATE_KEY — a wallet private key holding a little USDC on Base mainnet ($1 covers ~30 mixed calls). Payments are gasless for the buyer (EIP-3009); the wallet needs USDC only, no ETH. Use a dedicated low-balance wallet, never your main one.

Rules of the road

  • Never send real PHI. Paid endpoints accept codes and numbers; phi_scrub_demo is for synthetic/test text only and stores nothing. Production de-identification runs licensed in your environment — contact [email protected].
  • Determinations reflect typical published payer policy; plan-level variations exist. Verify plan-specific requirements for final decisions.

Who made this

Laureen Nicholson — 10 years in medical billing, now building an AI-agent billing company in public. Live demos: Flow (claim journey) · WorkQueue · PHI Scrubber · marketplace stats. Want the full billing service or a white-label deal? getautomatedrcm.com.

Source: README.md at commit c113909

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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
  • License10 pts