# DenialPath (remote · denialpath.vercel.app)

Deterministic CMS NCCI/MUE claim scrubbing and CARC/RARC denial explanations, cited to source.

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `denialpath.vercel.app`: 67/100 (this document), [markdown](https://verifymcp.io/servers/maxbeech-denialpath/api-mcp.md), [page](https://verifymcp.io/servers/maxbeech-denialpath/api-mcp)

## Channel facts

- Endpoint: `https://denialpath.vercel.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1658 tokens (~276/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http maxbeech-denialpath https://denialpath.vercel.app/api/mcp
```

### Codex

```toml
[mcp_servers.maxbeech-denialpath]
url = "https://denialpath.vercel.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "maxbeech-denialpath": {
      "type": "remote",
      "url": "https://denialpath.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add maxbeech-denialpath --url https://denialpath.vercel.app/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  maxbeech-denialpath:
    url: "https://denialpath.vercel.app/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "maxbeech-denialpath": {
      "type": "http",
      "url": "https://denialpath.vercel.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-08-02 (score 67, +1)

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

### 2026-07-31 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

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

### 2026-07-27 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (6)

### `check_claim` (~285 tokens)

Scrub a claim against the NCCI procedure-to-procedure (PTP) edits and medically unlikely edits (MUE) in force on its date of service. Deterministic: no model, so identical input always returns an identical verdict. Every finding.status is one of pass (checked against a real edit and clean), fail (an edit fires), bypassed (an edit fires but a modifier already on the line legitimately resolves it), or no_data (we hold no edit for this code or pair in our dataset). no_data is NOT a pass: treat it as unchecked, since CMS may still deny the line under an edit outside our loaded subset. summary.clean is true only when every finding is pass and none are no_data - never report a claim clean because nothing failed if some lines were never checked. The response echoes editQuarter (the CMS quarter version the verdict was computed against) and coverage (how many PTP pairs and MUE codes are loaded), so you can tell a caller exactly what was checked. Free, no API key needed; a key only raises the rate limit.

Input parameters:

- `dateOfService` (string, required): ISO yyyy-mm-dd. Selects which CMS edit quarter applies.
- `lines` (array, required): The billed lines on this claim.
- `payerSlug` (string): Optional payer slug for context. Does not change the PTP/MUE verdict.

### `explain_denial` (~220 tokens)

Explain a CARC (Claim Adjustment Reason Code) and any RARCs (Remittance Advice Remark Codes) from a remittance: plain meaning, ranked corrective actions, and whether an appeal is worth filing. found:false means we do not hold that CARC in our dataset (X12 publishes far more codes than we have curated) - the response still returns the group-code meaning when a group prefix (CO/PR/OA/PI) was supplied, and note explains the gap rather than leaving it silent. unknownRarc reports, rather than silently drops, any RARC you passed that we do not hold. Passing payer additionally attaches that payer's appeal deadline where we hold one. Free, no API key needed.

Input parameters:

- `carc` (string, required): CARC code, with or without a group prefix, e.g. "CO-45" or "45".
- `payer` (string): Optional payer slug, to attach a timely-filing appeal deadline.
- `rarc` (array): Optional RARC codes on the same remittance line.

### `get_ncci_edits` (~264 tokens)

Look up NCCI procedure-to-procedure (PTP) edits, in two modes. Pair mode: pass column1, column2 (either order) and dateOfService to check whether that specific pair bundles on that date; status is no_data (we hold no edit for this pair in our dataset - NOT confirmation CMS has none), not_applicable (we hold the edit but it does not apply on this date, either outside its effective/deletion window or modifierIndicator "9" meaning the edit is deleted or never applicable), or applies. List mode: pass code alone to get every pair in the dataset involving that code, in either column, with no date filtering. modifierIndicator "0" means no modifier may ever bypass the edit; "1" means a modifier may bypass it, but only where the services were genuinely distinct. Free, no API key needed.

Input parameters:

- `code` (string): List mode: a single code, returning every pair involving it.
- `column1` (string): A CPT/HCPCS code. Pair mode: use with column2 and dateOfService.
- `column2` (string): The other code in the pair.
- `dateOfService` (string): ISO yyyy-mm-dd. Required in pair mode.

### `get_mue` (~171 tokens)

Look up the medically unlikely edit (MUE) unit limit for a single CPT/HCPCS code. status is found or no_data; no_data means we hold no MUE value for this code in our dataset, not that CMS publishes none. When found, the returned limit.mai (adjudication indicator: "1" line edit - denies the excess units on the line; "2" date-of-service absolute - never payable above the limit on that date, not even on appeal; "3" date-of-service clinical - may be allowed above the limit with supporting documentation) governs what a biller can do above the limit, explained in limit.maiMeaning. Free, no API key needed.

Input parameters:

- `code` (string, required): CPT/HCPCS code, e.g. "36415".

### `draft_appeal` (~361 tokens)

Generate an appeal letter for a denial, assembled deterministically from cited facts. REQUIRES A PRO OR SCALE PLAN. Called by an anonymous caller or a key on the free plan, this returns an upgrade_required error naming the pricing page - it never fabricates or partially generates a letter for a caller who cannot access the feature. The letter argues the billing question only: it never asserts anything about the patient's clinical condition. Any fact only the practice holds (providerName, claimNumber, dateOfService, codes, the signature) that is not supplied is rendered as an explicit "[TO BE COMPLETED BY PRACTICE]" placeholder in the letter body and listed by name in placeholders, never invented. grounded is true only when we hold the CARC supplied and could argue it with our own corrective-action data; when false, the letter still assembles around payer/claim details and any practiceNote given, but the substantive grounds section is left as a placeholder for the practice to write.

Input parameters:

- `carc` (string, required): CARC code from the remittance, e.g. "CO-45" or "45".
- `claimNumber` (string): Optional. Rendered as a placeholder if omitted.
- `codes` (array): Optional procedure codes at issue, numeric reference only.
- `dateOfService` (string): Optional. Rendered as a placeholder if omitted.
- `payerSlug` (string): Optional payer slug, to cite that payer's appeal policy and window.
- `practiceNote` (string): Optional free-text detail from the practice, appended to the argument section.
- `providerName` (string): Optional. Rendered as a placeholder if omitted.
- `rarc` (array): Optional RARC codes on the same remittance line.

### `get_timely_filing` (~114 tokens)

Days remaining to file an initial claim (or, if already past, how far over) for a payer given a date of service. daysRemaining and expired are null when we hold no published timely filing limit for that payer, which is common since many limits are contract-specific - check note before treating the result as an actual deadline. Free, no API key needed.

Input parameters:

- `dateOfService` (string, required): ISO yyyy-mm-dd.
- `payer` (string, required): Payer slug, e.g. "aetna".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/maxbeech-denialpath/api-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 65
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 63
- 2026-07-26: 62

## Links

- Remote endpoint: https://denialpath.vercel.app/api/mcp
- Website: https://denialpath.vercel.app/developers/mcp
- Changelog RSS feed: https://verifymcp.io/servers/maxbeech-denialpath/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/maxbeech-denialpath/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/maxbeech-denialpath/api-mcp