Untap

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Check UK Delay Repay, UK261 flights and TfL refunds. Save claims and check commutes on request.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Untap": {
      "url": "https://untap.money/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (20)

• find_money_owed read-only

  Takes a plain-language description of what happened (a late or cancelled train, a delayed or cancelled flight, a TfL overcharge, a parking ticket, a council tax, water or broadband problem) and returns the UK refund and compensation schemes Untap covers that may apply. For each one it gives the fact that decides it, the Untap check that covers it and Untap’s free guide. It also picks out any flight number, date, time or amount in the text. Matching is by keywords, not a full reading of the situation, so the list is a starting point rather than a verdict. No sign-in needed. Nothing is saved to an account. A record of the check, with no name, account or IP address, is kept for a year so answers can be verified.

  Parameters:

  • situation (required) — string — What happened, in the person’s own words. For example: "my train from Brighton to Victoria was 40 minutes late on Monday" or "I think my council tax band is wrong".

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_train_delay read-only

  Checks a late or cancelled train in Great Britain against National Rail’s historic running records and works out Delay Repay. Takes the two stations (names, partial names or three-letter codes), the date and roughly when the train left; the operator, ticket type and price paid are optional. Returns the matched train with scheduled and actual times, the delay at the destination, the operator and its scheme, the amount (or the percentage when no price is given), the claim deadline, a claim pack with the value for each form field, and the details needed to save the claim to an Untap account. When several trains fit, the result lists them, each with a service_id. The records cover roughly the last year and each day appears the day after. They hold direct trains only, so a journey with a change is checked one train at a time. When nothing could be learned, status is data_not_available with delay_known false, a reason, retryable and retry_after_seconds or try_again_on. When National Rail is slow the lookup carries on in the background, and a retry after retry_after_seconds is answered from the cache. No sign-in needed. Nothing is saved to an account. A record of the check, with no name, account or IP address, is kept for a year so answers can be verified.

  Parameters:

  • from (required) — string — Station the person got on at. A name, part of a name or a three-letter code: "Brighton", "Kings Cross", "BTN".
  • to (required) — string — Station the person got off at, in the same forms.
  • date (required) — string — Date of travel. YYYY-MM-DD is best; "25/09/2026", "25 September", "yesterday" and "last Friday" also work.
  • tickets — How many tickets of this price are on the booking, one per passenger. Defaults to 1. The amount is per ticket times this.
  • operator — Train company if known, as the person says it: "Southern", "GWR", "Avanti". Used to narrow the match.
  • price_paid — What one ticket cost, in pounds: "£24.50", 24.5 or 17 (read as £17.00). For a season ticket, the price of the whole season. Needed for a cash amount; without it the percentage is returned.
  • service_id — The service_id of a train listed in an earlier result. With it, that train is checked directly.
  • ticket_type — As printed: "Anytime Return", "Off-Peak Single", "Advance", "Annual Season", "Monthly Season", "Flexi Season". A return halves the single fare the amount is worked from. A season is valued per journey from its length; a season with no length gets no amount.
  • departure_time — Roughly when the train left the first station, UK time: "08:05", "8am", "around 8". Needed to find the train unless service_id is given.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_flight_compensation read-only

  Works out compensation for a delayed or cancelled flight under UK261 or EU261. Takes the flight number and date. What happened comes from flight-status records, which cover about the last year, or from what_happened and arrival_delay_minutes when given. Returns the matched route, the arrival delay, the distance band, the amount per passenger, the extraordinary-circumstances caveat, the airline’s claim page, the dispute body for a refused claim, deadline guidance, a claim pack and the details needed to save the claim to an Untap account. When the airports given differ from the flight-status record, the result says so. No sign-in needed. Nothing is saved to an account. A record of the check, with no name, account or IP address, is kept for a year so answers can be verified.

  Parameters:

  • flight_number (required) — string — Airline code and number, as on the booking: "BA2551", "U2 8123".
  • date (required) — string — Date the flight was due to depart, local time. YYYY-MM-DD is best.
  • price_paid — Optional, in pounds: "£180" or 180. Not used for the amount, which is fixed in law, but needed to save the claim to an account.
  • to_airport — Three-letter arrival airport code, if known: "BCN".
  • from_airport — Three-letter departure airport code, if known: "LGW". Helps pick the right flight on multi-stop numbers.
  • what_happened — What happened, if known. When left out, Untap looks it up in flight-status records.
  • arrival_delay_minutes — How late the flight arrived at the gate, in minutes, if the person knows. Compensation turns on arrival, not departure.
  • cancellation_notice_days — For a cancellation: how many days before departure the airline told the person. 14 or more means no compensation.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_tfl_journeys read-only

  Checks Transport for London contactless or Oyster journeys for overcharges: incomplete journeys (no touch out, so the maximum fare was charged) and missed Hopper fares. Takes journey rows from a journey history, or the text of the CSV download from a TfL account. PDFs and images are not accepted. TfL refunds an incomplete journey as the maximum fare minus the fare for the journey actually made. Without the destination, the refund shown is an upper limit equal to the whole charge; with intended_destination on the row, it is an estimate from the usual fare to that station. Returns the refundable journeys and total, older journeys outside TfL’s 8 week window, how to claim in the TfL account, a claim pack and the details needed to save the journeys to an Untap account. It does not check service delays on the Tube, DLR, Elizabeth line or Overground, or Santander Cycles; the result lists these under not_checked. No sign-in needed. Nothing is saved to an account. A record of the check, with no name, account or IP address, is kept for a year so answers can be verified.

  Parameters:

  • csv_text — The text of the CSV journey history downloaded from a TfL account. Takes priority over journeys.
  • journeys — Journey rows from a TfL contactless or Oyster journey history. Used when csv_text is not given.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_delay_repay_rules read-only

  Returns one train operator’s Delay Repay rules: the delay at which it starts paying, each payout tier, the claim deadline, the link to its claim form, any automatic or one-click scheme, and the date the rules were last checked against the operator’s own page. Accepts the operator’s name as people say it, such as Avanti, GWR or Southern. No sign-in needed.

  Parameters:

  • operator (required) — string — Train company name as people say it: "Avanti", "GWR", "Southern", "LNER", or a two-letter operator code.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_claim_instructions read-only

  Returns how to submit one train, flight or TfL compensation claim on the company’s own form. Takes the claim type and the train operator or airline, with the journey date, ticket type, where it was booked and the airports as optional extras. Returns the eligibility rules for that company and claim type, the official claim page (marked unverified where Untap could not confirm it), numbered submission steps, each form field with where to find its value, the evidence to attach, the deadline (as a date when the journey date is given), any company rule on who may submit, what to expect after submitting and when to chase, the escalation route (operator to the Rail Ombudsman; airline to its dispute scheme, the CAA or a national enforcement body; TfL to London TravelWatch) and the sources with the dates they were checked. Covers every train operator in Untap’s Delay Repay engine, TfL and the airlines UK travellers fly most. Facts Untap has not verified come back marked as unknown rather than estimated. No sign-in needed. Nothing is saved to an account. A record of the check, with no name, account or IP address, is kept for a year so answers can be verified.

  Parameters:

  • claim_type (required) — string — What the claim is for: a late or cancelled train, a delayed or cancelled flight, denied boarding, a TfL incomplete journey or another TfL overcharge.
  • company — The train operator or airline, by name or code as people say it: "Southern", "LNER", "easyJet", "BA", "U2". Not needed for TfL.
  • booked_via — Where the ticket was bought: from the operator or airline itself, from a ticket retailer such as Trainline, through a travel agent, or as part of a package holiday.
  • ticket_type — Ticket type as printed, such as "Anytime Return", "Advance Single" or "Season". Decides the rail return-ticket rule.
  • journey_date — Date of travel, YYYY-MM-DD. With it, the result gives the last day to claim as a date.
  • arrival_airport — Three-letter arrival airport code, such as "LHR".
  • departure_airport — Three-letter departure airport code, such as "CDG". Decides whether UK261 or EU261 applies, and with the arrival airport, the distance band.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• scan_for_claims read-only

  Reads up to 25 emails (sender, subject, date and plain-text body) and picks out the ones that point to a train, flight or TfL claim: booking confirmations, delay and cancellation notices, airline schedule changes and denied boarding, TfL incomplete journey and maximum fare emails, and claim acknowledgements and decisions. Detection is by sender domain, subject pattern and fixed phrases, with no language model. For each match it returns the type, the signals that matched, the booking reference, dates, flight number, stations or airports, times and amounts it could read, a confidence level, a deadline hint, and the Untap check that fits with its arguments filled in and any missing ones listed. Emails with no signal are listed by position. Each body is read up to 20,000 characters. Nothing from the emails is stored; the usage record holds counts only. No sign-in needed.

  Parameters:

  • emails (required) — array — Up to 25 emails, each with its sender, subject, date and plain-text body.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• save_claim

  Saves the result of a train, flight or TfL check to the person’s Untap account, so it appears on their dashboard with its deadline. Accepts the save_claim arguments returned by a check, with the price paid added where the check listed it as missing. The verdict is worked out again from those facts rather than copied. A train journey that is already saved is returned as it is, not saved twice. Requires sign-in to Untap.

  Parameters:

  • category (required) — string — Which kind of check the claim came from.
  • tfl — For category "tfl": the journeys, in the shape a TfL check returns in save_claim.arguments.tfl.
  • train — For category "train": the train booking, in the shape a train check returns in save_claim.arguments.train, with ticket_price_pence set.
  • flight — For category "flight": the flight, in the shape a flight check returns in save_claim.arguments.flight, with ticket_price_pence set.

  Hints: read-only no · destructive no · idempotent no · open-world no

