Skip to content

Claim Back MCP server

io.github.Keith-CY/claimbackKeith-CYstreamable-httpv1.0.0Scanned

Medicare Advantage denial appeals (US): sourced guides, appeal deadlines, and help appealing.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

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.
Govern this server →

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 Claim Back MCP server can do

The Claim Back MCP server is published by the GitHub account Keith-CY. It has 4 tools. It can create or change data (2 tools: appeal_deadline and claim_back_services), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.0.0.

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
  • appeal_deadlineCalendar arithmetic for Medicare Advantage appeal deadlines.No 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.
    Description, as the server wrote it
    Calendar arithmetic for Medicare Advantage appeal deadlines. Give notice_date (the date printed on the plan’s denial notice) for the plan reconsideration deadline: 65 days from that date (the rule is 60 days from receipt, presumed 5 days after the date). Or give care_end_date (the date covered skilled nursing, home health or outpatient rehab care ends, on the Notice of Medicare Non-Coverage), and notice_delivered_date (the day that notice was handed over) if known, for the fast appeal: by noon of the day after delivery; without the delivery date, noon the day before the end date, which holds only for a notice that came two days ahead. The notice’s own instructions come first.

    Annotations the server declares

    • title: Work out an appeal deadline
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • claim_back_servicesHow Claim Back helps with a Medicare Advantage appeal, and what it costs: a free check of the denial letter, then two fixed-price services (we handle it for you, paid only if the d…No 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.
    Description, as the server wrote it
    How Claim Back helps with a Medicare Advantage appeal, and what it costs: a free check of the denial letter, then two fixed-price services (we handle it for you, paid only if the decision is reversed; or we prepare it and you send it). It also says what Claim Back offers for a long-term care insurance claim denial. Returns the link where the user uploads their letter. Use it when the user wants help with an appeal or asks about Claim Back.

    Annotations the server declares

    • title: Claim Back’s services and prices
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • list_guidesLists Claim Back’s guides (US), each with its slug, title, one-line summary and link.No findings

    Why it is in this group

    • The name "list_guides" says "list": a word for reading.
    Description, as the server wrote it
    Lists Claim Back’s guides (US), each with its slug, title, one-line summary and link. Medicare Advantage: how to appeal and who can ask, the appeal deadline, a prior authorization denial, the fast appeal when care is ending, care ended or denied because the patient stopped improving (the maintenance standard), and the independent review. Long-term care insurance: what to do after a denial, and the independent review of benefit-trigger denials state by state. Use it to find the guide that answers the user’s question, then read_guide.

    Annotations the server declares

    • title: List the appeal guides
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_guideReturns one guide in full as Markdown, with its sources (federal and state regulations, Medicare.gov, CMS and state insurance departments).No findings

    Why it is in this group

    • The name "read_guide" says "read": a word for reading.
    Description, as the server wrote it
    Returns one guide in full as Markdown, with its sources (federal and state regulations, Medicare.gov, CMS and state insurance departments). Use it to answer questions about Medicare Advantage appeals and long-term care insurance claim denials accurately, and link the guide in the answer.

    Annotations the server declares

    • title: Read an appeal guide
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

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
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • 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.

    Matched text

    https://claimback.lapla.si/mcp: tools/list returned 4 tools to an anonymous client, including appeal_deadline (write), claim_back_services (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http claimback https://claimback.lapla.si/mcp
claude mcp add --transport http claimback https://claimback.lapla.si/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__claimback__list_guides",
      "mcp__claimback__read_guide"
    ],
    "ask": [
      "mcp__claimback__appeal_deadline",
      "mcp__claimback__claim_back_services"
    ],
    "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 claimback. Review it before you use it.

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.Keith-CY/claimback/verify?hash=f826021bf52255bac8e5db59f97cbace48fc5839ec1fe0abc3750a13680308fd" | jq -e '.changed == false'

Pinned hash f826021bf522, from Nov 16, 2026, 18: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.Keith-CY/claimback/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Keith-CY/claimback
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Keith-CY/claimback.svg)](https://radar.anlyon.com/servers/io.github.Keith-CY/claimback)

Source: MCP Registry. Synced Oct 21, 2026, 18:17 UTC.

Claim Back MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Claim Back MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Claim Back MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Claim Back 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 Claim Back MCP server have?

4 tools: 2 write, 2 read. appeal_deadline, claim_back_services, list_guides and read_guide.

Does the Claim Back MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Claim Back MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Claim Back MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.