# Insurance Denials (npm · @pipeworx/mcp-insurance-denials) US health-insurance claim denials and appeal outcomes, by insurer. - Trust score: 81/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-insurance-denials/insurance-denials-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-insurance-denials/insurance-denials-mcp) - npm · `@pipeworx/mcp-insurance-denials`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-insurance-denials/pipeworx-mcp-insurance-denials.md), [page](https://verifymcp.io/servers/pipeworx-io-insurance-denials/pipeworx-mcp-insurance-denials) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-insurance-denials` - Version: `0.2.1` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - No production dependencies, so there is no dependency health to assess. - **Provenance & Transparency**: 97/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-insurance-denials). - Clear OSI-approved license (MIT). - Actively maintained (last published 2 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 59/100 - AI-judged instruction clarity (good). - 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. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 23/100 - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## 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. ### Claude ```bash claude mcp add pipeworx-io-insurance-denials -- npx -y @pipeworx/mcp-insurance-denials ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-insurance-denials": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-insurance-denials" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-insurance-denials": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-insurance-denials" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-insurance-denials -- npx -y @pipeworx/mcp-insurance-denials ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-insurance-denials": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-insurance-denials" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-insurance-denials --command npx --arg -y --arg @pipeworx/mcp-insurance-denials ``` ### Hermes ```yaml mcp_servers: pipeworx-io-insurance-denials: command: "npx" args: ["-y", "@pipeworx/mcp-insurance-denials"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-insurance-denials": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-insurance-denials" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-insurance-denials -t stdio -c npx -a -y @pipeworx/mcp-insurance-denials ``` ### Other ```json { "mcpServers": { "pipeworx-io-insurance-denials": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-insurance-denials" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 81, +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. ### 2026-11-03 (score 80, +26) - [security improvement] Known CVEs: unverified → pass - [security improvement] Malware scan: unverified → pass - [functional improvement] Dependency health: unverified → pass ### 2026-11-02 (score 54, −24) - [security regression] Known CVEs: pass → unverified - [security regression] Malware scan: pass → unverified - [functional regression] Dependency health: pass → unverified - [functional improvement] Stability: unverified → 0.13 - [functional] Package version: 0.2.0 → 0.2.1 ### 2026-11-01 (score 78, 0) - [functional regression] Security disclosure: unverified → fail ### 2026-10-29 (score 78) First indexed and scored. ## MCP tools (4) ### `insurer_denial_rates` (~359 tokens) 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 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. Input parameters: - `limit` (number): How many issuers to return (default 20, max 200). - `market` (string): 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… - `order` (string): "highest" (default) ranks the biggest deniers first; "lowest" ranks the smallest. - `state` (string): Two-letter US state code to filter by, e.g. "TX", "FL". Omit for all states. ### `insurer_appeal_outcomes` (~327 tokens) 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 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. Input parameters: - `appeal_type` (string): "internal" (default, decided by the insurer) or "external" (decided by an independent reviewer). - `limit` (number): How many issuers to return (default 20, max 200). - `market` (string): Restrict to issuers participating in "medical" / "QHP", "dental" / "SADP", or "SHOP". Selects issuers rather than splitting their figures. Omit for all. - `order` (string): "highest" (default) ranks the most-overturned first; "lowest" ranks the least. - `state` (string): Two-letter US state code to filter by, e.g. "TX". Omit for all states. ### `insurer_denial_profile` (~196 tokens) 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. Input parameters: - `insurer` (string, required): Insurer name or part of one, e.g. "Ambetter", "Blue Cross Blue Shield of Texas", "oscar". - `state` (string): Optional two-letter state code to narrow a multi-state insurer, e.g. "TX". ### `insurer_denial_coverage` (~102 tokens) 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. ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-insurance-denials/pipeworx-mcp-insurance-denials#diagnostics ## Score history - 2026-11-05: 81 - 2026-11-04: 81 - 2026-11-03: 80 - 2026-11-02: 54 - 2026-11-01: 78 - 2026-10-31: 78 - 2026-10-30: 78 - 2026-10-29: 78 ## 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. ### What did VerifyMCP test on the Insurance Denials MCP server? VerifyMCP ran 16 checks on Insurance Denials, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - npm package: https://www.npmjs.com/package/@pipeworx/mcp-insurance-denials - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-insurance-denials - Repository: https://github.com/pipeworx-io/mcp-insurance-denials - Website: https://pipeworx.io/packs/insurance-denials - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-insurance-denials/pipeworx-mcp-insurance-denials.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-insurance-denials/pipeworx-mcp-insurance-denials/changelog.json - Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-insurance-denials/pipeworx-mcp-insurance-denials.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-insurance-denials/pipeworx-mcp-insurance-denials