quick_visa_check returns when the pair was last checked, so an answer carries its own freshness rather than sounding equally confident whether it is current or three years stale. It is keyless for the simple question and metered for everything past it, which makes it cheap to add before you know whether you need the rest.
An MCP server over the Orizn visa database. It answers entry questions with data rather than a guess: what a passport holder needs for a destination, what it costs, how long it takes, and whether they may leave the airport during a layover. Coverage figures are read live from the API rather than printed in the documentation.
- check_visa_requirement — the full entry picture for one passport into one destination: requirement type, days allowed, documents, application steps, fees, processing times, passport validity, photo specs, vaccinations, insurance, safety advisory, overstay penalties, entry by air, land or sea, remote-work visas, extension and minor rules, and embassies
- quick_visa_check — one line for a pair: the requirement code, visa-free days, and the date the pair was last verified
- compare_destinations — up to 25 destinations for one passport side by side, with requirement, visa-free days, passport validity, fee, safety, health and remote-work visa per row
- check_transit_visa — layover rules only: whether the holder may stay airside or leave the airport, and how many free transit hours the main hubs allow
- get_coverage_stats — the database's own coverage: pairs, passports, destinations, translations and languages, and the distribution of requirement types
Node.js 18 or newer; clients run npx -y orizn-visa-mcp over stdio. quick_visa_check works with no key at all, at 10 checks a day, alongside get_coverage_stats. A free key in ORIZN_API_KEY (or passed as --api-key, which takes precedence) lifts that cap and unlocks documents, fees, processing times, transit rules and the 15 languages.
One command plus a key — npx orizn-visa-mcp, then supply credentials