# Nomadpoint MCP server

Source: https://glimind.com/server/mcp-registry%2Fapp.nomadpoint%2Fnomadpoint
Registry id: `mcp-registry/app.nomadpoint/nomadpoint`
Status: auth-required (checked 2026-10-26T20:06:38.018Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 211
- Outages (90 days): 12

## Install

```json
{
  "mcpServers": {
    "nomadpoint-mcp-server": {
      "type": "http",
      "url": "https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http nomadpoint-mcp-server https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp
```

## Tools (43)

- `add_passport`: 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.
- `create_accommodation`: Add a booked place to stay (hotel/hostel/apartment) to a trip.
- `create_activity`: Add a thing to do — or a travel leg between places — to a trip, optionally attached to a stop.
- `create_document`: 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
- `create_expense`: 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 th
- `create_flight`: Add a flight to a trip.
- `create_journey`: Start a new trip. Use when the user wants a separate trip rather than adding to an existing one.
- `create_stay`: 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.
- `create_visa`: Record a visa the user holds or has applied for.
- `delete_accommodation`: Remove a booking from the trip.
- `delete_activity`: Remove an activity from the trip.
- `delete_document`: Delete one of the user's travel documents.
- `delete_expense`: Remove a recorded expense. Irreversible.
- `delete_flight`: Remove a flight from the trip.
- `delete_journey`: Permanently delete a trip and everything on it — stops, flights, bookings, activities — for every member. Owner only. Irreversible; confirm with the user first.
- `delete_stay`: Remove a stop from the trip. Refuses when the stop carries a booking — delete the booking instead.
- `delete_visa`: Delete a recorded visa.
- `get_budget`: 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.
- `get_country_info`: Country reference info and the user's visa requirement for it, based on their primary passport.
- `get_journey`: 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 SA
- `get_journey_share_link`: 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.
- `get_me`: Who the user is: profile, the passports/nationalities they hold (which decide every visa answer), and their recorded passport documents. Worth reading before pl
- `get_visa_status`: 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".
- `leave_journey`: Leave a trip someone else shared with the user. Owners can't leave their own trip — they delete it.
- `list_documents`: The user's travel documents (passports, visas, insurance, tickets) — metadata only, not the files.
- `list_expenses`: 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 ea
- `list_journey_members`: Who is on a trip: user ids, roles, and profiles. Use it to get the ids that set_item_travellers takes.
- `list_journeys`: List the user's trips (journeys) they own or have joined, with dates and whether they own it.
- `list_visas`: Visas the user holds — type, number, validity, entries used.
- `remove_journey_member`: Remove someone from a shared trip. Owner only.
- `search_airlines`: Find airlines by name or IATA code.
- `search_airports`: Find airports by city, name or IATA code. Use this to get the codes create_flight requires — never guess them.
- `search_cities`: Find cities by name. Use it to confirm the exact city name create_stay expects.
- `set_budget`: 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.
- `set_item_travellers`: 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
- `update_accommodation`: Change a booking's property, dates, price, confirmation or notes.
- `update_activity`: Change an activity's title, timing, place or notes.
- `update_expense`: Correct a recorded expense — its amount, currency, date, title, category or which stop it belongs to.
- `update_flight`: Change a flight's route, times, seat, confirmation or notes.
- `update_journey`: 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 warni
- `update_preferences`: 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 
- `update_stay`: Change a stop's city, country, dates or notes.
- `update_visa`: Change a recorded visa, or archive it by setting is_active to false.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.