app.nomadpoint/nomadpoint
REMOTE · GXHDCVOVEUFBKTHHENDF.SUPABASE.CO
Plan trips and track visa days per traveller across 39,601 entry rules
Available components
Last scanned (20 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 0
- Stability: pass → 0.97 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 0
- Schema quality: unverified → 100 ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- New resource “journey_itinerary” functional
- 12 Sept 26 0
- New tool “create_document” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2b50611cd88e9c50e4e2231f4d3f059 |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gxhdcvoveufbkthhendf.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://nomadpoint.app/.well-known/oauth-protected-resource/mcp", scope="email"
Bearer resource_metadata="https://nomadpoint.app/.well-known/oauth-protected-resource/mcp", scope="email"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| www-authenticate | Bearer resource_metadata="https://nomadpoint.app/.well-known/oauth-protected-resource/mcp", scope="email" |
Protected resource metadata
| Document | https://nomadpoint.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Problem | metadata_resource_mismatch |
| Resource | https://nomadpoint.app/mcp |
| Authorisation server | https://gxhdcvoveufbkthhendf.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp | Auth required | 401 | |
| http (plaintext) | http://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp | HTTPS enforced | 301 | https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_passport ~113
Record a passport from its details alone (no scan needed). Also adds the country to the user's nationalities, which is what visa answers are computed from.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | – |
| expiry_date | string | – | ISO date, e.g. 2026-08-01 |
| is_primary | boolean | – | – |
| issue_date | string | – | ISO date, e.g. 2026-08-01 |
| passport_number | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
create_accommodation ~277
Add a booked place to stay (hotel/hostel/apartment) to a trip.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| booking_url | string | – | – |
| check_in | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| check_out | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| confirmation_code | string | – | – |
| country_code | string | – | – |
| currency | string | – | – |
| journey_id | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | – | The property's own name, e.g. 'Memmo Alfama' |
| notes | string | – | – |
| place_name | string | – | The CITY the property is in, e.g. 'Lisbon' — not the property's name |
| price_per_night | number | – | – |
| provider | string | – | Who it was booked with, e.g. 'Booking.com' |
| travelers | array | – | Member user ids this is for (from list_journey_members). Omit for everyone — that's the norm. |
| type | string | yes | hotel, hostel, airbnb, apartment, other |
No output schema declared.
No examples provided.
create_activity ~289
Add a thing to do — or a travel leg between places — to a trip, optionally attached to a stop.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| booking_url | string | – | – |
| category | string | – | – |
| country_code | string | – | – |
| currency | string | – | – |
| emoji | string | – | – |
| end_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| is_booked | boolean | – | False = planned but not yet purchased/reserved. Set true only once payment actually went through. |
| journey_id | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| notes | string | – | – |
| place_name | string | – | – |
| price | number | – | – |
| start_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| stay_id | string | – | UUID of the stop this belongs to — attaches it to that city's days |
| title | string | yes | – |
| transport_mode | string | – | For a travel leg: walk, taxi, train, bus, ferry, drive |
| travelers | array | – | Member user ids this is for (from list_journey_members). Omit for everyone — that's the norm. |
No output schema declared.
No examples provided.
create_document ~215
Record a travel document (ticket, boarding pass, hotel confirmation, insurance…) and, when a file_name/mime_type is given, return a signed upload_url to PUT the file to. Use related_id to attach it to the flight, accommodation or activity it belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | – |
| document_type | string | yes | passport, visa, boarding_pass, hotel_confirmation, travel_insurance, vaccination, national_id, drivers_license, onward_ticket, other |
| file_name | string | – | e.g. ticket-14147653.pdf — only needed when a file will be uploaded |
| mime_type | string | – | e.g. application/pdf, image/jpeg |
| related_id | string | – | UUID of the flight/accommodation/activity this document belongs to |
| title | string | yes | – |
| valid_from | string | – | ISO date, e.g. 2026-08-01 |
| valid_until | string | – | ISO date, e.g. 2026-08-01 |
No output schema declared.
No examples provided.
create_expense ~345
Record one thing the user spent money on. Use for spend with no itinerary item of its own — meals, transport, visa fees, a booking that isn't on the trip. If the purchase IS already on the itinerary, set its price with update_flight/update_accommodation/update_activity instead; doing both counts it twice. Pass source_ref when importing so a re-run can't duplicate it.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | The total actually paid. Never a deposit, a per-night rate or a single fee. |
| amount_usd | number | – | The same amount in USD, frozen at entry. Set it ONLY when the source states a USD (or already-converted home-currency) figure. Omit otherwise — the app converts at the live rate, which is honest, whe… |
| category | string | yes | One of the app's expense categories. Food is 'restaurant'. |
| currency | string | yes | ISO 4217 code, e.g. USD, EUR, THB |
| journey_id | string | yes | – |
| related_event_id | string | – | The flight/booking/activity this relates to, if any. |
| source_ref | string | – | Where this came from, e.g. 'gmail:<messageId>'. Unique per user — a repeat import is refused. |
| spent_on | string | yes | ISO date, e.g. 2026-08-01 |
| stay_id | string | – | The stop this belongs to. Omit unless certain — an expense with a date is attributed to the stop whose dates contain it automatically. |
| title | string | yes | What it was, as the user would recognise it |
No output schema declared.
No examples provided.
create_flight ~305
Add a flight to a trip.
| Name | Type | Req | Description |
|---|---|---|---|
| airline_code | string | – | IATA airline code, e.g. 'TP' — find it with search_airlines |
| airline_name | string | – | – |
| arrival_airport_code | string | yes | IATA code, e.g. 'NRT' — find it with search_airports |
| arrival_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| arrival_terminal | string | – | – |
| booking_url | string | – | – |
| cabin_class | string | – | – |
| confirmation_code | string | – | – |
| currency | string | – | – |
| departure_airport_code | string | yes | IATA code, e.g. 'JFK' — find it with search_airports |
| departure_datetime | string | yes | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| departure_terminal | string | – | – |
| flight_number | string | – | – |
| is_onward_ticket | boolean | – | Mark it as the proof-of-onward-travel ticket for an entry requirement |
| journey_id | string | yes | – |
| notes | string | – | – |
| price | number | – | – |
| seat | string | – | – |
| travelers | array | – | Member user ids this is for (from list_journey_members). Omit for everyone — that's the norm. |
No output schema declared.
No examples provided.
create_journey ~86
Start a new trip. Use when the user wants a separate trip rather than adding to an existing one.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| end_date | string | – | ISO date, e.g. 2026-08-01 |
| name | string | yes | – |
| start_date | string | – | ISO date, e.g. 2026-08-01 |
No output schema declared.
No examples provided.
create_stay ~234
Add a stay — a stop in a city — to a trip. This is how a destination gets onto the itinerary; book lodging for it with create_accommodation on the same dates.
| Name | Type | Req | Description |
|---|---|---|---|
| checkin_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| checkout_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| checkout_flexible | boolean | – | – |
| city | string | yes | City name, e.g. 'Lisbon' — the city itself, not a neighbourhood, street or hotel |
| city_code | string | – | Optional alternative to `city` when you already know the code, e.g. 'LIS' |
| country_code | string | yes | ISO country code, e.g. 'JP' |
| journey_id | string | yes | – |
| notes | string | – | – |
| travelers | array | – | Member user ids this is for (from list_journey_members). Omit for everyone — that's the norm. |
No output schema declared.
No examples provided.
create_visa ~193
Record a visa the user holds or has applied for.
| Name | Type | Req | Description |
|---|---|---|---|
| application_date | string | – | ISO date, e.g. 2026-08-01 |
| cost_currency | string | – | – |
| cost_paid | number | – | – |
| country_code | string | yes | – |
| embassy_consulate | string | – | – |
| entries_allowed | string | – | single, double, multiple |
| expiry_date | string | – | ISO date, e.g. 2026-08-01 |
| issue_date | string | – | ISO date, e.g. 2026-08-01 |
| max_entries | number | – | – |
| notes | string | – | – |
| passport_country_code | string | – | – |
| visa_name | string | – | – |
| visa_number | string | – | – |
| visa_type | string | yes | e.g. tourist, business, student, work, digital_nomad, transit |
No output schema declared.
No examples provided.
delete_accommodation ~24
Remove a booking from the trip.
| Name | Type | Req | Description |
|---|---|---|---|
| accommodation_id | string | yes | – |
No output schema declared.
No examples provided.
delete_activity ~23
Remove an activity from the trip.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | – |
No output schema declared.
No examples provided.
delete_document ~24
Delete one of the user's travel documents.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | – |
No output schema declared.
No examples provided.
delete_expense ~26
Remove a recorded expense. Irreversible.
| Name | Type | Req | Description |
|---|---|---|---|
| expense_id | string | yes | – |
No output schema declared.
No examples provided.
delete_flight ~24
Remove a flight from the trip.
| Name | Type | Req | Description |
|---|---|---|---|
| flight_id | string | yes | – |
No output schema declared.
No examples provided.
delete_journey ~52
Permanently delete a trip and everything on it — stops, flights, bookings, activities — for every member. Owner only. Irreversible; confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | – |
No output schema declared.
No examples provided.
delete_stay ~38
Remove a stop from the trip. Refuses when the stop carries a booking — delete the booking instead.
| Name | Type | Req | Description |
|---|---|---|---|
| stay_id | string | yes | – |
No output schema declared.
No examples provided.
delete_visa ~22
Delete a recorded visa.
| Name | Type | Req | Description |
|---|---|---|---|
| visa_id | string | yes | – |
No output schema declared.
No examples provided.
get_budget ~51
The user's own spending target for a trip, if they set one. Personal, not shared: each member of a trip has their own, and no one else's is readable.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | – |
No output schema declared.
No examples provided.
get_country_info ~43
Country reference info and the user's visa requirement for it, based on their primary passport.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | ISO country code, e.g. 'TH' |
No output schema declared.
No examples provided.
get_journey ~124
Get one journey's itinerary: stays (the stops), flights, booked accommodations, and activities. A booked stay is ONE row that appears in both lists under the SAME id — the stop it is, and the booking it carries. Pass from_date/to_date to read one window of a long trip instead of all of it.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | ISO date, e.g. 2026-08-01 |
| journey_id | string | yes | – |
| to_date | string | – | ISO date, e.g. 2026-08-01 |
No output schema declared.
No examples provided.
get_journey_share_link ~53
The link that invites someone onto a trip as a co-editor. Anyone who opens it joins immediately, so it is the whole invite — there is no separate accept step.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | – |
No output schema declared.
No examples provided.
get_me ~41
Who the user is: profile, the passports/nationalities they hold (which decide every visa answer), and their recorded passport documents. Worth reading before planning anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_visa_status ~55
How many days of the user's allowance in a country are used and how many remain this year — the answer to "how much longer can I stay".
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | – |
| year | number | – | – |
No output schema declared.
No examples provided.
leave_journey ~38
Leave a trip someone else shared with the user. Owners can't leave their own trip — they delete it.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | – |
No output schema declared.
No examples provided.
list_documents ~66
The user's travel documents (passports, visas, insurance, tickets) — metadata only, not the files.
| Name | Type | Req | Description |
|---|---|---|---|
| document_type | string | – | Filter: passport, national_id, drivers_license, boarding_pass, hotel_confirmation, travel_insurance, vaccination, visa, onward_ticket, other |
No output schema declared.
No examples provided.
list_expenses ~108
Recorded spending on a trip — the money entered by hand or imported, NOT the booked prices on flights and hotels (those come back from get_journey). Includes each row's source_ref, so an importer can see what it already brought in.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | ISO date, e.g. 2026-08-01 |
| journey_id | string | yes | – |
| to_date | string | – | ISO date, e.g. 2026-08-01 |
No output schema declared.
No examples provided.
list_journey_members ~46
Who is on a trip: user ids, roles, and profiles. Use it to get the ids that set_item_travellers takes.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | – |
No output schema declared.
No examples provided.
list_journeys ~32
List the user's trips (journeys) they own or have joined, with dates and whether they own it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_visas ~24
Visas the user holds — type, number, validity, entries used.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_journey_member ~36
Remove someone from a shared trip. Owner only.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | yes | – |
| user_id | string | yes | – |
No output schema declared.
No examples provided.
search_airlines ~32
Find airlines by name or IATA code.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
search_airports ~49
Find airports by city, name or IATA code. Use this to get the codes create_flight requires — never guess them.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
search_cities ~49
Find cities by name. Use it to confirm the exact city name create_stay expects.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | – |
| limit | number | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
set_budget ~93
Set or replace the user's own spending target for a trip. 'month' means per month of the trip; 'journey' means the whole trip. Replaces any existing target.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| currency | string | yes | ISO 4217 code, e.g. USD, EUR, THB |
| journey_id | string | yes | – |
| period | string | – | Defaults to 'month'. |
No output schema declared.
No examples provided.
set_item_travellers ~99
Say which people on a shared trip an item is for — one person's separate flight, one person's room. Omitting travelers (or passing an empty list) means everyone, which is the default and right for most items.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | – |
| item_type | string | yes | – |
| travelers | array | – | Member user ids this is for (from list_journey_members). Omit for everyone — that's the norm. |
No output schema declared.
No examples provided.
update_accommodation ~245
Change a booking's property, dates, price, confirmation or notes.
| Name | Type | Req | Description |
|---|---|---|---|
| accommodation_id | string | yes | – |
| address | string | – | – |
| booking_url | string | – | – |
| check_in | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| check_out | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| confirmation_code | string | – | – |
| country_code | string | – | – |
| currency | string | – | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | – | The property's own name, e.g. 'Memmo Alfama' |
| notes | string | – | – |
| place_name | string | – | The CITY the property is in, e.g. 'Lisbon' — not the property's name |
| price_per_night | number | – | – |
| provider | string | – | Who it was booked with, e.g. 'Booking.com' |
| type | string | – | hotel, hostel, airbnb, apartment, other |
No output schema declared.
No examples provided.
update_activity ~250
Change an activity's title, timing, place or notes.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | – |
| address | string | – | – |
| booking_url | string | – | – |
| category | string | – | – |
| country_code | string | – | – |
| currency | string | – | – |
| emoji | string | – | – |
| end_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| is_booked | boolean | – | False = planned but not yet purchased/reserved. Set true only once payment actually went through. |
| latitude | number | – | – |
| longitude | number | – | – |
| notes | string | – | – |
| place_name | string | – | – |
| price | number | – | – |
| start_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| stay_id | string | – | UUID of the stop this belongs to — attaches it to that city's days |
| title | string | – | – |
| transport_mode | string | – | For a travel leg: walk, taxi, train, bus, ferry, drive |
No output schema declared.
No examples provided.
update_expense ~195
Correct a recorded expense — its amount, currency, date, title, category or which stop it belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| amount_usd | number | – | The same amount in USD, frozen at entry. Set it ONLY when the source states a USD (or already-converted home-currency) figure. Omit otherwise — the app converts at the live rate, which is honest, whe… |
| category | string | – | One of the app's expense categories. Food is 'restaurant'. |
| currency | string | – | ISO 4217 code, e.g. USD, EUR, THB |
| expense_id | string | yes | – |
| related_event_id | string | – | – |
| spent_on | string | – | ISO date, e.g. 2026-08-01 |
| stay_id | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
update_flight ~284
Change a flight's route, times, seat, confirmation or notes.
| Name | Type | Req | Description |
|---|---|---|---|
| airline_code | string | – | IATA airline code, e.g. 'TP' — find it with search_airlines |
| airline_name | string | – | – |
| arrival_airport_code | string | – | IATA code, e.g. 'NRT' — find it with search_airports |
| arrival_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| arrival_terminal | string | – | – |
| booking_url | string | – | – |
| cabin_class | string | – | – |
| confirmation_code | string | – | – |
| currency | string | – | – |
| departure_airport_code | string | – | IATA code, e.g. 'JFK' — find it with search_airports |
| departure_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| departure_terminal | string | – | – |
| flight_id | string | yes | – |
| flight_number | string | – | – |
| is_onward_ticket | boolean | – | Mark it as the proof-of-onward-travel ticket for an entry requirement |
| notes | string | – | – |
| price | number | – | – |
| seat | string | – | – |
No output schema declared.
No examples provided.
update_journey ~134
Rename a trip, change its dates or description, archive it, or set its home-base countries (countries where the user has their own place — no missing-stay warnings there). Owner only.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| end_date | string | – | ISO date, e.g. 2026-08-01 |
| home_base_country_codes | array | – | ISO country codes |
| is_archived | boolean | – | – |
| journey_id | string | yes | – |
| name | string | – | – |
| start_date | string | – | ISO date, e.g. 2026-08-01 |
No output schema declared.
No examples provided.
update_preferences ~155
Set the standing facts every trip should respect: where home is, the home airport, the currency to quote in, nightly budget, travel pace, and preferred working hours.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_max | number | – | – |
| budget_min | number | – | – |
| currency | string | – | – |
| home_airport_code | string | – | – |
| home_city | string | – | – |
| home_country_code | string | – | – |
| temperature_preference | string | – | – |
| travel_pace | string | – | e.g. slow, moderate, fast |
| work_end_hour | number | – | – |
| work_start_hour | number | – | – |
| work_timezone | string | – | IANA zone, e.g. Europe/Lisbon |
No output schema declared.
No examples provided.
update_stay ~181
Change a stop's city, country, dates or notes.
| Name | Type | Req | Description |
|---|---|---|---|
| checkin_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| checkout_datetime | string | – | ISO-8601 datetime, e.g. 2026-08-01T14:30:00Z |
| checkout_flexible | boolean | – | – |
| city | string | – | City name, e.g. 'Lisbon' — the city itself, not a neighbourhood, street or hotel |
| city_code | string | – | Optional alternative to `city` when you already know the code, e.g. 'LIS' |
| country_code | string | – | ISO country code, e.g. 'JP' |
| notes | string | – | – |
| stay_id | string | yes | – |
No output schema declared.
No examples provided.
update_visa ~175
Change a recorded visa, or archive it by setting is_active to false.
| Name | Type | Req | Description |
|---|---|---|---|
| application_date | string | – | ISO date, e.g. 2026-08-01 |
| cost_currency | string | – | – |
| cost_paid | number | – | – |
| embassy_consulate | string | – | – |
| entries_allowed | string | – | – |
| expiry_date | string | – | ISO date, e.g. 2026-08-01 |
| is_active | boolean | – | – |
| issue_date | string | – | ISO date, e.g. 2026-08-01 |
| max_entries | number | – | – |
| notes | string | – | – |
| visa_id | string | yes | – |
| visa_name | string | – | – |
| visa_number | string | – | – |
| visa_type | string | – | – |
No output schema declared.
No examples provided.
How do I install the app.nomadpoint/nomadpoint MCP server?
app.nomadpoint/nomadpoint is a hosted endpoint at https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · gxhdcvoveufbkthhendf.supabase.co
claude mcp add --transport http app-nomadpoint-nomadpoint 'https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp'
What is the app.nomadpoint/nomadpoint MCP server?
app.nomadpoint/nomadpoint is an MCP server listed in the public MCP registry as app.nomadpoint/nomadpoint. Plan trips and track visa days per traveller across 39,601 entry rules. This page covers its hosted endpoint (https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp).
Is the app.nomadpoint/nomadpoint MCP server safe to use?
app.nomadpoint/nomadpoint scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the app.nomadpoint/nomadpoint MCP server expose?
app.nomadpoint/nomadpoint exposes 43 tools: list_journeys, get_journey, create_journey, update_journey, delete_journey, and 38 more. Their descriptions and schemas cost roughly 4,948 tokens of context every time the server is loaded.
Does the app.nomadpoint/nomadpoint MCP server require authentication?
Yes. app.nomadpoint/nomadpoint asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the app.nomadpoint/nomadpoint MCP server still maintained?
app.nomadpoint/nomadpoint is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.