# app.nomadpoint/nomadpoint (remote · gxhdcvoveufbkthhendf.supabase.co)

Plan trips and track visa days per traveller across 39,601 entry rules

- Trust score: 90/100 (high trust)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `gxhdcvoveufbkthhendf.supabase.co`: 90/100 (this document), [markdown](https://verifymcp.io/servers/app-nomadpoint-nomadpoint/functions-v1-mcp.md), [page](https://verifymcp.io/servers/app-nomadpoint-nomadpoint/functions-v1-mcp)

## Channel facts

- Endpoint: `https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5144 tokens (~116/item across 44 items; 43 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 38% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 45 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

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

### Claude

```bash
claude mcp add --transport http app-nomadpoint-nomadpoint 'https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-nomadpoint-nomadpoint": {
      "url": "https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.app-nomadpoint-nomadpoint]
url = "https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-nomadpoint-nomadpoint": {
      "type": "remote",
      "url": "https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-nomadpoint-nomadpoint --url 'https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-nomadpoint-nomadpoint:
    url: "https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-nomadpoint-nomadpoint": {
      "Transport": "http",
      "Url": "https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-nomadpoint-nomadpoint -t streamable-http -u 'https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 90, 0)

- [functional] Stability: pass → 0.97

### 2026-09-19 (score 90, 0)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 88, +3)

- [functional improvement] Schema quality: unverified → 100
- [functional] The server now declares the “resources” capability
- [functional] First check of Capabilities: pass
- [functional] New resource “journey_itinerary”

### 2026-09-13 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 84, 0)

- [functional] New tool “create_document”

### 2026-09-11 (score 84, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [cosmetic] “create_activity” added an optional parameter “is_booked”
- [cosmetic] “update_activity” added an optional parameter “is_booked”

## MCP tools (43)

### `list_journeys` (~32 tokens)

List the user's trips (journeys) they own or have joined, with dates and whether they own it.

### `get_journey` (~124 tokens)

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.

Input parameters:

- `from_date` (string): ISO date, e.g. 2026-08-01
- `journey_id` (string, required)
- `to_date` (string): ISO date, e.g. 2026-08-01

### `create_journey` (~86 tokens)

Start a new trip. Use when the user wants a separate trip rather than adding to an existing one.

Input parameters:

- `description` (string)
- `end_date` (string): ISO date, e.g. 2026-08-01
- `name` (string, required)
- `start_date` (string): ISO date, e.g. 2026-08-01

### `update_journey` (~134 tokens)

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.

Input parameters:

- `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, required)
- `name` (string)
- `start_date` (string): ISO date, e.g. 2026-08-01

### `delete_journey` (~52 tokens)

Permanently delete a trip and everything on it — stops, flights, bookings, activities — for every member. Owner only. Irreversible; confirm with the user first.

Input parameters:

- `journey_id` (string, required)

### `get_journey_share_link` (~53 tokens)

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.

Input parameters:

- `journey_id` (string, required)

### `list_journey_members` (~46 tokens)

Who is on a trip: user ids, roles, and profiles. Use it to get the ids that set_item_travellers takes.

Input parameters:

- `journey_id` (string, required)

### `remove_journey_member` (~36 tokens)

Remove someone from a shared trip. Owner only.

Input parameters:

- `journey_id` (string, required)
- `user_id` (string, required)

### `leave_journey` (~38 tokens)

Leave a trip someone else shared with the user. Owners can't leave their own trip — they delete it.

Input parameters:

- `journey_id` (string, required)

### `create_stay` (~234 tokens)

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.

Input parameters:

- `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, required): 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, required): ISO country code, e.g. 'JP'
- `journey_id` (string, required)
- `notes` (string)
- `travelers` (array): Member user ids this is for (from list_journey_members). Omit for everyone — that's the norm.

### `create_flight` (~305 tokens)

Add a flight to a trip.

Input parameters:

- `airline_code` (string): IATA airline code, e.g. 'TP' — find it with search_airlines
- `airline_name` (string)
- `arrival_airport_code` (string, required): 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, required): IATA code, e.g. 'JFK' — find it with search_airports
- `departure_datetime` (string, required): 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, required)
- `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.

### `create_accommodation` (~277 tokens)

Add a booked place to stay (hotel/hostel/apartment) to a trip.

Input parameters:

- `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, required)
- `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, required): hotel, hostel, airbnb, apartment, other

### `create_activity` (~289 tokens)

Add a thing to do — or a travel leg between places — to a trip, optionally attached to a stop.

Input parameters:

- `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, required)
- `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, required)
- `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.

### `update_stay` (~181 tokens)

Change a stop's city, country, dates or notes.

Input parameters:

- `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, required)

### `update_flight` (~284 tokens)

Change a flight's route, times, seat, confirmation or notes.

Input parameters:

- `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, required)
- `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)

### `update_accommodation` (~245 tokens)

Change a booking's property, dates, price, confirmation or notes.

Input parameters:

- `accommodation_id` (string, required)
- `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

### `update_activity` (~250 tokens)

Change an activity's title, timing, place or notes.

Input parameters:

