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.

com.coverage-rights/coverage-rights

REMOTE · WWW.COVERAGE-RIGHTS.COM

Insurer denial rates, appeal outcomes by treatment and condition, and appeal rights lookups.

−1 this week 85 Trust /100

Last scanned (19 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1757 tokens (~175/item across 10 items; 10 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 Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool coverage: 78% → 57% ▼ functional
    • Schema quality: 159 → 175 ▼ functional
    • Server version: 1.3.0 → 1.4.0 functional
    • New tool “prepare_knee_injection_evidence” functional
  • 4 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_drug_playbook” rewrote its description, which is the text the model reads security
    • Tool “get_insurer_metrics” now declares an output schema ▲ functional
    • Tool “get_state_external_review” now declares an output schema ▲ functional
    • Tool “get_treatment_outcomes” now declares an output schema ▲ functional
    • Tool “list_insurers” now declares an output schema ▲ functional
    • Tool “rank_denial_rates” now declares an output schema ▲ functional
    • Tool “search_outcomes” now declares an output schema ▲ functional
    • Tool “get_appeal_rights” now declares an output schema ▲ functional
    • Tool “get_condition_outcomes” now declares an output schema ▲ functional
    • Tool “get_drug_playbook” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Server version: 1.2.0 → 1.3.0 functional
    • “get_appeal_rights” reworded the description of “denial_reason” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “rank_denial_rates” rewrote its description, which is the text the model reads security
    • Tool “get_appeal_rights” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 78% ▼ functional
    • “get_appeal_rights” added an optional parameter “regulatory_state_basis” cosmetic
    • “get_appeal_rights” added an optional parameter “appeal_stage” cosmetic
    • “get_appeal_rights” added an optional parameter “current_status” cosmetic
    • “get_appeal_rights” added an optional parameter “drug_channel” cosmetic
    • “get_appeal_rights” added an optional parameter “employer_type” cosmetic
    • “get_appeal_rights” added an optional parameter “funding_status” cosmetic
    • “get_appeal_rights” added an optional parameter “regulatory_marker” cosmetic
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 · Probed https://www.coverage-rights.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.coverage-rights.com CN=YR2,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 RSA 2048 SHA256-RSA 690ef7f26cbbbf3d8f5dceb286a50abb350
SANs: www.coverage-rights.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.coverage-rights.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
coverage-rights.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://*.google-analytics.com; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data: https:; connect-src 'self' https://www.googletagmanager.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.google.com
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.coverage-rights.com/api/mcp Verified 200
http (plaintext) http://www.coverage-rights.com/api/mcp HTTPS enforced 308 https://www.coverage-rights.com/api/mcp
MCP tools · 10 exposed · ~1,135 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
get_appeal_rights ~260

Deterministically resolve the governing appeal route, missing facts, filing recipient, deadlines, current external-review status, and verified grounds. Distinguishes Original Medicare, Medicare Advantage medical benefits, Part D pharmacy benefits, employer funding/governance, ACA, Medicaid, FEHB, TRICARE, and unknown coverage; unsupported or ambiguous routes fail closed.

NameTypeReqDescription
appeal_stagestring––
current_statusstring––
denial_reasonstringyesDenial category. For medication denials use 'prescription-drug' and supply the actual coverage program, benefit channel and routing facts. Applicable grounds and rule triggers depend on that route; p…
drug_channelstring–For a drug denial, whether the medical or pharmacy benefit applies
employer_typestring–Required to resolve job-based coverage
funding_statusstring–Required to resolve job-based state versus federal governance
insurer_slugstring–Insurer slug for insurer-specific stats
programstringyesPlan type
regulatory_markerstring––
regulatory_state_basisstring––
statestring–Two-letter state code, e.g. 'ca'
NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
can_generate_paidbooleanyesExisting resolver capability flag, not payment acceptance or advice to purchase.
corpus_verification_notestringyes–
deadlinesarrayyes–
documents_to_gather–yes–
escalation_path–yes–
external_review_current_statusobjectyes–
external_review_trackstringyes–
filing_recipientstringyes–
groundsarrayyes–
missing_factsarrayyes–
next_actionobjectyes–
page–yes–
prefilled_appeal_url–yes–
primary_sourcesarrayyes–
route_confidencestringyes–
route_idstringyes–
route_labelstringyes–
statisticsarrayyes–
verified_ground_countintegeryes–
warnings–yes–
why_this_route–yes–

No examples provided.

get_condition_outcomes ~64

External-review outcomes for a medical condition: how often insurance denials involving this condition were overturned, plus the most-fought treatments for it.

NameTypeReqDescription
slugstringyesCondition slug, e.g. 'obesity', 'autism', 'hepatitis-c'
NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
conditionstring––
decisionsinteger––
errorstring–Lookup error text when _coverage.status is not_found or unsupported.
most_fought_treatmentsarray––
overturn_rate_pct–––
overturned–––
page––Existing free information page when a matching record is available.
sourceobject––

No examples provided.

get_drug_playbook ~107

Curated medication background, common denial patterns, preparation considerations, and available historical California review outcomes for covered GLP-1 and IBD drugs. Accepts a brand or generic name. Confirm current labeling, the actual benefit channel and plan criteria; the guide does not establish current coverage, an exception entitlement, an individual outcome, or an applicable deadline.

NameTypeReqDescription
drugstringyesBrand or generic drug name, e.g. 'Zepbound', 'ustekinumab'
NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
appeal_angles–––
appeal_rights_hintstring––
brandstring––
common_denial_patternsarray––
coveredarray––
errorstring–Lookup error text when _coverage.status is not_found or unsupported.
fda_approved_indications–––
genericstring––
notestring––
page––Existing free information page when a matching record is available.
published_outcomes–––
step_therapy_notestring––

No examples provided.

get_insurer_metrics ~83

Get an insurer's verified CY2025 prior-authorization metrics (denial rate, appeal overturn rate, decision times) from its own CMS-0057-F disclosure, plus contract/plan-level rows where collected. Includes source URLs and scope notes.

NameTypeReqDescription
slugstringyesInsurer slug from list_insurers, e.g. 'unitedhealthcare'
NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
contract_rowsarray––
errorstring–Lookup error text when _coverage.status is not_found or unsupported.
insurerstring––
page––Existing free information page when a matching record is available.
rollup–––
rollup_statusstring––

No examples provided.

get_state_external_review ~86

How a state's external review process works: filing deadline, regulator contact, and key facts. Verified detail currently covers 10 states (CA, TX, FL, NY, PA, IL, OH, GA, NC, MI); other states return the covered list.

NameTypeReqDescription
statestringyesTwo-letter state code, e.g. 'ca', 'ny', 'fl'
NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
covered–––
errorstring–Lookup error text when _coverage.status is not_found or unsupported.
filing_deadlineobject––
filing_deadline_days–––
notes–––
page––Existing free information page when a matching record is available.
phonestring––
primary_sourcesarray––
processstring––
regulatorstring––
regulator_url–––
statestring––
summarystring––

No examples provided.

get_treatment_outcomes ~116

External-review outcomes for a treatment: how often insurer denials of this treatment/drug/procedure were overturned by independent reviewers (42,749 published CA IMR decisions, 2001–2026). Accepts a category slug (e.g. 'pharmacy') or specific treatment slug (e.g. 'zepbound', 'speech-therapy').

NameTypeReqDescription
slugstringyesTreatment slug, e.g. 'zepbound', 'pharmacy', 'speech-therapy'. Use search_outcomes to find slugs.
NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
by_conditionarray––
by_denial_reasonarray––
decisionsinteger––
errorstring–Lookup error text when _coverage.status is not_found or unsupported.
overturn_rate_pct–––
overturned–––
page––Existing free information page when a matching record is available.
sourceobject––
subcategoriesarray––
treatmentstring––
typestring––

No examples provided.

list_insurers ~33

List tracked U.S. health insurers with whether verified CMS-0057-F prior-authorization metrics are available for each.

Input schema present but exposes no named parameters.

NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
insurersarrayyes–

No examples provided.

prepare_knee_injection_evidence ~246

Prepare a free, category-level evidence checklist for a knee osteoarthritis hyaluronic-acid injection denial using routing facts, injection-series status, and record availability categories. Reuses the existing knee denial preparation kit. Does not inspect records or verify an insurer's specific criteria, provide clinical recommendations, draft an appeal, calculate deadlines, or estimate success. Send only the schema's bounded categories; never send names, identifiers, record text, or uploaded documents. Missing routing facts and unsupported routes remain explicit holds.

NameTypeReqDescription
appeal_stagestring––
current_statusstring––
denial_reasonstring––
drug_channelstring–This checklist covers medical-benefit injections only; do not infer the channel.
employer_typestring––
funding_statusstring––
injection_seriesstring––
programstring––
recordsarray–Category availability only, not evidence contents or a finding of sufficiency.
regulatory_markerstring––
regulatory_state_basisstring––
statestring–Lowercase state code from the notice or plan, not residence alone.
NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
criteria_checkobjectyes–
evidence_categoriesarrayyes–
evidence_sufficiency_assessedbooleanyes–
gapsarrayyes–
injection_seriesstringyes–
missing_factsarrayyes–
plan_criteria_verifiedbooleanyes–
preparation_scopestringyes–
public_resourcesobjectyes–
questions_for_clinician–yes–
questions_for_plan–yes–
reported_recordsarrayyes–
routeobjectyes–
statusstringyes–
unsupported_reasons–yes–
user_reported_categories_onlybooleanyes–

No examples provided.

rank_denial_rates ~57

Insurer prior-authorization denial rates (CY2025), ranked only within compatible reporting cohorts. Each row includes its cohort, rank within that cohort, exact source scope, calculation method, and source link. Never compare ranks across cohorts.

Input schema present but exposes no named parameters.

NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
page–yes–
rankingarrayyes–
ranking_basisstringyes–

No examples provided.

search_outcomes ~83

Search treatments (categories + specific drugs/procedures) and conditions by name. Returns slugs for get_treatment_outcomes / get_condition_outcomes plus headline overturn rates.

NameTypeReqDescription
limitinteger–Max results per type (default 10)
querystringyesSearch text, e.g. 'wegovy', 'back pain', 'imaging'
NameTypeReqDescription
_coverageobjectyes–
_notestringyes–
corpusobjectyes–
resultsarrayyes–
sourceobjectyes–

No examples provided.

Install

How do I install the com.coverage-rights/coverage-rights MCP server?

com.coverage-rights/coverage-rights is a hosted endpoint at https://www.coverage-rights.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.coverage-rights.com

# add to Claude Code
claude mcp add --transport http com-coverage-rights-coverage-rights 'https://www.coverage-rights.com/api/mcp'
Common questions

What is the com.coverage-rights/coverage-rights MCP server?

com.coverage-rights/coverage-rights is an MCP server listed in the public MCP registry as com.coverage-rights/coverage-rights. Insurer denial rates, appeal outcomes by treatment and condition, and appeal rights lookups. This page covers its hosted endpoint (https://www.coverage-rights.com/api/mcp).

Is the com.coverage-rights/coverage-rights MCP server safe to use?

com.coverage-rights/coverage-rights scores 85 out of 100 on VerifyMCP. 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 com.coverage-rights/coverage-rights MCP server expose?

com.coverage-rights/coverage-rights exposes 10 tools: list_insurers, get_insurer_metrics, rank_denial_rates, get_treatment_outcomes, get_condition_outcomes, and 5 more. Their descriptions and schemas cost roughly 1,135 tokens of context every time the server is loaded.

Does the com.coverage-rights/coverage-rights MCP server require authentication?

No. We connected to com.coverage-rights/coverage-rights without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.coverage-rights/coverage-rights MCP server still maintained?

com.coverage-rights/coverage-rights 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 did VerifyMCP test on the com.coverage-rights/coverage-rights MCP server?

VerifyMCP ran 13 checks on com.coverage-rights/coverage-rights, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.