Travel Facts

app.nomadpointPublished by nomadpoint.appv1.1.1Updated Nov 1, 2026

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

The publisher's own server: travel.art

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

No-auth remote MCP server that answers visa entry rules, Schengen 90/180 day counts, and turns a planned route into a claimable itinerary link.

What you can do
  • Check visa requirements for a passport and destination, returning entry type and permitted stay in days
  • Calculate days used and remaining in the Schengen Area under the 90/180 rule, including overstay checks for planned trips
  • Create a trip plan from ordered stops with arrival and departure dates, returning a link the traveller can open to save the itinerary
When to use it
Useful when an assistant helps with travel planning: answering visa questions, checking whether a multi-country Europe trip would overstay the Schengen limit, or handing over a finished itinerary as an editable plan instead of plain text.
Requirements
A remote streamable HTTP endpoint; no account, API key or environment variables are needed for the three tools. Network access to the provider's endpoint is required.
Before you install
Visa and stay data is informational and entry rules change, so the destination's official source should be confirmed before travelling. Coverage is limited to short tourist stays, not work, study or residence permits. create_trip_plan produces a shareable plan link, so check what the itinerary reveals before handing it out.

Installation

In SourceWeft

  1. Open Travel Facts in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.nomadpoint%2Ftravel-facts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "travel-facts": {
      "type": "http",
      "url": "https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/mcp-public"
    }
  }
}

README

NomadPoint skill

An agent skill that teaches Claude (and other agents) how to use the NomadPoint MCP server to read and edit your trips — journeys, stays, flights, accommodations, activities, and visa/country info.

Install

bash
npx skills add eladkishon/nomadpoint-skills

This installs the skill into .claude/skills/ (add --global for ~/.claude/skills).

Connect the MCP

The skill uses the NomadPoint MCP server. In the NomadPoint app → Settings → Integrations → Claude / MCP, tap Copy prompt for Claude and paste it into Claude — it adds the MCP server (with your personal token) and installs this skill.

The MCP endpoint is an HTTP server authenticated with a per-user Bearer np_mcp_… token. No secrets live in this skill.

What it covers

  • Reading trips: list_journeys, get_journey, get_country_info
  • Creating: create_stay, create_flight, create_accommodation, create_activity
  • Editing/removing: update_* / delete_* for each

See SKILL.md for the full guidance.

Travel API (no key)

Plain JSON over HTTPS, CORS open, no account or key.

GET https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/travel-api/visa?passport=US&destination=THGET https://gxhdcvoveufbkthhendf.supabase.co/functions/v1/travel-api/schengen?stays=2026-01-05..2026-01-20,2026-03-01..2026-03-14&as_of=2026-04-01
  • visa: entry type (visa free, visa on arrival, e-visa, visa required) and the allowed stay in days for a passport and destination, both ISO 3166-1 alpha-2. Covers 39,601 pairs, with source and the date checked. Short tourist stays only.
  • schengen: days used and left under the 90/180 rule, the date you have to be out by, and the next date a full stay opens again. stays is a comma-separated list of entry..exit dates. Entry and exit days both count, and the window covers the whole Schengen Area, not each country separately. as_of defaults to today.

The same answers are available as a no-auth MCP server, app.nomadpoint/travel-facts in the official MCP registry, which can also save a planned route as an itinerary (create_trip_plan). Entry rules change, so confirm with the destination's official source before travelling.

Source: README.md at commit 3c804ae

Tools

3

check_visa_requirement

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.

Parameterspassportrequireddestinationrequired

calculate_schengen_days

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.

Parametersas_ofstaysrequired

create_trip_plan

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.

Parametersnamerequiredstopsrequired

Version history

1
  1. v1.1.1LatestOct 18, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Travel integrations