io.github.aneduaim/untap-mcp

Est-ce que io.github.aneduaim/untap-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.aneduaim/untap-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 20 outils

• add_flight≈ 704 tokens

  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.

  Paramètres, retour & exemple (12)

  Paramètres

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

  Exemple d'appel

  {"name": "add_flight", "arguments": {"airline_iata": "texte", "arrival_iata": "texte", "flight_number": "texte", "departure_iata": "texte", "passenger_name": "texte", "booking_reference": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_parking_fine≈ 942 tokens

  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.

  Paramètres, retour & exemple (17)

  Paramètres

  • location · string · requis
    Street or car park name where the contravention allegedly occurred.
  • appeal_url · ? · requis
    Direct https URL on the notice for online appeals, or null if none.
  • issued_date · string · requis
    Date the notice was issued or served, ISO 8601 date.
  • issuer_name · string · requis
    Issuer name as written, e.g. "London Borough of Camden" or "ParkingEye Ltd".
  • issuer_type · string · requis · council | private
    Council = local authority issued under TMA 2004. Private = on private land by a parking operator (BPA or IPC member).
  • amount_pence · integer · requis
    Full charge amount in pence. £65 = 6500.
  • full_deadline · string|null · requis
    Last date on the notice for paying the full amount or lodging an appeal, as an ISO date.
  • pcn_reference · string · requis
    PCN or notice reference number printed on the document.
  • observed_notes · array · requis
    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.
  • discount_deadline · string|null · requis
    ISO date by which the discount applies, or null if not stated.
  • contravention_code · string|null · requis
    Council contravention code, e.g. "01", "12", "MR11". Null for private tickets.
  • contravention_date · string · requis
    Date the contravention allegedly occurred, ISO 8601 date.
  • vehicle_registration · string|null · requis
    Vehicle registration mark, or null if not shown.
  • has_windscreen_notice · boolean · requis
    True if a paper notice was placed on the windscreen. False if it arrived in the post only.
  • discounted_amount_pence · ? · requis
    Reduced amount in pence if paid promptly (usually 50% within 14 or 21 days). Null if none stated.
  • contravention_description · string · requis
    Full text of the alleged contravention as printed on the notice.
  • keeper_notice_served_date · string|null · requis
    Private only: date the Notice to Keeper was served.

  Exemple d'appel

  {"name": "add_parking_fine", "arguments": {"location": "texte", "appeal_url": "texte", "issued_date": "texte", "issuer_name": "texte", "issuer_type": "council", "amount_pence": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_tfl_journeys≈ 1016 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • journeys · array · requis
    Every journey on the statement. Up to 500 per call.
  • card_last4 · string|null · requis
    Last 4 digits of the contactless card, if shown.
  • period_end · string|null · requis
    Statement period end date YYYY-MM-DD.
  • period_start · string|null · requis
    Statement period start date YYYY-MM-DD.

  Exemple d'appel

  {"name": "add_tfl_journeys", "arguments": {"journeys": [], "card_last4": "texte", "period_end": "texte", "period_start": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• add_train_journey≈ 1088 tokens

  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.

  Paramètres, retour & exemple (5)

  Paramètres

  • legs · array · requis
    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 · ? · optionnel
    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.
  • ticket_type · string · requis · single | return | open_return | advance | anytime | off_peak | super_off_peak | season
    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 · string|null · requis
    Booking reference if available, otherwise null.
  • ticket_price_pence · integer · requis
    Total fare paid in pence for the whole booking. £62.00 = 6200.

  Exemple d'appel

  {"name": "add_train_journey", "arguments": {"legs": [], "ticket_type": "single", "booking_reference": "texte", "ticket_price_pence": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_commute≈ 320 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "check_commute", "arguments": {"date": "texte", "commute_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_flight_compensation≈ 732 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • date · string · requis
    Date the flight was due to depart, local time. YYYY-MM-DD is best.
  • price_paid · ? · optionnel
    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 · ? · optionnel
    Three-letter arrival airport code, if known: "BCN".
  • from_airport · ? · optionnel
    Three-letter departure airport code, if known: "LGW". Helps pick the right flight on multi-stop numbers.
  • flight_number · string · requis
    Airline code and number, as on the booking: "BA2551", "U2 8123".
  • what_happened · ? · optionnel
    What happened, if known. When left out, Untap looks it up in flight-status records.
  • arrival_delay_minutes · ? · optionnel
    How late the flight arrived at the gate, in minutes, if the person knows. Compensation turns on arrival, not departure.
  • cancellation_notice_days · ? · optionnel
    For a cancellation: how many days before departure the airline told the person. 14 or more means no compensation.

  Exemple d'appel

  {"name": "check_flight_compensation", "arguments": {"date": "texte", "flight_number": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_tfl_journeys≈ 1098 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "check_tfl_journeys", "arguments": {"csv_text": "texte", "journeys": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_train_delay≈ 953 tokens

  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.

  Paramètres, retour & exemple (9)

  Paramètres

  • to · string · requis
    Station the person got off at, in the same forms.
  • date · string · requis
    Date of travel. YYYY-MM-DD is best; "25/09/2026", "25 September", "yesterday" and "last Friday" also work.
  • from · string · requis
    Station the person got on at. A name, part of a name or a three-letter code: "Brighton", "Kings Cross", "BTN".
  • tickets · ? · optionnel
    How many tickets of this price are on the booking, one per passenger. Defaults to 1. The amount is per ticket times this.
  • operator · ? · optionnel
    Train company if known, as the person says it: "Southern", "GWR", "Avanti". Used to narrow the match.
  • price_paid · ? · optionnel
    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 · ? · optionnel
    The service_id of a train listed in an earlier result. With it, that train is checked directly.
  • ticket_type · ? · optionnel
    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 · ? · optionnel
    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.

  Exemple d'appel

  {"name": "check_train_delay", "arguments": {"to": "texte", "date": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• delete_my_data≈ 316 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • confirm · boolean · optionnel
    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 · optionnel
    The confirmation_token from a preview. Required when confirm is true; each token works once.

  Exemple d'appel

  {"name": "delete_my_data", "arguments": {"confirm": true, "confirmation_token": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_money_owed≈ 343 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • situation · string · requis
    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".

  Exemple d'appel

  {"name": "find_money_owed", "arguments": {"situation": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_claim_instructions≈ 844 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

  • company · ? · optionnel
    The train operator or airline, by name or code as people say it: "Southern", "LNER", "easyJet", "BA", "U2". Not needed for TfL.
  • booked_via · ? · optionnel
    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.
  • claim_type · string · requis · train_delay | train_cancellation | flight_delay | flight_cancellation | denied_boarding | tfl_incomplete_journey | tfl_overcharge
    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.
  • ticket_type · ? · optionnel
    Ticket type as printed, such as "Anytime Return", "Advance Single" or "Season". Decides the rail return-ticket rule.
  • journey_date · ? · optionnel
    Date of travel, YYYY-MM-DD. With it, the result gives the last day to claim as a date.
  • arrival_airport · ? · optionnel
    Three-letter arrival airport code, such as "LHR".
  • departure_airport · ? · optionnel
    Three-letter departure airport code, such as "CDG". Decides whether UK261 or EU261 applies, and with the arrival airport, the distance band.

  Exemple d'appel

  {"name": "get_claim_instructions", "arguments": {"claim_type": "train_delay"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_delay_repay_rules≈ 240 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

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

  Exemple d'appel

  {"name": "get_delay_repay_rules", "arguments": {"operator": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_commutes≈ 156 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

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

  Exemple d'appel

  {"name": "list_commutes", "arguments": {"include_stopped": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_my_claims≈ 280 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "list_my_claims", "arguments": {"limit": 1, "category": "texte", "include_closed": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_savings≈ 323 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Maximum number of savings rows to return. Defaults to 25, capped at 100.
  • status · ? · requis
    Restrict to a single status, or null for all.
  • category · ? · requis
    Restrict to a single category, or null for all categories.

  Exemple d'appel

  {"name": "list_savings", "arguments": {"status": "texte", "category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• save_claim≈ 2516 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • tfl · ? · optionnel
    For category "tfl": the journeys, in the shape a TfL check returns in save_claim.arguments.tfl.
  • train · ? · optionnel
    For category "train": the train booking, in the shape a train check returns in save_claim.arguments.train, with ticket_price_pence set.
  • flight · ? · optionnel
    For category "flight": the flight, in the shape a flight check returns in save_claim.arguments.flight, with ticket_price_pence set.
  • category · string · requis · train | flight | tfl
    Which kind of check the claim came from.

  Exemple d'appel

  {"name": "save_claim", "arguments": {"category": "train"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• save_commute≈ 588 tokens

  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.

  Paramètres, retour & exemple (8)

  Paramètres

  • to · string · requis
    Arrival station name or three-letter code.
  • from · string · requis
    Departure station name or three-letter code.
  • label · ? · optionnel
    Optional short name such as Morning commute.
  • weekdays · array · optionnel
    Usual travel days: Monday=1 through Sunday=7. Informational only; no automatic checks.
  • commute_id · ? · optionnel
    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 · optionnel · single | return
    Day ticket type. For return, the price is the whole return fare. Season tickets are not supported by saved commutes.
  • departure_time · string · requis
    Usual UK departure time, for example 08:05 or 8am.
  • ticket_price_pence · ? · optionnel
    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.

  Exemple d'appel

  {"name": "save_commute", "arguments": {"to": "texte", "from": "texte", "departure_time": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• scan_for_claims≈ 517 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

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

  Exemple d'appel

  {"name": "scan_for_claims", "arguments": {"emails": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• stop_commute≈ 176 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • commute_id · string · requis
    The id of a saved commute. The route is kept and can be restored.

  Exemple d'appel

  {"name": "stop_commute", "arguments": {"commute_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_claim_status≈ 368 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "update_claim_status", "arguments": {"status": "sent", "claim_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://untap.money/api/mcp