**Untap** checks whether you are owed money in the UK, and tells you exactly how to get it back. Seven checks work straight away, without an account. - **Trains:** Untap looks up your journey in the rail industry's historic running records and works out Delay Repay under your operator's own scheme, for 23 operators, including the 120-minute tier that pays the whole return fare on 21 of them. - **Flights:** UK261 and EU261 compensation of £220, £350 or £520 (or €250, €400 or €600) for delays of three hours or more and for cancellations. Flights that leave the UK or the EU are covered whatever country you live in. - **TfL:** paste your contactless or Oyster journey history and Untap finds incomplete journeys and missed Hopper fares still inside the refund window. - **Claim instructions:** exact steps, form fields, evidence and escalation route for each operator, airline and TfL. - **Inbox scan:** finds possible claims in emails you share, without storing them. Every answer comes with the amount, the deadline and a link to the operator's or airline's own claim form. You send the claim yourself, so the money goes straight to you. Untap takes no cut and never files claims on your behalf. Sign in to Untap (OAuth 2.1) and your assistant can also save claims, track progress, check a saved commute for a date you choose and delete your data on request. The rules behind every check are published as open data at https://untap.money/open-data/rules. Built in London by Andrey.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (2985 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 20 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 88% of peers
- This listing 87 · peer median 81
- Latency
- Faster than 12% of peers
- This listing 815 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/untap/claims/mcpcurl -X POST https://server.smithery.ai/untap/claims/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'