• save_commute

  Saves or updates one direction of a usual train journey (a commute) in the person’s Untap account: stations, usual departure time, travel days and day-ticket fare. An outward and a homeward journey are two separate routes. Saving the same route and time again updates it. Nothing is checked automatically; a saved route is checked only on request. Day tickets only; season tickets are not supported. Requires sign-in to Untap.

  Parameters:

  • from (required) — string — Departure station name or three-letter code.
  • to (required) — string — Arrival station name or three-letter code.
  • departure_time (required) — string — Usual UK departure time, for example 08:05 or 8am.
  • label — Optional short name such as Morning commute.
  • weekdays — array — Usual travel days: Monday=1 through Sunday=7. Informational only; no automatic checks.
  • commute_id — The id of an existing commute in this account, to update or restore it. When left out, a new route is saved.
  • ticket_type — string — Day ticket type. For return, the price is the whole return fare. Season tickets are not supported by saved commutes.
  • ticket_price_pence — Usual day-ticket price in pence, £24.50=2450. Optional, for when the fare is known and stays the same. A day-ticket price, not a weekly or monthly season price.

  Hints: read-only no · destructive no · idempotent yes · open-world no

• list_commutes read-only

  Lists the person’s saved train routes with their ids, usual times, days and fares. Makes no National Rail lookups. Requires sign-in to Untap.

  Parameters:

  • include_stopped — boolean — Include stopped routes so they can be restored.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• stop_commute

  Hides a saved train route from the active list. The route is kept and can be restored by saving it again with its commute_id. No claims or bookings change. Requires sign-in to Untap.

  Parameters:

  • commute_id (required) — string — The id of a saved commute. The route is kept and can be restored.

  Hints: read-only no · destructive no · idempotent yes · open-world no

