Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Nomads.com is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Find the best cities to live and work remotely: cost of living, internet, safety, weather and more.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nomads-com-mcp https://nomads.com/mcp
# 2 — ask your agent for something these tools do
# search_cities, list_meetups, create_meetup and 11 more
Nomads.com costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NOAll 1 server
nomads1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nomads-com-mcp https://nomads.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — some of its tools take a key of its publisher’s own, and the rest work without.
What it asks of you
Nothing is required, but it can take Authorization header (Optional. Only for the member tools (trips, favorites, meetups): Bearer <username>:<key>, with the personal key from https://nomads.com/settings. City search works without it.) if you want to set it. Its publisher says some of its tools need it, and the rest work without.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_cost_usd | integer | no | Max monthly cost for a nomad in USD (responses also carry expat, local, family, rent and coworking costs) |
| region | string | no | One of: Europe, Asia, North America, Latin America, Africa, Middle East, Oceania |
| country | string | no | — |
| min_internet_mbps | number | no | — |
| min_safety | number | no | 0 to 5 |
| min_temperature_c | number | no | — |
| max_temperature_c | number | no | — |
| limit | integer | no | 1 to 100 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | no | City slug from search_cities, e.g. lisbon-portugal |
| country | string | no | — |
| days_ahead | integer | no | How far ahead to look, 1 to 365, default 90 |
| limit | integer | no | 1 to 100, default 50 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| 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 |
| time | string | yes | Local start time as a whole hour, e.g. 19 or 19:00 |
| category | string | yes | The main activity |
| title | string | no | Short title, max 60 characters |
| description | string | yes | What you will do. No paid tickets or selling |
| venue | string | yes | Name of the cafe, bar or restaurant |
| address | string | yes | Street address only, no links |
| recurrence | string | no | Optional: repeat every week (same weekday) or every month (same nth weekday) |
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 con
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| meetup_id | string | no | From create_meetup, list_meetups, or this tool called without it |
| date | string | no | YYYY-MM-DD |
| time | string | no | Local start time as a whole hour, e.g. 19 or 19:00 |
| category | string | no | The main activity |
| title | string | no | Short title, max 60 characters |
| description | string | no | What you will do. No paid tickets or selling |
| venue | string | no | Name of the cafe, bar or restaurant |
| address | string | no | Street address only, no links |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| meetup_id | string | no | From create_meetup, list_meetups, or this tool called without it |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Lowercase country slug, e.g. portugal, united-kingdom |
Get the curated data for one city by its slug (from search_cities), e.g. lisbon-portugal.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
Save a city or country to the member's Nomads.com favorites (the heart on the site). Authenticated as the member, like get_favorites.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | 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) |
Remove a city or country from the member's Nomads.com favorites. Authenticated as the member, like get_favorites.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | 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) |
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 priva
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| from_date | string | no | Only trips that end on or after this date, YYYY-MM-DD |
| to_date | string | no | Only trips that start on or before this date, YYYY-MM-DD |
| limit | integer | no | How many trips, newest first: 1 to 1000, default 200 |
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+longitud
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| city_slug | string | no | From search_cities or get_city, e.g. lisbon-portugal. Omit if using latitude/longitude instead |
| latitude | number | no | Use instead of city_slug when you only have a place name to geocode, not our slug |
| longitude | number | no | — |
| city | string | no | The place name that was geocoded. Required (with country) for places that have no Nomads.com city within 5km |
| country | string | no | The place's country name. Required with city for places without a Nomads.com city page |
| date_start | string | yes | YYYY-MM-DD |
| date_end | string | yes | YYYY-MM-DD, after date_start |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| trip_id | string | yes | From get_trips |
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| username | string | no | Omit when signed in through the connector (OAuth or Authorization header) |
| key | string | no | From https://nomads.com/settings. Omit when signed in through the connector (OAuth or Authorization header) |
| trip_id | string | yes | From get_trips |
| date_start | string | no | New start date, YYYY-MM-DD. Omit to keep |
| date_end | string | no | New end date, YYYY-MM-DD. Omit to keep |
| city_slug | string | no | New place, from search_cities or get_city. Omit to keep the place |
| latitude | number | no | New place by coordinates, instead of city_slug |
| longitude | number | no | — |
| city | string | no | With latitude/longitude: the place name. Required (with country) for places that have no Nomads.com city within 5km |
| country | string | no | With city: the place's country name |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Nomads.com or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest14feb24685dd502c6405e5ac7235af73c241b7c81f4758b796906dd8b494fcd3
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_cities | no tags | |
| list_meetups | no tags | |
| create_meetup | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| edit_meetup | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| cancel_meetup | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_country | no tags | |
| get_city | no tags | |
| get_favorites | no tags | |
| add_favorite | state-write | state-write: declares readOnlyHint: false |
| remove_favorite | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_trips | no tags | |
| add_trip | state-write | state-write: declares readOnlyHint: false |
| remove_trip | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| edit_trip | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest14feb24685dd502c
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Nomads.com can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.