Claim Back
REMOTE · CLAIMBACK.LAPLA.SI
Medicare Advantage denial appeals (US): sourced guides, appeal deadlines, and help appealing.
Available components
Last scanned (20 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 967 tokens (~241/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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 0
- Tool “appeal_deadline” rewrote its description, which is the text the model reads security
- Tool “list_guides” rewrote its description, which is the text the model reads security
- Schema quality: 218 → 241 ▼ functional
- “appeal_deadline” added an optional parameter “notice_delivered_date” cosmetic
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “claim_back_services” rewrote its description, which is the text the model reads security
- Tool “list_guides” rewrote its description, which is the text the model reads security
- Tool “read_guide” rewrote its description, which is the text the model reads security
- Schema quality: 187 → 215 ▼ functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://claimback.lapla.si/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lapla.si | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 86c4cd4ca98f396f132e197e60c16b55 |
| SANs: lapla.si, claimback.lapla.si, *.claimback.lapla.si | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of claimback.lapla.si. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| si. | present | 42378 | 13 | Verified |
| lapla.si. | absent | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://claimback.lapla.si/mcp | Verified | 200 | |
| http (plaintext) | http://claimback.lapla.si/mcp | Inconclusive | 405 |
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 →
appeal_deadline Work out an appeal deadline ~233
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.
| Name | Type | Req | Description |
|---|---|---|---|
| care_end_date | string | – | The date covered care ends, from the Notice of Medicare Non-Coverage, YYYY-MM-DD. |
| notice_date | string | – | The date printed on the denial notice, YYYY-MM-DD. |
| notice_delivered_date | string | – | The day the Notice of Medicare Non-Coverage was delivered, YYYY-MM-DD (with care_end_date). |
No output schema declared.
No examples provided.
claim_back_services Claim Back’s services and prices ~103
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_guides List the appeal guides ~120
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_guide Read an appeal guide ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The guide’s slug, from list_guides. |
No output schema declared.
No examples provided.
How do I install the Claim Back MCP server?
Claim Back is a hosted endpoint at https://claimback.lapla.si/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 · claimback.lapla.si
claude mcp add --transport http keith-cy-claimback 'https://claimback.lapla.si/mcp'
What is the Claim Back MCP server?
Claim Back is an MCP server listed in the public MCP registry as io.github.Keith-CY/claimback. Medicare Advantage denial appeals (US): sourced guides, appeal deadlines, and help appealing. This page covers its hosted endpoint (https://claimback.lapla.si/mcp).
Is the Claim Back MCP server safe to use?
Claim Back scores 72 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 Claim Back MCP server expose?
Claim Back exposes 4 tools: list_guides, read_guide, appeal_deadline, claim_back_services. Their descriptions and schemas cost roughly 535 tokens of context every time the server is loaded.
Does the Claim Back MCP server require authentication?
No. We connected to Claim Back without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Claim Back MCP server still maintained?
Claim Back is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.