• check_commute read-only

  Checks a saved train route against National Rail’s running records for one travel date and works out Delay Repay: the matched train, the delay, the amount, the deadline and a claim pack. When several trains match, the result lists them, each with a service_id. A saved route does not show that the person travelled that day, and the result says so. Nothing is saved or filed. Requires sign-in to Untap.

  Parameters:

  • commute_id (required) — string — The id of a saved commute.
  • date (required) — string — The travel date to check, preferably YYYY-MM-DD. "yesterday" also works.
  • service_id — The service_id of a train listed in an earlier result. With it, that train is checked directly.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• list_my_claims read-only

  Lists the claims in the person’s Untap account with amounts, deadlines, the verdict and their progress (not sent, sent, paid, rejected or archived). By default it shows claims that are still open; include_closed adds paid, rejected and archived ones. Requires sign-in to Untap.

  Parameters:

  • limit — integer — Most rows to return. Defaults to 25.
  • category — Restricts the list to one category. When left out, all categories are listed.
  • include_closed — boolean — Also show claims marked paid, rejected or archived, and ones with nothing to claim.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• update_claim_status

  Records progress on a claim in the person’s Untap account: sent (submitted to the operator or airline), paid (with the amount received, if known), rejected, or archived. Takes the claim_id given when the claim was saved or listed. This updates Untap’s record only; it does not contact the operator or airline. Requires sign-in to Untap.

  Parameters:

  • claim_id (required) — string — The claim_id given when the claim was saved or listed.
  • status (required) — string — sent: submitted to the operator or airline. paid: money received. rejected: the claim was refused. archived: hide it without an outcome.
  • note — Optional short note, such as the operator’s reference or the reason given for a refusal.
  • amount_received_pence — For paid: the amount actually received, in pence. £12.40 = 1240.

  Hints: read-only no · destructive no · idempotent yes · open-world no

