Untap

npx add-mcp 'https://untap.money/api/mcp'

Untap assistant tools

Untap checks UK refunds and compensation, then gives you the amount, the deadline and the organisation’s claim link. You submit the claim yourself. Untap takes no cut.

Connect

Add https://untap.money/api/mcp as a remote MCP server using Streamable HTTP. In Claude, add a custom connector. In ChatGPT, use a custom connector where your account supports it. Setup instructions.

The seven public tools work without an account. Saving claims or commutes, reading your account and updating progress require OAuth sign-in through Untap. Your assistant never needs your password or a copied API key.

Agents that do not use MCP can call the same public tools as JSON over HTTPS: POST https://untap.money/api/agent/v1/{tool}, with the input in the body. The OpenAPI 3.1 description lists every endpoint and schema. Inputs, results and limits match the MCP tools.

From a check to a claim

1. Describe the journey and travel date. The assistant asks for missing details and chooses the relevant check.
2. Confirm the actual train or flight if several match. The result gives the amount or percentage, deadline, assumptions and claim link.
3. If you want to track it, ask to save the checked claim. Sign in through Untap and provide any missing fare or booking details.
4. Submit on the operator or airline’s site. Tell your assistant when you have sent it or been paid to update your Untap record.

Checking eligibility alone does not save a booking or claim. Saved commutes need a specific date you request and confirmation that you took the journey. Untap does not book tickets, show live departure boards, pay charges or handle baggage claims.

What gets saved

Public checks do not save your booking, journey rows, documents or result to an account. They keep usage records containing the tool name, outcome and duration. Rate limits use a salted IP digest rather than your raw address. Train and flight lookups send the journey details needed to National Rail or our flight-data provider.

Account tools save only what you ask them to: claims, booking details, TfL journeys, progress and recurring routes. These records remain until you delete them. Saved commutes are checked only when asked, without scheduled checks or automatic claim filing.

Disconnect an assistant to revoke its access. Disconnecting does not delete claims. Use Your Data or the two-step delete_my_data tool to delete your saved data. See the privacy policy.

Limits and errors

Public lookup tools allow 40 calls per caller per hour; lighter checks allow 240. Cached results reduce repeat lookups. Across the service, daily upstream caps are 600 rail lookups and 150 flight lookups. A shared assistant address may share a caller limit.

Inputs that need clarification return candidates or the missing fields. A missing flight record asks for what happened rather than assuming it was on time. A limit or unavailable provider returns a retry message. Claim amounts rely on the supplied facts and each scheme’s rules; a claim pack is not a submitted claim.

Available tools

Save a usual train journey

Sign-in required

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.

Limit: 30 calls per hour.

commute_id (optional)

The id of an existing commute in this account, to update or restore it. When left out, a new route is saved.

label (optional)

Optional short name such as Morning commute.

from (required)

Departure station name or three-letter code.

to (required)

Arrival station name or three-letter code.

departure_time (required)

Usual UK departure time, for example 08:05 or 8am.

weekdays (optional)

Usual travel days: Monday=1 through Sunday=7. Informational only; no automatic checks.

ticket_type (optional)

Day ticket type. For return, the price is the whole return fare. Season tickets are not supported by saved commutes.

ticket_price_pence (optional)

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.

List saved commutes

Sign-in required

list_commutes

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.

Limit: 60 calls per hour.

include_stopped (optional)

Include stopped routes so they can be restored.

Check a saved commute for a travel date

Sign-in required

check_commute

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.

Limit: 20 calls per hour.

commute_id (required)

The id of a saved commute.

date (required)

The travel date to check, preferably YYYY-MM-DD. "yesterday" also works.

service_id (optional)

The service_id of a train listed in an earlier result. With it, that train is checked directly.

Stop a saved commute

Sign-in required

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.

Limit: 30 calls per hour.

commute_id (required)

The id of a saved commute. The route is kept and can be restored.

Find money you may be owed

No sign-in

find_money_owed

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. Journey details are not saved to an account; limited usage metadata is recorded.

Limit: 240 calls per hour.

situation (required)

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

Check a delayed train for Delay Repay

No sign-in

