---
name: settlements-jobs
description: "Step-by-step job recipes for the Settlement Claim Finder MCP server: Find open class action settlements you may claim; Check whether a settlement link is the official site. Use when the user asks things like \"I live in Texas and bought an iPhone 16 last year. Is there a settlement I can claim?\" or \"I got a text about the Apple Siri settlement at smartphoneaisettlement.com. Is that real?\""
license: MIT
---

# Settlement Claim Finder jobs

Each section below walks through one job with the tools of the `settlements` MCP server. The same recipes are MCP prompts (prompts/list) on `https://settlements.openkrill.app/mcp`.
Connect the server at `https://settlements.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Find open class action settlements you may claim

Job: Find open class action settlements you may claim, with the Settlement Claim Finder MCP server.

Use the `find_settlements` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "I live in Texas and bought an iPhone 16 last year. Is there a settlement I can claim?"

Steps:
1. Call `find_settlements` as a normal MCP tool call, with the request's values in the fields of its inputSchema.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"where":"Texas","bought_or_used":"iPhone 16"}`
4. For the request "I live in Texas and bought an iPhone 16 last year. Is there a settlement I can claim?", a correct answer looks like this: The Apple Smartphone AI settlement with its deadline and official claim link.
5. Follow the server's own rules:
   - Use find_settlements with where and the brands, products or services the person named; leave bought_or_used out when they want the full list.
   - Show name, who, payout, deadline with days_left and claim_url exactly as returned, then not_legal_advice and safety.
   - Say that only the official notice decides who qualifies, and when needs_notice is true say the person can file only if they got a notice.
   - Never file a claim, never invent a settlement, a payout or a deadline, and never suggest a paid claim service.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `find_settlements`).

## Check whether a settlement link is the official site

Job: Check whether a settlement link is the official site, with the Settlement Claim Finder MCP server.

Use the `check_settlement_site` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "I got a text about the Apple Siri settlement at smartphoneaisettlement.com. Is that real?"

Steps:
1. Call `check_settlement_site` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `url`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"url":"smartphoneaisettlement.com"}`
4. For the request "I got a text about the Apple Siri settlement at smartphoneaisettlement.com. Is that real?", a correct answer looks like this: listed true with the Apple settlement and the advice to type the address.
5. Follow the server's own rules:
   - Show name, who, payout, deadline with days_left and claim_url exactly as returned, then not_legal_advice and safety.
   - Say that only the official notice decides who qualifies, and when needs_notice is true say the person can file only if they got a notice.
   - Use check_settlement_site for a link from a message.
   - Never file a claim, never invent a settlement, a payout or a deadline, and never suggest a paid claim service.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `check_settlement_site`).