# app.nomadpoint/travel-facts (remote · nomadpoint.app)

No-auth: save a planned trip as a claimable itinerary, visa rules per passport, Schengen 90/180

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `nomadpoint.app`: 75/100 (this document), [markdown](https://verifymcp.io/servers/app-nomadpoint-travel-facts/mcp-public.md), [page](https://verifymcp.io/servers/app-nomadpoint-travel-facts/mcp-public)

## Channel facts

- Endpoint: `https://nomadpoint.app/mcp-public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.2`

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

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 582 tokens (~194/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

## Install

### How do I install the app.nomadpoint/travel-facts MCP server?

app.nomadpoint/travel-facts is a hosted endpoint at https://nomadpoint.app/mcp-public, 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-travel-facts 'https://nomadpoint.app/mcp-public'
```

### Cursor

```json
{
  "mcpServers": {
    "app-nomadpoint-travel-facts": {
      "url": "https://nomadpoint.app/mcp-public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-nomadpoint-travel-facts": {
      "type": "http",
      "url": "https://nomadpoint.app/mcp-public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-nomadpoint-travel-facts]
url = "https://nomadpoint.app/mcp-public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-nomadpoint-travel-facts": {
      "type": "remote",
      "url": "https://nomadpoint.app/mcp-public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-nomadpoint-travel-facts --url 'https://nomadpoint.app/mcp-public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-nomadpoint-travel-facts:
    url: "https://nomadpoint.app/mcp-public"
```

### Netclaw

```json
{
  "McpServers": {
    "app-nomadpoint-travel-facts": {
      "Transport": "http",
      "Url": "https://nomadpoint.app/mcp-public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-nomadpoint-travel-facts -t streamable-http -u 'https://nomadpoint.app/mcp-public'
```

### Other

```json
{
  "mcpServers": {
    "app-nomadpoint-travel-facts": {
      "type": "http",
      "url": "https://nomadpoint.app/mcp-public"
    }
  }
}
```

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-11-21 (score 75, +1)

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

### 2026-11-19 (score 74, +1)

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

### 2026-11-17 (score 73, +1)

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

### 2026-11-15 (score 72, +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.

### 2026-11-12 (score 71, +1)

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

### 2026-11-11 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 70)

First indexed and scored.

## MCP tools (3)

### `check_visa_requirement` (~149 tokens)

Check visa requirement

Use this when someone asks whether they need a visa to visit a country, or how long they can stay, for a specific passport. Returns the entry type (visa free, visa on arrival, e-visa, visa required) and the permitted stay in days when known. Do not use it for work, study or residence permits; it covers short tourist stays only.

Input parameters:

- `destination` (string, required): The country being visited as an ISO 3166-1 alpha-2 code, e.g. US, GB, TH
- `passport` (string, required): The passport's issuing country as an ISO 3166-1 alpha-2 code, e.g. US, GB, TH

### `calculate_schengen_days` (~138 tokens)

Calculate Schengen days

Use this when someone wants to know how many days they have used or have left in the Schengen Area under the 90/180 rule, or whether a planned trip would overstay. Pass every stay in any Schengen country with entry and exit dates. Do not use it for countries outside the Schengen Area, or for holders of an EU/EEA/Swiss passport, to whom the rule does not apply.

Input parameters:

- `as_of` (string): Date to assess on, YYYY-MM-DD. Defaults to today.
- `stays` (array, required): Each stay in the Schengen Area. Past and planned stays can be mixed.

### `create_trip_plan` (~154 tokens)

Save a trip plan

Use this after you have planned a trip with someone, to hand them the itinerary as a real, editable plan instead of a wall of text. No account or key needed. Pass the stops in order with arrival and departure dates, and optionally things to do in each. Returns plan_url: the traveller opens it to see the route and save it to their own NomadPoint on iPhone, Mac or web (free). Give the traveller that link. Do not use it for bookings: it records a plan, it does not reserve anything.

Input parameters:

- `name` (string, required): What the traveller would call it, e.g. 'Japan in April'
- `stops` (array, required): Each city on the route, in order.

## Diagnostics

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

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 71
- 2026-11-11: 70
- 2026-11-10: 70

## Common questions

### What is the app.nomadpoint/travel-facts MCP server?

app.nomadpoint/travel-facts is an MCP server listed in the public MCP registry as app.nomadpoint/travel-facts. No-auth: save a planned trip as a claimable itinerary, visa rules per passport, Schengen 90/180. This page covers its hosted endpoint (https://nomadpoint.app/mcp-public).

### Is the app.nomadpoint/travel-facts MCP server safe to use?

app.nomadpoint/travel-facts scores 75 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/travel-facts MCP server expose?

app.nomadpoint/travel-facts exposes 3 tools: check_visa_requirement, calculate_schengen_days, create_trip_plan. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.

### Does the app.nomadpoint/travel-facts MCP server require authentication?

No. We connected to app.nomadpoint/travel-facts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the app.nomadpoint/travel-facts MCP server still maintained?

app.nomadpoint/travel-facts is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the app.nomadpoint/travel-facts MCP server?

VerifyMCP ran 13 checks on app.nomadpoint/travel-facts, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://nomadpoint.app/mcp-public
- Repository: https://github.com/eladkishon/nomadpoint-skills
- Website: https://nomadpoint.app/schengen-calculator
- Changelog RSS feed: https://verifymcp.io/servers/app-nomadpoint-travel-facts/mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-nomadpoint-travel-facts/mcp-public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-nomadpoint-travel-facts/mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/app-nomadpoint-travel-facts/mcp-public
