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/denialbot

NPM · @COVERAGE-UNLOCKED/DENIALBOT-MCP

Insurance denial code lookup, appeal letter generation, and denial analysis for AI agents.

0 this week 75 Trust /100

Last scanned (30 minutes ago)

Scores higher than 50% 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 & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 248 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability85
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 567 tokens (~94/item across 6 items; 6 tools + 0 resources), lean.Pass
  • 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −6
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
  • 20 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.83 → pass security
  • 15 Oct 26 −3
    • Stability: pass → 0.80 functional
  • 14 Oct 26 +1
    • Stability: 0.97 → pass security
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/@coverage-unlocked/denialbot-mcp@1.0.1

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 · 6 exposed · ~567 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_letter ~87

Analyze raw denial letter text to identify denial codes, classify the denial type, assess urgency, and recommend next steps. Use when a user has received a denial letter and wants to understand it, or needs help identifying what codes apply.

NameTypeReqDescription
denial_textstringyesThe full text of the insurance denial letter or Explanation of Benefits (EOB). Can be pasted directly from the document.

No output schema declared.

No examples provided.

check_api_status ~29

Check the operational status of the DenialBot API. Use to verify connectivity before making other calls.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_usage ~25

Check current API usage, quota remaining, and tier information for the authenticated API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

generate_appeal_letter ~209

Generate a professional 800-1200 word insurance appeal letter with regulatory citations (ACA, ERISA), clinical evidence references, confidence score, and estimated success rate. Use when a user wants help writing an appeal, has been denied coverage, or needs a template appeal letter.

NameTypeReqDescription
denial_codestringyesThe denial code from the insurance company (e.g., 'CO-18')
denial_reasonstring–The stated reason for denial from the insurance company's explanation of benefits (EOB)
diagnosisstringyesThe patient's medical diagnosis (e.g., 'Type 2 Diabetes Mellitus with peripheral neuropathy')
insurance_companystring–The insurance company name (e.g., 'Blue Cross Blue Shield of Illinois')
patient_summarystring–Brief clinical summary of the patient's situation, relevant history, and why the procedure is needed
procedurestringyesThe denied medical procedure or service (e.g., 'Advanced continuous glucose monitoring system')

No output schema declared.

No examples provided.

list_denial_codes ~117

List all 50+ insurance denial codes in the database. Returns code, description, and category for each. Optionally filter by category. Use when a user wants to browse codes, find the right code for their situation, or asks 'what are the common denial codes'.

NameTypeReqDescription
categorystring–Optional filter by category: 'Coverage', 'Medical Necessity', 'Procedure Related', 'Cost-Sharing', 'Administrative', 'Patient Issues', 'Other Adjudication', 'Frequency Limits'. Omit to list all codes.

No output schema declared.

No examples provided.

lookup_denial_code ~100

Look up detailed information about an insurance denial code including description, category, appeal strategy, success rate, recommended actions, and supporting regulations. Use when a user mentions a specific denial code or asks about a denial reason.

NameTypeReqDescription
codestringyesThe denial code to look up (e.g., 'CO-18', 'PR-1', 'OA-23', 'MA-04'). Supports all standard CARC/RARC denial code formats.

No output schema declared.

No examples provided.

Install

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

io.github.edgeedgehq/denialbot runs locally as an npm package, launched with npx -y @coverage-unlocked/denialbot-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 · @coverage-unlocked/denialbot-mcp

# add to Claude Code
claude mcp add edgeedgehq-denialbot -- npx -y @coverage-unlocked/denialbot-mcp
Common questions

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

io.github.edgeedgehq/denialbot is an MCP server listed in the public MCP registry as io.github.edgeedgehq/denialbot. Insurance denial code lookup, appeal letter generation, and denial analysis for AI agents. This page covers its npm package (@coverage-unlocked/denialbot-mcp).

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

io.github.edgeedgehq/denialbot scores 75 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/denialbot MCP server expose?

io.github.edgeedgehq/denialbot exposes 6 tools: lookup_denial_code, list_denial_codes, generate_appeal_letter, analyze_denial_letter, check_api_status, check_usage. Their descriptions and schemas cost roughly 567 tokens of context every time the server is loaded.

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

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

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