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.

io.github.edgeedgehq/coverageunlocked

NPM · COVERAGEUNLOCKED-MCP

AI-powered insurance denial appeals. Win probabilities, payer intelligence & regulatory leverage.

0 this week 79 Trust /100

Last scanned (1 hour ago)

Scores higher than 62% 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 685 tokens (~137/item across 5 items; 5 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 5 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 0
    • Stability: 0.97 → pass security
  • 3 Nov 26 0
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • Stability: 0.97 → pass security
  • 27 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
  • 20 Oct 26 0
    • Stability: pass → 0.97 functional
  • 19 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
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/coverageunlocked-mcp@1.0.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~685 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
analyze_denial ~229

Analyze an insurance denial and get win probability, top denial reasons, and appeal guidance. Covers 489+ CPT codes across 9 procedure categories with data from 20 years of industry experience. Use this when someone asks about insurance denials, claim denials, appeal chances, or how to fight a denied claim.

NameTypeReqDescription
api_keystring–CoverageUnlocked API key for Pro access. Free tier: 10 queries/day with basic results. Get Pro at https://app.coverageunlocked.com/mcp
cpt_codestringyesThe CPT or HCPCS code that was denied (e.g., "99214", "70553", "E0601")
denial_reasonstring–The reason given for the denial, if available
payerstring–Insurance company name (e.g., "UnitedHealthcare", "Anthem", "Aetna", "Cigna", "Humana", "BCBS")
statestring–Two-letter state code (e.g., "CA", "TX", "NY") for state-specific regulatory leverage

No output schema declared.

No examples provided.

check_denial_risk ~119

Check the denial risk BEFORE submitting a claim. Returns the probability of denial and top risk factors for a given CPT code and payer. Use this when someone asks "will my claim be denied?" or "what's the risk of denial for this procedure?"

NameTypeReqDescription
api_keystring–CoverageUnlocked API key for Pro access
cpt_codestringyesThe CPT or HCPCS code to check
payerstring–Insurance company name
prior_auth_obtainedboolean–Whether prior authorization was obtained

No output schema declared.

No examples provided.

get_appeal_strategy ~134

Get a detailed appeal strategy for a denied insurance claim, including counter-arguments, regulatory citations, documentation requirements, and insider tips. Best results with CPT code + payer + state + denial reason.

NameTypeReqDescription
api_keystring–CoverageUnlocked Pro API key required for full strategy. Free tier gets a preview.
cpt_codestringyesThe CPT or HCPCS code that was denied
denial_reasonstring–The denial reason provided by the payer
payerstringyesInsurance company that denied the claim
statestring–Two-letter state code for state-specific leverage

No output schema declared.

No examples provided.

get_payer_intelligence ~104

Get behavioral intelligence on a specific insurance payer — their denial patterns, known tactics, and counter-strategies. Covers UnitedHealthcare, Anthem, Aetna, Cigna, Humana, BCBS, TRICARE, and state-specific plans.

NameTypeReqDescription
api_keystring–CoverageUnlocked Pro API key. Free tier gets a summary.
payerstringyesInsurance company name (e.g., "UnitedHealthcare", "Anthem", "Aetna")

No output schema declared.

No examples provided.

get_regulatory_leverage ~99

Get state-specific regulatory leverage for insurance denial appeals — appeal deadlines, prompt payment laws, mental health parity enforcement, and external review options. Covers 15 states.

NameTypeReqDescription
api_keystring–CoverageUnlocked Pro API key. Free tier gets basic deadlines.
plan_typestring–Type of insurance plan
statestringyesTwo-letter state code (e.g., "CA", "TX") or full state name

No output schema declared.

No examples provided.

Install

How do I install the io.github.edgeedgehq/coverageunlocked MCP server?

io.github.edgeedgehq/coverageunlocked runs locally as an npm package, launched with npx -y coverageunlocked-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · coverageunlocked-mcp

# add to Claude Code
claude mcp add edgeedgehq-coverageunlocked -- npx -y coverageunlocked-mcp
Common questions

What is the io.github.edgeedgehq/coverageunlocked MCP server?

io.github.edgeedgehq/coverageunlocked is an MCP server listed in the public MCP registry as io.github.edgeedgehq/coverageunlocked. AI-powered insurance denial appeals. Win probabilities, payer intelligence & regulatory leverage. This page covers its npm package (coverageunlocked-mcp).

Is the io.github.edgeedgehq/coverageunlocked MCP server safe to use?

io.github.edgeedgehq/coverageunlocked scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.edgeedgehq/coverageunlocked MCP server expose?

io.github.edgeedgehq/coverageunlocked exposes 5 tools: analyze_denial, check_denial_risk, get_appeal_strategy, get_payer_intelligence, get_regulatory_leverage. Their descriptions and schemas cost roughly 685 tokens of context every time the server is loaded.

Is the io.github.edgeedgehq/coverageunlocked MCP server still maintained?

io.github.edgeedgehq/coverageunlocked 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 io.github.edgeedgehq/coverageunlocked MCP server under?

io.github.edgeedgehq/coverageunlocked declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.