Appeal My Claim MCP server
io.github.GoodTurnStudio/appealmyclaimGoodTurnStudiostreamable-httpv1.1.1Scanned
Appeal a denied US health insurance claim: denial codes, rights, deadlines and a draft letter.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Appeal My Claim MCP server can do
The Appeal My Claim MCP server is published by the GitHub account GoodTurnStudio. It has 4 tools. It can create or change data (2 tools: explain_denial_code and draft_appeal_letter), but cannot delete data. 2 tools only read.
4 tools bring in text other people can write (get_appeal_rights, get_appeal_deadlines, explain_denial_code and 1 more).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
draft_appeal_letterDraft an appeal letter for the user to review and send.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Draft an appeal letter for the user to review and send
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
explain_denial_codeExplain the denial codes on an Explanation of Benefits.Reads text others write1 finding
Why it is in this group
- The name "explain_denial_code" says "explain": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "explain_denial_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "explain_denial_code" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Explain the denial codes on an Explanation of Benefits
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
get_appeal_deadlinesHow long someone has to appeal, and how fast the plan must decide.Reads text others writeNo findings
Why it is in this group
- The name "get_appeal_deadlines" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: How long someone has to appeal, and how fast the plan must decide
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_appeal_rightsAppeal rights, steps and free help for a plan type and state.Reads text others writeNo findings
Why it is in this group
- The name "get_appeal_rights" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Appeal rights, steps and free help for a plan type and state
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://goodturn-mcp.pages.dev/.well-known/oauth-protected-resource/appealmyclaim/mcp
- Authorization servers
- https://jobspotter.pages.dev
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://goodturn-mcp.pages.dev/appealmyclaim/mcp: tools/list returned 4 tools to an anonymous client, including explain_denial_code (write), draft_appeal_letter (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "explain_denial_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "explain_denial_code" says "explain": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http appealmyclaim https://goodturn-mcp.pages.dev/appealmyclaim/mcpclaude mcp add --transport http appealmyclaim https://goodturn-mcp.pages.dev/appealmyclaim/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__appealmyclaim__get_appeal_rights",
"mcp__appealmyclaim__get_appeal_deadlines"
],
"ask": [
"mcp__appealmyclaim__explain_denial_code",
"mcp__appealmyclaim__draft_appeal_letter"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as appealmyclaim. Review it before you use it.
Capability tags behind 4 rules
- mcp__appealmyclaim__get_appeal_rights untrusted-input
- mcp__appealmyclaim__get_appeal_deadlines untrusted-input
- mcp__appealmyclaim__explain_denial_code untrusted-input
- mcp__appealmyclaim__draft_appeal_letter untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.GoodTurnStudio/appealmyclaim/verify?hash=408c3e1f1d14f2d535fde6ade5a40ea6a1032f4f10050873b70d6436c7d698b0" | jq -e '.changed == false'Pinned hash 408c3e1f1d14, from Nov 15, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.GoodTurnStudio/appealmyclaim/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.GoodTurnStudio/appealmyclaim)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:16 UTC.
Appeal My Claim MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Appeal My Claim MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Appeal My Claim MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Appeal My Claim MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Appeal My Claim MCP server have?
- 4 tools: 2 write, 2 read. explain_denial_code, draft_appeal_letter, get_appeal_rights and get_appeal_deadlines.
Does the Appeal My Claim MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Appeal My Claim MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Appeal My Claim MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.