check_train_delay

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. No sign-in needed. Journey details are not saved to an account; limited usage metadata is recorded.

Limit: 40 calls per hour.

from (required)

Station the person got on at. A name, part of a name or a three-letter code: "Brighton", "Kings Cross", "BTN".

to (required)

Station the person got off at, in the same forms.

date (required)

Date of travel. YYYY-MM-DD is best; "25/09/2026", "25 September", "yesterday" and "last Friday" also work.

departure_time (optional)

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.

operator (optional)

Train company if known, as the person says it: "Southern", "GWR", "Avanti". Used to narrow the match.

ticket_type (optional)

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.

price_paid (optional)

What the ticket cost: "£24.50", 24.50 or 2450 (pence). For a season ticket, the price of the whole season. Needed for a cash amount; without it the percentage is returned.

service_id (optional)

The service_id of a train listed in an earlier result. With it, that train is checked directly.

Check a flight for UK261 or EU261 compensation

No sign-in

check_flight_compensation

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. Journey details are not saved to an account; limited usage metadata is recorded.

Limit: 40 calls per hour.

flight_number (required)

Airline code and number, as on the booking: "BA2551", "U2 8123".

date (required)

Date the flight was due to depart, local time. YYYY-MM-DD is best.

from_airport (optional)

Three-letter departure airport code, if known: "LGW". Helps pick the right flight on multi-stop numbers.

to_airport (optional)

Three-letter arrival airport code, if known: "BCN".

what_happened (optional)

What happened, if known. When left out, Untap looks it up in flight-status records.

arrival_delay_minutes (optional)

How late the flight arrived at the gate, in minutes, if the person knows. Compensation turns on arrival, not departure.

cancellation_notice_days (optional)

For a cancellation: how many days before departure the airline told the person. 14 or more means no compensation.

price_paid (optional)

Optional. Not used for the amount, which is fixed in law, but needed to save the claim to an account.

Check TfL journeys for overcharges

No sign-in

check_tfl_journeys

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. No sign-in needed. Journey details are not saved to an account; limited usage metadata is recorded.

Limit: 240 calls per hour.

journeys (optional)

Journey rows from a TfL contactless or Oyster journey history. Used when csv_text is not given.

csv_text (optional)

The text of the CSV journey history downloaded from a TfL account. Takes priority over journeys.

Delay Repay rules for a train operator

No sign-in

get_delay_repay_rules

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.

Limit: 240 calls per hour.

operator (required)

Train company name as people say it: "Avanti", "GWR", "Southern", "LNER", or a two-letter operator code.

How to submit a train, flight or TfL claim

No sign-in

get_claim_instructions

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. Journey details are not saved to an account; limited usage metadata is recorded.

Limit: 240 calls per hour.

claim_type (required)

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 (optional)

The train operator or airline, by name or code as people say it: "Southern", "LNER", "easyJet", "BA", "U2". Not needed for TfL.

journey_date (optional)

Date of travel, YYYY-MM-DD. With it, the result gives the last day to claim as a date.

ticket_type (optional)

Ticket type as printed, such as "Anytime Return", "Advance Single" or "Season". Decides the rail return-ticket rule.

booked_via (optional)

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.

departure_airport (optional)

Three-letter departure airport code, such as "CDG". Decides whether UK261 or EU261 applies, and with the arrival airport, the distance band.

arrival_airport (optional)

Three-letter arrival airport code, such as "LHR".

Scan emails for train, flight and TfL claims

No sign-in

scan_for_claims

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.

Limit: 240 calls per hour.

emails (required)

Up to 25 emails, each with its sender, subject, date and plain-text body.

Save a checked claim to your Untap account

Sign-in required

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.

Limit: 30 calls per hour.

category (required)

Which kind of check the claim came from.

train (optional)

For category "train": the train booking, in the shape a train check returns in save_claim.arguments.train, with ticket_price_pence set.

flight (optional)

For category "flight": the flight, in the shape a flight check returns in save_claim.arguments.flight, with ticket_price_pence set.

tfl (optional)

For category "tfl": the journeys, in the shape a TfL check returns in save_claim.arguments.tfl.

List my claims

Sign-in required

list_my_claims

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.

Limit: 60 calls per hour.

