io.github.edgeedgehq/coverageunlocked
NPM · COVERAGEUNLOCKED-MCP · SCANNED SEP 20
AI-powered insurance denial appeals. Win probabilities, payer intelligence & regulatory leverage.
Available components
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 172 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 Management90
- Stability observed for 27 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 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
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
claude mcp add edgeedgehq-coverageunlocked -- npx -y coverageunlocked-mcp
{
"mcpServers": {
"edgeedgehq-coverageunlocked": {
"command": "npx",
"args": [
"-y",
"coverageunlocked-mcp"
]
}
}
} {
"servers": {
"edgeedgehq-coverageunlocked": {
"command": "npx",
"args": [
"-y",
"coverageunlocked-mcp"
]
}
}
} codex mcp add edgeedgehq-coverageunlocked -- npx -y coverageunlocked-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"edgeedgehq-coverageunlocked": {
"type": "local",
"command": [
"npx",
"-y",
"coverageunlocked-mcp"
],
"enabled": true
}
}
} openclaw mcp add edgeedgehq-coverageunlocked --command npx --arg -y --arg coverageunlocked-mcp
mcp_servers:
edgeedgehq-coverageunlocked:
command: "npx"
args: ["-y", "coverageunlocked-mcp"] {
"McpServers": {
"edgeedgehq-coverageunlocked": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"coverageunlocked-mcp"
]
}
}
} assistant mcp add edgeedgehq-coverageunlocked -t stdio -c npx -a -y coverageunlocked-mcp
{
"mcpServers": {
"edgeedgehq-coverageunlocked": {
"command": "npx",
"args": [
"-y",
"coverageunlocked-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CoverageUnlocked API key for Pro access. Free tier: 10 queries/day with basic results. Get Pro at https://app.coverageunlocked.com/mcp |
| cpt_code | string | yes | The CPT or HCPCS code that was denied (e.g., "99214", "70553", "E0601") |
| denial_reason | string | – | The reason given for the denial, if available |
| payer | string | – | Insurance company name (e.g., "UnitedHealthcare", "Anthem", "Aetna", "Cigna", "Humana", "BCBS") |
| state | string | – | 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?"
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CoverageUnlocked API key for Pro access |
| cpt_code | string | yes | The CPT or HCPCS code to check |
| payer | string | – | Insurance company name |
| prior_auth_obtained | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CoverageUnlocked Pro API key required for full strategy. Free tier gets a preview. |
| cpt_code | string | yes | The CPT or HCPCS code that was denied |
| denial_reason | string | – | The denial reason provided by the payer |
| payer | string | yes | Insurance company that denied the claim |
| state | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CoverageUnlocked Pro API key. Free tier gets a summary. |
| payer | string | yes | Insurance 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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CoverageUnlocked Pro API key. Free tier gets basic deadlines. |
| plan_type | string | – | Type of insurance plan |
| state | string | yes | Two-letter state code (e.g., "CA", "TX") or full state name |
No output schema declared.
No examples provided.
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 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.