coverage-rights

At a glance

Runs where

On their server. What you send to it goes to them.

What you need

Nothing: it answered without a login

Tools

10 tools

Its own safety labels

10 read-only

Memory it takes

About 2,800 tokens of your AI's memory, just for its tool descriptions

Largest answer

About 55.3 KB in our test

Speed

Average answer in our test: 71 ms

Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 10 Nov 2026.

Is coverage-rights MCP server safe?

• None of the hidden-instruction wordings we know were found in its 10 tool descriptions.
• Its error messages showed no secrets or internal details.
• All 10 of its tools are labeled read-only.
• Overall it scored 93/100 on 10 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What this test does not check

• Its source code and packages.
• What a tool quietly does behind the scenes, such as writing a file or calling another service.
• Instructions hidden inside live tool answers. We only look for those in tool descriptions.
• Hidden instructions worded in a way our list doesn't know yet.
• Tools that could change something. Those are read, never run.

What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection

Known security advisories

It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.

What it can do

10 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Every tool is described

  2 warnings

  • !get_appeal_rights: Inputs with no description: regulatory_marker, regulatory_state_basis, appeal_stage, current_status
  • !prepare_knee_injection_evidence: Inputs with no description: program, denial_reason, employer_type, funding_status, regulatory_marker, regulatory_state_basis, appeal_stage, current_status, injection_series
  note
• !
  Follows MCP best practices (not scored yet)

  1 tip (not scored)

  • !The tool list is about 47 KB (roughly 12k tokens). AI apps send it with every message, so it takes that much of the AI's memory before any work starts.
  note
• ✓
  ConnectsConnected in 222 ms
  pass
• ✓
  Ready for the newest MCP versionUses the latest MCP version (2026-07-28)
  pass
• ✓
  Lists its toolsFound 10 tools
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓list_insurers: Worked (122 ms)
  • ✓get_insurer_metrics: Answered with an error, probably because of our sample input: {"error":"Unknown insurer 'test'. Call list_insurers for valid slugs.","_note":"Public-source information and preparation guidance. Preserv…
  • ✓rank_denial_rates: Worked (78 ms)
  • ✓get_treatment_outcomes: Answered with an error, probably because of our sample input: {"error":"No treatment 'test'. Use search_outcomes to find valid slugs.","_note":"Public-source information and preparation guidance. Prese…
  • ✓get_condition_outcomes: Answered with an error, probably because of our sample input: {"error":"No condition 'test'. Use search_outcomes to find valid slugs.","_note":"Public-source information and preparation guidance. Prese…
  • ✓search_outcomes: Worked (56 ms)
  • ✓get_appeal_rights: Worked (58 ms)
  • ✓get_drug_playbook: Answered with an error, probably because of our sample input: {"error":"No curated playbook for 'test'.","covered":[{"brand":"Wegovy","generic":"semaglutide","slug":"wegovy"},{"brand":"Zepbound","gener…
  • and 2 more
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓get_insurer_metrics: Refused missing required input "slug" with a clear error
  • ✓get_insurer_metrics: Refused wrong type for "slug" with a clear error
  • ✓get_treatment_outcomes: Refused missing required input "slug" with a clear error
  • ✓get_treatment_outcomes: Refused wrong type for "slug" with a clear error
  • ✓get_condition_outcomes: Refused missing required input "slug" with a clear error
  • ✓get_condition_outcomes: Refused wrong type for "slug" with a clear error
  • ✓search_outcomes: Refused missing required input "query" with a clear error
  • ✓search_outcomes: Refused wrong type for "query" with a clear error
  • and 7 more
  pass
• ✓
  Tools work together

  3 chains working

  • ✓list_insurers → get_insurer_metrics: get_insurer_metrics found what list_insurers returned (slug = "unitedhealthcare")
  • ✓rank_denial_rates → get_insurer_metrics: get_insurer_metrics found what rank_denial_rates returned (slug = "centene")
  • ✓search_outcomes → get_treatment_outcomes: get_treatment_outcomes found what search_outcomes returned (slug = "advanced-lipoprotein-testing")
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 222 ms
  • ✓Listing tools took 135 ms
  • ✓Average tool answer: 71 ms
  • ✓list_insurers: Slowest tool: list_insurers (122 ms)
  pass
• ✓
  No secrets leakedChecked 35 error messages: no secrets or internal details
  pass

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 10 Nov 202693

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use coverage-rights, signed in with GitHub, one per person. Reviews never change the score.