category (optional)

Restricts the list to one category. When left out, all categories are listed.

include_closed (optional)

Also show claims marked paid, rejected or archived, and ones with nothing to claim.

limit (optional)

Most rows to return. Defaults to 25.

Update a claim’s status

Sign-in required

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.

Limit: 60 calls per hour.

claim_id (required)

The claim_id given when the claim was saved or listed.

status (required)

sent: submitted to the operator or airline. paid: money received. rejected: the claim was refused. archived: hide it without an outcome.

amount_received_pence (optional)

For paid: the amount actually received, in pence. £12.40 = 1240.

note (optional)

Optional short note, such as the operator’s reference or the reason given for a refusal.

Add a train booking

Sign-in required

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.

Limit: 30 calls per hour.

ticket_price_pence (required)

Total fare paid in pence for the whole booking. £62.00 = 6200.

ticket_type (required)

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.

season_type (optional)

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.

booking_reference (required)

Booking reference if available, otherwise null.

legs (required)

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.

Add a flight

Sign-in required

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.

Limit: 30 calls per hour.

airline_iata (required)

Two-letter IATA airline code, e.g. "BA" for British Airways, "U2" for easyJet.

flight_number (required)

Flight number including the airline prefix, e.g. "BA2551".

departure_iata (required)

Three-letter IATA departure airport code, e.g. "LHR".

arrival_iata (required)

Three-letter IATA arrival airport code, e.g. "BCN".

scheduled_departure (required)

Scheduled departure as ISO 8601 datetime.

scheduled_arrival (required)

Scheduled arrival as ISO 8601 datetime.

ticket_price_pence (required)

Total fare paid in pence.

booking_reference (required)

PNR / airline booking reference if available, otherwise null.

passenger_name (required)

Passenger name as printed on the ticket, or null if not visible.

status (optional)

Optional. What happened to the flight, if known. When left out, Untap looks the flight up in AeroDataBox flight-status records.

actual_arrival (optional)

Optional. Actual arrival as an ISO 8601 datetime, if known.

delay_minutes (optional)

Optional. Arrival delay in minutes, if known.

Add TfL journeys from a contactless statement

Sign-in required

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.

Limit: 10 calls per hour.

card_last4 (required)

Last 4 digits of the contactless card, if shown.

period_start (required)

Statement period start date YYYY-MM-DD.

period_end (required)

Statement period end date YYYY-MM-DD.

journeys (required)

Every journey on the statement. Up to 500 per call.

Add a parking ticket (PCN)

Sign-in required

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.

Limit: 30 calls per hour.

pcn_reference (required)

PCN or notice reference number printed on the document.

issuer_type (required)

Council = local authority issued under TMA 2004. Private = on private land by a parking operator (BPA or IPC member).

issuer_name (required)

Issuer name as written, e.g. "London Borough of Camden" or "ParkingEye Ltd".

contravention_code (required)

Council contravention code, e.g. "01", "12", "MR11". Null for private tickets.

contravention_description (required)

Full text of the alleged contravention as printed on the notice.

vehicle_registration (required)

Vehicle registration mark, or null if not shown.

location (required)

Street or car park name where the contravention allegedly occurred.

contravention_date (required)

Date the contravention allegedly occurred, ISO 8601 date.

issued_date (required)

Date the notice was issued or served, ISO 8601 date.

amount_pence (required)

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)

ISO date by which the discount applies, or null if not stated.

full_deadline (required)

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)

True if a paper notice was placed on the windscreen. False if it arrived in the post only.

keeper_notice_served_date (required)

Private only: date the Notice to Keeper was served.

observed_notes (required)

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.

List the person’s refund opportunities

Sign-in required

list_savings

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.

Limit: 60 calls per hour.

category (required)

Restrict to a single category, or null for all categories.

status (required)

Restrict to a single status, or null for all.

limit (optional)

Maximum number of savings rows to return. Defaults to 25, capped at 100.

Delete all my Untap data

Sign-in required

delete_my_data

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.

Limit: 5 calls per hour.

confirm (optional)

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 (optional)

The confirmation_token from a preview. Required when confirm is true; each token works once.

Questions or errors: contact@untap.money.