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.

Insurance Denials

NPM · @PIPEWORX/MCP-INSURANCE-DENIALS · 2 COMPONENTS

US health-insurance claim denials and appeal outcomes, by insurer.

+3 this week 81 Trust /100

Last scanned (15 hours ago)

Scores higher than 69% of npm servers

Category Health and Science

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-insurance-denials). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1039 tokens (~259/item across 4 items; 4 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 Management23
  • Stability observed for 7 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 4 Nov 26 +1

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

  • 3 Nov 26 +26
    • Known CVEs: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 2 Nov 26 −24
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: pass → unverified ▼ functional
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 1 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 78

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-insurance-denials@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-insurance-denials
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-insurance-denials/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637453839
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:cfa20e2ce3f6f73a22e0c5a95689d00722b5eb28df96126734150b26c2097ebdc31e89963c4e19955e251b2e50c3d12509ad8e495c3faf03750434bad

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~984 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
insurer_appeal_outcomes ~327

Does appealing a denied health-insurance claim work? Marketplace issuers ranked by the share of appeals that were OVERTURNED in the patient's favour, plan year 2026. Answers "is it worth appealing a denied claim", "what percentage of insurance appeals succeed", "how often does <company> reverse a denial", and which insurer most often changes its mind. Returns internal appeals (decided by the insurer itself) and external appeals (decided by an independent reviewer) separately, with how many were filed, how many were overturned, and the overturn percentage — the two differ a lot and the external number is the independent one. Sourced from the CMS Transparency in Coverage Public Use File; covers HealthCare.gov states only, so state-run exchanges such as California and New York are not present.

NameTypeReqDescription
appeal_typestring–"internal" (default, decided by the insurer) or "external" (decided by an independent reviewer).
limitnumber–How many issuers to return (default 20, max 200).
marketstring–Restrict to issuers participating in "medical" / "QHP", "dental" / "SADP", or "SHOP". Selects issuers rather than splitting their figures. Omit for all.
orderstring–"highest" (default) ranks the most-overturned first; "lowest" ranks the least.
statestring–Two-letter US state code to filter by, e.g. "TX". Omit for all states.

No output schema declared.

No examples provided.

insurer_denial_coverage ~102

What this data covers before you rely on it: the plan year, how many issuers and states are present, which states are included, and the counts of issuers whose denial or appeal figures CMS suppressed. Use to check whether a state or insurer is in scope at all, and to tell "we hold no data for this state" apart from "this state's insurers deny nothing" — the CMS Transparency in Coverage file covers HealthCare.gov states only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

insurer_denial_profile ~196

Everything reported for ONE named health insurer: claims received and denied in and out of network, the denial rate, and both internal and external appeal outcomes, for plan year 2026. Use when a caller names a company — "how often does Ambetter deny claims", "Blue Cross denial rate in Texas", "what happens if I appeal with Oscar". Matches on the insurer's name and is forgiving about punctuation, case and partial names; an issuer selling in several states returns one entry per state, since CMS reports these figures per issuer per state. Sourced from the CMS Transparency in Coverage Public Use File; covers HealthCare.gov states only.

NameTypeReqDescription
insurerstringyesInsurer name or part of one, e.g. "Ambetter", "Blue Cross Blue Shield of Texas", "oscar".
statestring–Optional two-letter state code to narrow a multi-state insurer, e.g. "TX".

No output schema declared.

No examples provided.

insurer_denial_rates ~359

Which health insurers deny the most claims — US marketplace issuers ranked by the share of in-network claims they denied, for plan year 2026. Answers "what percentage of claims does my insurance company deny", "which insurer denies the most", "how often does <company> deny claims", and comparisons between insurers in a state. Returns each issuer with claims received, claims denied, the denial rate as a percentage, and how many marketplace plans it offers. Filter by state (two-letter code) or by market — medical plans (Individual QHP), standalone dental (Individual SADP, which denies at much higher rates than medical), or small-group SHOP; the market filter selects which ISSUERS to include, since CMS publishes these counts per issuer rather than per market. Sourced from the CMS Transparency in Coverage Public Use File, which insurers report into under federal rule; covers HealthCare.gov states only, so issuers on state-run exchanges such as California and New York are not present.

NameTypeReqDescription
limitnumber–How many issuers to return (default 20, max 200).
marketstring–Restrict to issuers participating in a market: "medical" / "QHP", "dental" / "SADP" for standalone dental, or "SHOP" for small-group. Selects issuers; it does not split an issuer's claim counts, whic…
orderstring–"highest" (default) ranks the biggest deniers first; "lowest" ranks the smallest.
statestring–Two-letter US state code to filter by, e.g. "TX", "FL". Omit for all states.

No output schema declared.

No examples provided.

Install

How do I install the Insurance Denials MCP server?

Insurance Denials runs locally as an npm package, launched with npx -y @pipeworx/mcp-insurance-denials. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-insurance-denials

# add to Claude Code
claude mcp add pipeworx-io-insurance-denials -- npx -y @pipeworx/mcp-insurance-denials
Common questions

What is the Insurance Denials MCP server?

Insurance Denials is an MCP server listed in the public MCP registry as io.github.pipeworx-io/insurance-denials. US health-insurance claim denials and appeal outcomes, by insurer. This page covers its npm package (@pipeworx/mcp-insurance-denials).

Is the Insurance Denials MCP server safe to use?

Insurance Denials scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Insurance Denials MCP server expose?

Insurance Denials exposes 4 tools: insurer_denial_rates, insurer_appeal_outcomes, insurer_denial_profile, insurer_denial_coverage. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.

Is the Insurance Denials MCP server still maintained?

Insurance Denials is still listed as active in the MCP registry. We last reached this channel on 5 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 Insurance Denials MCP server under?

Insurance Denials declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.