Appeal My Claim
REMOTE · GOODTURN-MCP.PAGES.DEV
Appeal a denied US health insurance claim: denial codes, rights, deadlines and a draft letter.
Available components
Last scanned (14 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1051 tokens (~262/item across 4 items; 4 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 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 4 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
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 →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 7 Nov 26 0
- Stability: 0.97 → pass security
- 6 Nov 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
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 21 Nov 2026 · Probed https://goodturn-mcp.pages.dev/appealmyclaim/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=goodturn-mcp.pages.dev | CN=YE1,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 590c8ade87714dff31f31ce636eafc7da48 |
| SANs: *.goodturn-mcp.pages.dev, goodturn-mcp.pages.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of goodturn-mcp.pages.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| pages.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://goodturn-mcp.pages.dev/appealmyclaim/mcp | Verified | 200 | |
| http (plaintext) | http://goodturn-mcp.pages.dev/appealmyclaim/mcp | HTTPS enforced | 301 | https://goodturn-mcp.pages.dev/appealmyclaim/mcp |
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 →
draft_appeal_letter Draft an appeal letter for the user to review and send ~360
Draft an appeal letter for the user to review and send. For requests like "my insurer denied my MRI as not medically necessary, help me appeal" or "write an appeal letter for an out-of-network denial". Returns a letter as plain text with [brackets] for anything not given, a checklist of what to attach (denial notice, doctor's letter of medical necessity, records), and tips. It never sends or files anything.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | – | Claim or reference number. |
| date | string | – | Date of service. |
| denial_code | string | – | The reason code on the notice, like CO-50 or PR-197. Picks the reason when reason is left out, and is quoted in the letter. |
| denial_date | string | – | Date on the denial notice. |
| details | string | – | A sentence or two in the user's words on why the care should be covered. |
| doctor | string | – | Treating doctor's name. |
| member_id | string | – | Member ID or Medicare number. |
| name | string | – | Member's name. |
| plan | string | – | Insurer or plan name. |
| plan_type | string | – | Same values as plan_type in get_appeal_rights. Changes the wording for Medicare. |
| provider | string | – | Hospital, clinic or provider name. |
| reason | string | – | Why the claim was denied: medical_necessity, emergency (said it wasn't an emergency), experimental, out_of_network, prior_auth, coding or generic. Required unless denial_code is given. |
| service | string | – | The care that was denied, like "MRI of the right knee". |
| urgent | string | – | Set to yes to ask for an expedited review. |
No output schema declared.
No examples provided.
explain_denial_code Explain the denial codes on an Explanation of Benefits ~166
Explain the denial codes on an Explanation of Benefits. For requests like "my EOB says CO-50, what does that mean?", "what is denial code PR 204?" or "what does N130 mean?". Returns each code in plain words, who usually fixes it (the provider's billing office, an appeal, or the user), whether the provider can bill the user for it (from the group code CO, PR, OA or PI), and a letter link when an appeal fits.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | One to four codes from the notice, like CO-50, PR 204, 197 or N130. |
| plan_type | string | – | Same values as plan_type in get_appeal_rights. Carried into the letter link. |
No output schema declared.
No examples provided.
get_appeal_deadlines How long someone has to appeal, and how fast the plan must decide ~167
How long someone has to appeal, and how fast the plan must decide. For requests like "how long do I have to appeal?", "when is my appeal due?" or "how fast does my insurer have to answer?". With the date on the denial notice, gives an approximate file-by date. The date on the user's own notice is the one that counts.
| Name | Type | Req | Description |
|---|---|---|---|
| denial_date | string | – | Date on the denial notice, like 2026-09-01, 09/01/2026 or September 1, 2026. |
| plan_type | string | – | Same values as plan_type in get_appeal_rights. Default: most private plans. |
| urgent | string | – | Set to yes if waiting could seriously harm the person's health. |
No output schema declared.
No examples provided.
get_appeal_rights Appeal rights, steps and free help for a plan type and state ~199
Appeal rights, steps and free help for a plan type and state. For requests like "what are my appeal rights in California?", "my insurer denied my claim, what can I do?" or "how do Medicare appeals work?". Returns who decides, the steps (internal appeal, external review, Medicare levels or Medicaid fair hearing), deadlines, and where to get free help, including the state insurance department. If the plan type is not known, leave it out to get the rules for most private plans.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_type | string | – | Plan type: marketplace, employer, employer_insured, employer_self_funded, medicare, medicare_advantage, part_d or medicaid. Everyday words work too, like "job", "Obamacare" or "Medi-Cal". Default: mo… |
| state | string | – | US state name or two-letter code, like California or CA. Puerto Rico works too. |
No output schema declared.
No examples provided.
How do I install the Appeal My Claim MCP server?
Appeal My Claim is a hosted endpoint at https://goodturn-mcp.pages.dev/appealmyclaim/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 · goodturn-mcp.pages.dev
claude mcp add --transport http goodturnstudio-appealmyclaim 'https://goodturn-mcp.pages.dev/appealmyclaim/mcp'
What is the Appeal My Claim MCP server?
Appeal My Claim is an MCP server listed in the public MCP registry as io.github.GoodTurnStudio/appealmyclaim. Appeal a denied US health insurance claim: denial codes, rights, deadlines and a draft letter. This page covers its hosted endpoint (https://goodturn-mcp.pages.dev/appealmyclaim/mcp).
Is the Appeal My Claim MCP server safe to use?
Appeal My Claim scores 83 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 Appeal My Claim MCP server expose?
Appeal My Claim exposes 4 tools: get_appeal_rights, get_appeal_deadlines, explain_denial_code, draft_appeal_letter. Their descriptions and schemas cost roughly 892 tokens of context every time the server is loaded.
Does the Appeal My Claim MCP server require authentication?
No. We connected to Appeal My Claim without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Appeal My Claim MCP server still maintained?
Appeal My Claim is still listed as active in the MCP registry. We last reached this channel on 21 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 Appeal My Claim MCP server?
VerifyMCP ran 13 checks on Appeal My Claim, 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.