@backwork/mcp

MCPattestedlive
v2.1.2Backwork LLCMITUpdated 5d agonpmGitHub

MCP server for Backwork: Medicare and payer medical policy, prior authorization, claim risk, and medical codes. Hosted OAuth remote or local stdio.

Endpoint healthlive
checked 1 day ago · 202ms · auth required
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
614Downloads/wk
1GitHub stars
5d agoLast update
Needs 1 credential before it runs
  • BACKWORK_API_KEYAPI keyrequired

    Backwork API key (bwk_live_...). The hosted remote uses OAuth instead and needs no key.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorBackwork LLC
LicenseMIT
Version2.1.2
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · c2f3cb2
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface8 tools · none privileged
Security scan✓ Cleanv2.1.2 · 1d agoHow well does this scan work?
EvalsNone
IndexedOct 4, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · none privileged
Statically extracted from the published packagev2.1.2 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

coverage_lookupNo description published

This tool published no description. Forge does not invent one.

policy_researchResearch coverage policies and criteria. Use this for policy search, fetching one policy by ID, searching extracted criteria, reviewing policy changes, mapping state to MAC jurisdiction, or comparing how Medicare contractors (MACs) cover the same procedure codes side by side. This replaces several…

Research coverage policies and criteria. Use this for policy search, fetching one policy by ID, searching extracted criteria, reviewing policy changes, mapping state to MAC jurisdiction, or comparing how Medicare contractors (MACs) cover the same procedure codes side by side. This replaces several…

No input schema was published for this tool.

claim_validationValidate claim coverage, documentation requirements, denial risk, and optional policy-specific criteria in one workflow.

Validate claim coverage, documentation requirements, denial risk, and optional policy-specific criteria in one workflow.

No input schema was published for this tool.

prior_auth_researchCheck, start, or poll payer prior-authorization research without exposing separate task-management tools.

Check, start, or poll payer prior-authorization research without exposing separate task-management tools.

No input schema was published for this tool.

drug_formulary_researchSearch commercial pharmacy-benefit evidence from CVS Caremark, Express Scripts, and UnitedHealthcare / Optum Rx.

Search commercial pharmacy-benefit evidence from CVS Caremark, Express Scripts, and UnitedHealthcare / Optum Rx.

No input schema was published for this tool.

compliance_reviewReview compliance dashboard state, list unreviewed policy changes, or acknowledge changes when explicitly requested.

Review compliance dashboard state, list unreviewed policy changes, or acknowledge changes when explicitly requested.

No input schema was published for this tool.

webhook_managementList, create, update, delete, or test webhook endpoints. Use only when the user is explicitly managing webhook configuration. Backwork delivers one event type, compliance.acknowledged; policy-change webhooks are not sent.

List, create, update, delete, or test webhook endpoints. Use only when the user is explicitly managing webhook configuration. Backwork delivers one event type, compliance.acknowledged; policy-change webhooks are not sent.

No input schema was published for this tool.

system_healthCheck Backwork API health and dependency status. Use for diagnostics, not for coverage research.

Check Backwork API health and dependency status. Use for diagnostics, not for coverage research.

No input schema was published for this tool.

7 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for Backwork: Medicare and payer medical policy, prior authorization, claim risk, and medical codes. Hosted OAuth remote or local stdio.

Keywords
mcpmcp-servermodel-context-protocolhealthcareprior-authorizationmedical-policypayermedicarecoveragemedical-codesbackwork
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-05 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in health & fitness