• add_train_journey

  Adds a UK train booking to the person’s Untap account and works out Delay Repay for it. One booking per call, with each journey in legs (one for a single, two for a return, in travel order). Untap checks National Rail’s Historical Service Performance records for each journey; the delay, actual arrival and cancellation fields are optional, and when left out Untap looks them up. Operators accept one journey per claim form, so a return with both directions late means two claims. A train journey that is already saved is returned as it is, not saved twice. Requires sign-in to Untap.

  Parameters:

  • ticket_price_pence (required) — integer — Total fare paid in pence for the whole booking. £62.00 = 6200.
  • ticket_type (required) — string — Ticket type as printed. For "return" and "open_return" the single fare is half the price paid; for "season" the amount is a share of one journey value (see season_type); every other type uses the full price as the single fare.
  • booking_reference (required) — ['string', 'null'] — Booking reference if available, otherwise null.
  • legs (required) — array — Each journey on this booking, in travel order: one for a single, two for a return (outward first), more for a multi-stop booking. Untap works out Delay Repay for each journey and adds them up.
  • season_type — Season tickets only: how long the season runs. The operator divides the season price into single journeys (for example annual 464, monthly 40, weekly 10, flexi 16) and pays a share of one journey. When left out, the result gives the percentage and the method but no amount.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• add_flight

  Adds a flight to the person’s Untap account and returns the UK261 or EU261 verdict, the amount and the airline’s claim link. For past flights Untap checks AeroDataBox flight-status records; the status, delay and actual arrival fields are optional, and when left out Untap looks them up. Takes the airline’s two-letter IATA code (BA, U2, FR) and three-letter airport codes (LHR, BCN). When the airports given differ from the flight-status record, the result says so. Compensation applies to arrival delays of 3 hours or more and to cancellations. Requires sign-in to Untap.

  Parameters:

  • airline_iata (required) — string — Two-letter IATA airline code, e.g. "BA" for British Airways, "U2" for easyJet.
  • flight_number (required) — string — Flight number including the airline prefix, e.g. "BA2551".
  • departure_iata (required) — string — Three-letter IATA departure airport code, e.g. "LHR".
  • arrival_iata (required) — string — Three-letter IATA arrival airport code, e.g. "BCN".
  • scheduled_departure (required) — string — Scheduled departure as ISO 8601 datetime.
  • scheduled_arrival (required) — string — Scheduled arrival as ISO 8601 datetime.
  • ticket_price_pence (required) — integer — Total fare paid in pence.
  • booking_reference (required) — ['string', 'null'] — PNR / airline booking reference if available, otherwise null.
  • passenger_name (required) — ['string', 'null'] — Passenger name as printed on the ticket, or null if not visible.
  • status — Optional. What happened to the flight, if known. When left out, Untap looks the flight up in AeroDataBox flight-status records.
  • delay_minutes — Optional. Arrival delay in minutes, if known.
  • actual_arrival — ['string', 'null'] — Optional. Actual arrival as an ISO 8601 datetime, if known.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• add_tfl_journeys

  Adds TfL contactless journeys to the person’s Untap account, up to 500 rows per call, and checks everything they have saved for incomplete journeys, missed Hopper fares and other overcharges. Each row carries flags for an incomplete journey, a revenue-inspection maximum fare, a free Hopper fare, a TfL correction and the daily or weekly cap, as shown on the statement. Journeys already saved are skipped. Refunds follow the same rule as the TfL check: an incomplete journey without a destination is an upper limit equal to the whole charge, and one with intended_destination is an estimate. Requires sign-in to Untap.

  Parameters:

  • card_last4 (required) — ['string', 'null'] — Last 4 digits of the contactless card, if shown.
  • period_start (required) — ['string', 'null'] — Statement period start date YYYY-MM-DD.
  • period_end (required) — ['string', 'null'] — Statement period end date YYYY-MM-DD.
  • journeys (required) — array — Every journey on the statement. Up to 500 per call.

  Hints: read-only no · destructive no · idempotent yes · open-world no

