# Nomads.com

> Find the best cities to live and work remotely: cost of living, internet, safety, weather and more.

- name: com.nomads/mcp
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 85/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.nomads%2Fmcp
- tools: https://api.protogrid.dev/v1/servers/com.nomads%2Fmcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "nomads": {
      "type": "http",
      "url": "https://nomads.com/mcp",
      "headers": {
        "Authorization": "Bearer ${NOMADS_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${NOMADS_TOKEN}`.

## Trust

- hygiene: 80
- liveness: 98
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-95% +updated-16d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 85/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2024-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 94 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 14 of 14 tools declare readOnlyHint or destructiveHint
- warn `tools.directory_hints`: 8 of 14 tools declare all four hints; missing: get_country (destructiveHint, idempotentHint); search_cities (destructiveHint, idempotentHint); list_meetups (destructiveHint, idempotentHint); …
- pass `tools.token_cost`: about 3,693 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: 83 (weight 15)

- warn `stability.changes`: 10 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name
- pass `stability.new_links`: no tool change named a new site

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 14, about 3,693 tokens to load them all
- tool set hash: eb744eda102049f8ac180730f255a6a9
- tools last changed: 2026-10-29T04:12:53.802Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.nomads/mcp.svg)](https://protogrid.dev/servers/com.nomads/mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-29 `edit_trip` changed (description, inputSchema)
  - before: Change the dates and/or the place of one trip in a Nomads.com member's own history, e.g. a stay that got longer or a wrong city. Authenticated as the member (connector Authorization header, or username + personal key from https://nomads.com/settings). Needs the trip_id (from get_trips); pass only what changes, everything else keeps its value. The trip keeps its trip_id, likes and comments. A new place works like add_trip: city_slug, OR latitude+longitude (snaps to a Nomads.com city within 5km, otherwise pass city and country names).
  - after: Change the dates and/or the place of one trip in a Nomads.com member's own history, e.g. a stay that got longer or a wrong city. Authenticated as the member (signed in through the connector with OAuth or an Authorization header, or username + personal key from https://nomads.com/settings). Needs the trip_id (from get_trips); pass only what changes, everything else keeps its value. The trip keeps its trip_id, likes and comments. A new place works like add_trip: city_slug, OR latitude+longitude (snaps to a Nomads.com city within 5km, otherwise pass city and country names).
- 2026-10-29 `remove_trip` changed (description, inputSchema)
  - before: Remove one trip from a Nomads.com member's own history, e.g. a duplicate or a superseded entry. Authenticated as the member (connector Authorization header, or username + personal key from https://nomads.com/settings). Needs the trip_id (returned by get_trips). Only the authenticated member's own trips can be removed.
  - after: Remove one trip from a Nomads.com member's own history, e.g. a duplicate or a superseded entry. Authenticated as the member (signed in through the connector with OAuth or an Authorization header, or username + personal key from https://nomads.com/settings). Needs the trip_id (returned by get_trips). Only the authenticated member's own trips can be removed.
- 2026-10-29 `add_trip` changed (description, inputSchema)
  - before: Add a trip to a Nomads.com member's own history: a stay in one place with a start and end date. Authenticated as the member: by the connector's Authorization header if set up, otherwise pass the member's username and their personal key from https://nomads.com/settings, plus the place, given EITHER as city_slug (from search_cities/get_city) OR as latitude+longitude (e.g. from a places/geocoding lookup). Coordinates within 5km of a Nomads.com city snap to it, same as the profile page's "add a trip" autocomplete; ANY other place also works - pass its city and country names with the coordinates and it is stored as-is, like the site's own trip editor.
  - after: Add a trip to a Nomads.com member's own history: a stay in one place with a start and end date. Authenticated as the member: signed in through the connector (OAuth sign-in or an Authorization header) if set up, otherwise pass the member's username and their personal key from https://nomads.com/settings, plus the place, given EITHER as city_slug (from search_cities/get_city) OR as latitude+longitude (e.g. from a places/geocoding lookup). Coordinates within 5km of a Nomads.com city snap to it, same as the profile page's "add a trip" autocomplete; ANY other place also works - pass its city and country names with the coordinates and it is stored as-is, like the site's own trip editor.
- 2026-10-29 `get_trips` changed (description, inputSchema)
  - before: Get a Nomads.com member's own trip history (past and upcoming stays: city, country, dates). Authenticated as the member: by the connector's Authorization header if set up, otherwise pass the member's username and their personal key from https://nomads.com/settings - this is private data, not for looking up other people.
  - after: Get a Nomads.com member's own trip history (past and upcoming stays: city, country, dates), newest first, 200 by default; use from_date/to_date for a period and limit for more. Authenticated as the member: signed in through the connector (OAuth sign-in or an Authorization header) if set up, otherwise pass the member's username and their personal key from https://nomads.com/settings - this is private data, not for looking up other people.
- 2026-10-29 `remove_favorite` changed (inputSchema)
- 2026-10-29 `add_favorite` changed (inputSchema)
- 2026-10-29 `get_favorites` changed (description, inputSchema)
  - before: Get a Nomads.com member's own favorite cities and countries (the places they hearted: places they want to go or come back to). Authenticated as the member: by the connector's Authorization header if set up, otherwise pass the member's username and their personal key from https://nomads.com/settings - this is private data, not for looking up other people.
  - after: Get a Nomads.com member's own favorite cities and countries (the places they hearted: places they want to go or come back to). Authenticated as the member: signed in through the connector (OAuth sign-in or an Authorization header) if set up, otherwise pass the member's username and their personal key from https://nomads.com/settings - this is private data, not for looking up other people.
- 2026-10-29 `cancel_meetup` changed (inputSchema)
- 2026-10-29 `edit_meetup` changed (inputSchema)
- 2026-10-29 `create_meetup` changed (description, inputSchema)
  - before: Host a Nomads.com meetup as the member: it is posted in the community chat, members in that city then get notified, and at 2 RSVPs it is also shared in the country channel and on X. Authenticated as the member (connector Authorization header, or username + personal key from https://nomads.com/settings). The member needs a profile photo and Telegram connected. Ask the member to confirm the details before calling this, it is posted publicly.
  - after: Host a Nomads.com meetup as the member: it is posted in the community chat, members in that city then get notified, and at 2 RSVPs it is also shared in the country channel and on X. Authenticated as the member (signed in through the connector with OAuth or an Authorization header, or username + personal key from https://nomads.com/settings). The member needs a profile photo and Telegram connected. Ask the member to confirm the details before calling this, it is posted publicly.

Full history: https://api.protogrid.dev/v1/servers/com.nomads%2Fmcp/changes

## Remotes

- https://nomads.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.953125)

## Packages

_none_

## Tools (14)

- `add_favorite`: Save a city or country to the member's Nomads.com favorites (the heart on the site). Authenticated as the member, like get_favorites.
- `add_trip`: Add a trip to a Nomads.com member's own history: a stay in one place with a start and end date. Authenticated as the member: signed in through the connector (OAuth sign-in or an Authorization header) if set up, otherwise pass the member's username and their personal key from https://nomads.com/settings, plus the place, given EITHER as city_slug (from search_cities/get_city) OR as latitude+longitude (e.g. from a places/geocoding lookup). Coordinates within 5km of a Nomads.com city snap to it, same as the profile page's "add a trip" autocomplete; ANY other place also works - pass its city and country names with the coordinates and it is stored as-is, like the site's own trip editor.
- `cancel_meetup`: Cancel a Nomads.com meetup the member organized. The cancel is posted in the community chat and everyone who RSVP'd gets a notification. It cannot be undone. Call without meetup_id to get the member's upcoming meetups with their ids. Authenticated as the member, like create_meetup. Ask the member to confirm first.
- `create_meetup`: Host a Nomads.com meetup as the member: it is posted in the community chat, members in that city then get notified, and at 2 RSVPs it is also shared in the country channel and on X. Authenticated as the member (signed in through the connector with OAuth or an Authorization header, or username + personal key from https://nomads.com/settings). The member needs a profile photo and Telegram connected. Ask the member to confirm the details before calling this, it is posted publicly.
- `edit_meetup`: Change a Nomads.com meetup the member organized: date, time, type, title, description, venue or address. Fields left out keep their current value. The change is posted in the community chat. Once 2+ people RSVP'd, the date and time can no longer change. Call without meetup_id to get the member's upcoming meetups with their ids. Authenticated as the member, like create_meetup. Ask the member to confirm the change first.
- `edit_trip`: Change the dates and/or the place of one trip in a Nomads.com member's own history, e.g. a stay that got longer or a wrong city. Authenticated as the member (signed in through the connector with OAuth or an Authorization header, or username + personal key from https://nomads.com/settings). Needs the trip_id (from get_trips); pass only what changes, everything else keeps its value. The trip keeps its trip_id, likes and comments. A new place works like add_trip: city_slug, OR latitude+longitude (snaps to a Nomads.com city within 5km, otherwise pass city and country names).
- `get_city`: Get the curated data for one city by its slug (from search_cities), e.g. lisbon-portugal.
- `get_country`: Get one country by its slug, e.g. portugal or united-kingdom: its Nomads.com page, its short animated thumbnail video (mp4, when there is one) and its top 10 cities by overall score, each with their own animated thumbnail.
- `get_favorites`: Get a Nomads.com member's own favorite cities and countries (the places they hearted: places they want to go or come back to). Authenticated as the member: signed in through the connector (OAuth sign-in or an Authorization header) if set up, otherwise pass the member's username and their personal key from https://nomads.com/settings - this is private data, not for looking up other people.
- `get_trips`: Get a Nomads.com member's own trip history (past and upcoming stays: city, country, dates), newest first, 200 by default; use from_date/to_date for a period and limit for more. Authenticated as the member: signed in through the connector (OAuth sign-in or an Authorization header) if set up, otherwise pass the member's username and their personal key from https://nomads.com/settings - this is private data, not for looking up other people.
- `list_meetups`: Upcoming Nomads.com meetups: where and when nomads meet in person, and how many people are going. Filter by city slug, country or how far ahead to look. Attendance is a count only; who attends is private.
- `remove_favorite`: Remove a city or country from the member's Nomads.com favorites. Authenticated as the member, like get_favorites.
- `remove_trip`: Remove one trip from a Nomads.com member's own history, e.g. a duplicate or a superseded entry. Authenticated as the member (signed in through the connector with OAuth or an Authorization header, or username + personal key from https://nomads.com/settings). Needs the trip_id (returned by get_trips). Only the authenticated member's own trips can be removed.
- `search_cities`: Search Nomads.com for the best cities to live and work remotely. Filters: budget, region, country, internet speed, safety, temperature. Returns at most 100 cities sorted by overall score. Each city includes costs, internet, weather, air quality, safety/cleanliness/healthcare/fun and other 0-5 scores, air conditioning (share of households, availability 1-5), tax burden (tax revenue as % of GDP) and an animated thumbnail video.