Nomads.com
REMOTE · NOMADS.COM
Find the best cities to live and work remotely: cost of living, internet, safety, weather and more.
Available components
Last scanned (20 hours ago)
Scores higher than 45% 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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_meetup). 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2768 tokens (~197/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 29 Oct 26 +1
- Tool “add_trip” rewrote its description, which is the text the model reads security
- Tool “create_meetup” rewrote its description, which is the text the model reads security
- Tool “edit_trip” rewrote its description, which is the text the model reads security
- Tool “get_favorites” rewrote its description, which is the text the model reads security
- Tool “get_trips” rewrote its description, which is the text the model reads security
- Tool “remove_trip” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “get_trips” added an optional parameter “from_date” cosmetic
- “get_trips” added an optional parameter “limit” cosmetic
- “get_trips” added an optional parameter “to_date” cosmetic
- “get_favorites” reworded the description of “username” cosmetic
- “add_favorite” reworded the description of “key” cosmetic
- “add_favorite” reworded the description of “username” cosmetic
- “add_trip” reworded the description of “key” cosmetic
- “add_trip” reworded the description of “username” cosmetic
- “cancel_meetup” reworded the description of “key” cosmetic
- “cancel_meetup” reworded the description of “username” cosmetic
- “create_meetup” reworded the description of “key” cosmetic
- “create_meetup” reworded the description of “username” cosmetic
- “edit_meetup” reworded the description of “key” cosmetic
- “edit_meetup” reworded the description of “username” cosmetic
- “edit_trip” reworded the description of “key” cosmetic
- “edit_trip” reworded the description of “username” cosmetic
- “get_favorites” reworded the description of “key” cosmetic
- “get_trips” reworded the description of “key” cosmetic
- “get_trips” reworded the description of “username” cosmetic
- “remove_favorite” reworded the description of “key” cosmetic
- “remove_favorite” reworded the description of “username” cosmetic
- “remove_trip” reworded the description of “key” cosmetic
- “remove_trip” reworded the description of “username” cosmetic
- 28 Oct 26 62
First indexed and scored.
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://nomads.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nomads.com | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9f74edf68af54a5c139f13c7142e20d6 |
| SANs: nomads.com, *.nomads.com | ||||||
| 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 secure
Validation of nomads.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nomads.com. | present | 2371 | 13 | Verified |
| nomads.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nomads.com/mcp | Verified | 200 | |
| http (plaintext) | http://nomads.com/mcp | HTTPS enforced | 301 | https://nomads.com/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_favorite ~120
Save a city or country to the member's Nomads.com favorites (the heart on the site). Authenticated as the member, like get_favorites.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| slug | string | yes | A city slug from search_cities (e.g. lisbon-portugal) or a country slug (e.g. portugal) |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
No output schema declared.
No examples provided.
add_trip ~365
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | The place name that was geocoded. Required (with country) for places that have no Nomads.com city within 5km |
| city_slug | string | – | From search_cities or get_city, e.g. lisbon-portugal. Omit if using latitude/longitude instead |
| country | string | – | The place's country name. Required with city for places without a Nomads.com city page |
| date_end | string | yes | YYYY-MM-DD, after date_start |
| date_start | string | yes | YYYY-MM-DD |
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| latitude | number | – | Use instead of city_slug when you only have a place name to geocode, not our slug |
| longitude | number | – | – |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
No output schema declared.
No examples provided.
cancel_meetup ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| meetup_id | string | – | From create_meetup, list_meetups, or this tool called without it |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
No output schema declared.
No examples provided.
create_meetup ~316
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Street address only, no links |
| category | string | yes | The main activity |
| city_slug | string | yes | From search_cities or get_city, e.g. lisbon-portugal |
| date | string | yes | YYYY-MM-DD, in the next 3 months |
| description | string | yes | What you will do. No paid tickets or selling |
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| recurrence | string | – | Optional: repeat every week (same weekday) or every month (same nth weekday) |
| time | string | yes | Local start time as a whole hour, e.g. 19 or 19:00 |
| title | string | – | Short title, max 60 characters |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
| venue | string | yes | Name of the cafe, bar or restaurant |
No output schema declared.
No examples provided.
edit_meetup ~282
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Street address only, no links |
| category | string | – | The main activity |
| date | string | – | YYYY-MM-DD |
| description | string | – | What you will do. No paid tickets or selling |
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| meetup_id | string | – | From create_meetup, list_meetups, or this tool called without it |
| time | string | – | Local start time as a whole hour, e.g. 19 or 19:00 |
| title | string | – | Short title, max 60 characters |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
| venue | string | – | Name of the cafe, bar or restaurant |
No output schema declared.
No examples provided.
edit_trip ~337
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).
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | With latitude/longitude: the place name. Required (with country) for places that have no Nomads.com city within 5km |
| city_slug | string | – | New place, from search_cities or get_city. Omit to keep the place |
| country | string | – | With city: the place's country name |
| date_end | string | – | New end date, YYYY-MM-DD. Omit to keep |
| date_start | string | – | New start date, YYYY-MM-DD. Omit to keep |
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| latitude | number | – | New place by coordinates, instead of city_slug |
| longitude | number | – | – |
| trip_id | string | yes | From get_trips |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
No output schema declared.
No examples provided.
get_city ~39
Get the curated data for one city by its slug (from search_cities), e.g. lisbon-portugal.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_country ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Lowercase country slug, e.g. portugal, united-kingdom |
No output schema declared.
No examples provided.
get_favorites ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
No output schema declared.
No examples provided.
get_trips ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Only trips that end on or after this date, YYYY-MM-DD |
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| limit | integer | – | How many trips, newest first: 1 to 1000, default 200 |
| to_date | string | – | Only trips that start on or before this date, YYYY-MM-DD |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
No output schema declared.
No examples provided.
list_meetups ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City slug from search_cities, e.g. lisbon-portugal |
| country | string | – | – |
| days_ahead | integer | – | How far ahead to look, 1 to 365, default 90 |
| limit | integer | – | 1 to 100, default 50 |
No output schema declared.
No examples provided.
remove_favorite ~110
Remove a city or country from the member's Nomads.com favorites. Authenticated as the member, like get_favorites.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| slug | string | yes | A city slug (e.g. lisbon-portugal) or a country slug (e.g. portugal) |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
No output schema declared.
No examples provided.
remove_trip ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| trip_id | string | yes | From get_trips |
| username | string | – | Omit when signed in through the connector (OAuth or Authorization header) |
No output schema declared.
No examples provided.
search_cities ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| limit | integer | – | 1 to 100 |
| max_cost_usd | integer | – | Max monthly cost for a nomad in USD (responses also carry expat, local, family, rent and coworking costs) |
| max_temperature_c | number | – | – |
| min_internet_mbps | number | – | – |
| min_safety | number | – | 0 to 5 |
| min_temperature_c | number | – | – |
| region | string | – | One of: Europe, Asia, North America, Latin America, Africa, Middle East, Oceania |
No output schema declared.
No examples provided.
How do I install the Nomads.com MCP server?
Nomads.com is a hosted endpoint at https://nomads.com/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 · nomads.com
claude mcp add --transport http com-nomads-mcp 'https://nomads.com/mcp'
What is the Nomads.com MCP server?
Nomads.com is an MCP server listed in the public MCP registry as com.nomads/mcp. Find the best cities to live and work remotely: cost of living, internet, safety, weather and more. This page covers its hosted endpoint (https://nomads.com/mcp).
Is the Nomads.com MCP server safe to use?
Nomads.com scores 65 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 Nomads.com MCP server expose?
Nomads.com exposes 14 tools: search_cities, list_meetups, create_meetup, edit_meetup, cancel_meetup, and 9 more. Their descriptions and schemas cost roughly 2,663 tokens of context every time the server is loaded.
Does the Nomads.com MCP server require authentication?
No. We connected to Nomads.com without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nomads.com MCP server still maintained?
Nomads.com 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.