- `activity_id` (string, required)
- `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

### `delete_stay` (~38 tokens)

Remove a stop from the trip. Refuses when the stop carries a booking — delete the booking instead.

Input parameters:

- `stay_id` (string, required)

### `delete_flight` (~24 tokens)

Remove a flight from the trip.

Input parameters:

- `flight_id` (string, required)

### `delete_accommodation` (~24 tokens)

Remove a booking from the trip.

Input parameters:

- `accommodation_id` (string, required)

### `delete_activity` (~23 tokens)

Remove an activity from the trip.

Input parameters:

- `activity_id` (string, required)

### `set_item_travellers` (~99 tokens)

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.

Input parameters:

- `item_id` (string, required)
- `item_type` (string, required)
- `travelers` (array): Member user ids this is for (from list_journey_members). Omit for everyone — that's the norm.

### `list_expenses` (~108 tokens)

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.

Input parameters:

- `from_date` (string): ISO date, e.g. 2026-08-01
- `journey_id` (string, required)
- `to_date` (string): ISO date, e.g. 2026-08-01

### `create_expense` (~345 tokens)

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.

Input parameters:

- `amount` (number, required): 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, required): One of the app's expense categories. Food is 'restaurant'.
- `currency` (string, required): ISO 4217 code, e.g. USD, EUR, THB
- `journey_id` (string, required)
- `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, required): 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, required): What it was, as the user would recognise it

### `update_expense` (~195 tokens)

Correct a recorded expense — its amount, currency, date, title, category or which stop it belongs to.

Input parameters:

- `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, required)
- `related_event_id` (string)
- `spent_on` (string): ISO date, e.g. 2026-08-01
- `stay_id` (string)
- `title` (string)

### `delete_expense` (~26 tokens)

Remove a recorded expense. Irreversible.

Input parameters:

- `expense_id` (string, required)

### `get_budget` (~51 tokens)

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.

Input parameters:

- `journey_id` (string, required)

### `set_budget` (~93 tokens)

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.

Input parameters:

- `amount` (number, required)
- `currency` (string, required): ISO 4217 code, e.g. USD, EUR, THB
- `journey_id` (string, required)
- `period` (string): Defaults to 'month'.

### `get_me` (~41 tokens)

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.

### `get_country_info` (~43 tokens)

Country reference info and the user's visa requirement for it, based on their primary passport.

Input parameters:

- `country_code` (string, required): ISO country code, e.g. 'TH'

### `get_visa_status` (~55 tokens)

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

Input parameters:

- `country_code` (string, required)
- `year` (number)

### `search_airports` (~49 tokens)

Find airports by city, name or IATA code. Use this to get the codes create_flight requires — never guess them.

Input parameters:

- `limit` (number)
- `query` (string, required)

### `search_cities` (~49 tokens)

Find cities by name. Use it to confirm the exact city name create_stay expects.

Input parameters:

- `country_code` (string)
- `limit` (number)
- `query` (string, required)

### `search_airlines` (~32 tokens)

Find airlines by name or IATA code.

Input parameters:

- `limit` (number)
- `query` (string, required)

### `update_preferences` (~155 tokens)

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.

Input parameters:

- `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

### `list_documents` (~66 tokens)

The user's travel documents (passports, visas, insurance, tickets) — metadata only, not the files.

Input parameters:

- `document_type` (string): Filter: passport, national_id, drivers_license, boarding_pass, hotel_confirmation, travel_insurance, vaccination, visa, onward_ticket, other

### `add_passport` (~113 tokens)

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.

Input parameters:

- `country_code` (string, required)
- `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)

### `create_document` (~215 tokens)

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.

Input parameters:

- `country_code` (string)
- `document_type` (string, required): 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, required)
- `valid_from` (string): ISO date, e.g. 2026-08-01
- `valid_until` (string): ISO date, e.g. 2026-08-01

### `delete_document` (~24 tokens)

Delete one of the user's travel documents.

Input parameters:

- `document_id` (string, required)

### `list_visas` (~24 tokens)

Visas the user holds — type, number, validity, entries used.

### `create_visa` (~193 tokens)

Record a visa the user holds or has applied for.

Input parameters:

- `application_date` (string): ISO date, e.g. 2026-08-01
- `cost_currency` (string)
- `cost_paid` (number)
- `country_code` (string, required)
- `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, required): e.g. tourist, business, student, work, digital_nomad, transit

### `update_visa` (~175 tokens)

Change a recorded visa, or archive it by setting is_active to false.

Input parameters:

- `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, required)
- `visa_name` (string)
- `visa_number` (string)
- `visa_type` (string)

### `delete_visa` (~22 tokens)

Delete a recorded visa.

Input parameters:

- `visa_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-nomadpoint-nomadpoint/functions-v1-mcp#diagnostics

## Score history

- 2026-09-20: 90
- 2026-09-19: 90
- 2026-09-18: 90
- 2026-09-17: 89
- 2026-09-16: 89
- 2026-09-15: 88
- 2026-09-14: 88
- 2026-09-13: 85
- 2026-09-12: 84
- 2026-09-11: 84
- 2026-09-10: 84
- 2026-09-09: 83
- 2026-09-08: 83
- 2026-09-07: 82
- 2026-09-06: 82
- 2026-09-05: 81
- 2026-09-04: 81
- 2026-09-03: 81
- 2026-09-02: 80
- 2026-09-01: 80
- 2026-08-31: 79
- 2026-08-30: 79
- 2026-08-29: 78
- 2026-08-28: 78
- 2026-08-27: 77
- 2026-08-26: 77
- 2026-08-25: 74
- 2026-08-24: 74
- 2026-08-23: 73
- 2026-08-22: 73

## Common questions

### 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 90 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp
- Authorisation metadata: https://gxhdcvoveufbkthhendf.supabase.co/.well-known/oauth-protected-resource/functions/v1/mcp
- Repository: https://github.com/eladkishon/nomadpoint
- Website: https://nomadpoint.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-nomadpoint-nomadpoint/functions-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-nomadpoint-nomadpoint/functions-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-nomadpoint-nomadpoint/functions-v1-mcp