• add_parking_fine

  Adds a UK parking ticket (a council PCN or a private parking charge) to the person’s Untap account and runs Untap’s appeal-grounds engine. Returns the grounds that may apply, how confident the match is, the appeal route and deadline. Grounds are matched against the contravention, the location and observed_notes; with no observed_notes, only general grounds come back and the result is a possible appeal, not money owed. Requires sign-in to Untap.

  Parameters:

  • pcn_reference (required) — string — PCN or notice reference number printed on the document.
  • issuer_type (required) — string — Council = local authority issued under TMA 2004. Private = on private land by a parking operator (BPA or IPC member).
  • issuer_name (required) — string — Issuer name as written, e.g. "London Borough of Camden" or "ParkingEye Ltd".
  • contravention_code (required) — ['string', 'null'] — Council contravention code, e.g. "01", "12", "MR11". Null for private tickets.
  • contravention_description (required) — string — Full text of the alleged contravention as printed on the notice.
  • vehicle_registration (required) — ['string', 'null'] — Vehicle registration mark, or null if not shown.
  • location (required) — string — Street or car park name where the contravention allegedly occurred.
  • contravention_date (required) — string — Date the contravention allegedly occurred, ISO 8601 date.
  • issued_date (required) — string — Date the notice was issued or served, ISO 8601 date.
  • amount_pence (required) — integer — Full charge amount in pence. £65 = 6500.
  • discounted_amount_pence (required) — Reduced amount in pence if paid promptly (usually 50% within 14 or 21 days). Null if none stated.
  • discount_deadline (required) — ['string', 'null'] — ISO date by which the discount applies, or null if not stated.
  • full_deadline (required) — ['string', 'null'] — Last date on the notice for paying the full amount or lodging an appeal, as an ISO date.
  • appeal_url (required) — Direct https URL on the notice for online appeals, or null if none.
  • has_windscreen_notice (required) — boolean — True if a paper notice was placed on the windscreen. False if it arrived in the post only.
  • keeper_notice_served_date (required) — ['string', 'null'] — Private only: date the Notice to Keeper was served.
  • observed_notes (required) — array — Short phrases from the notice or the person’s account that may support an appeal, such as unclear signs, a broken machine or a few minutes over. The appeal-grounds engine matches against these; with none, it can only suggest general grounds.

  Hints: read-only no · destructive no · idempotent no · open-world no

• list_savings read-only

  Lists the savings rows in the person’s Untap account, filtered by category and status. Each row has the verdict status (claimable, pending_check, not_eligible and so on) and user_progress, what the person has recorded since: none, submitted (sent), received (paid) or archived. Requires sign-in to Untap.

  Parameters:

  • category (required) — Restrict to a single category, or null for all categories.
  • status (required) — Restrict to a single status, or null for all.
  • limit — integer — Maximum number of savings rows to return. Defaults to 25, capped at 100.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• delete_my_data destructive

  Deletes every booking, statement, saved commute and claim in the person’s Untap account, in two steps. A call with confirm=false deletes nothing and returns a summary of what would be deleted, with a confirmation_token valid for 5 minutes. A call with confirm=true and that token deletes the data permanently; each token works once. The account itself is kept so Untap can still be used; deleting the account too is done at untap.money/data. Requires sign-in to Untap.

  Parameters:

  • confirm — boolean — false returns a preview of what would be deleted and a confirmation_token, and deletes nothing. true deletes, and works only with an unexpired confirmation_token from a preview.
  • confirmation_token — ['string', 'null'] — The confirmation_token from a preview. Required when confirm is true; each token works once.

  Hints: read-only no · destructive yes · idempotent no · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.