Overview
Covers about 200 passports and up to 235 destinations each, including territories with their own entry rules such as Hong Kong, Puerto Rico and Greenland. Pass countries as ISO 3166 two-letter codes or English names. Requirements are normalized to six categories so they compare across countries, and the allowed stay is given both as days and as the original wording, e.g. 90 days within any 180-day period. Data is checked weekly. Entry rules change, and conditions such as passport validity, onward tickets or purpose of travel still apply, so confirm with the destination's official source before booking.
Live Test Visa Requirements Source →
The tool
Once your client is connected to the VerveContext server, this appears in its tool list as VisaRequirements. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.
{
"name": "VisaRequirements",
"arguments": {
"passport": "US",
"destination": "JP"
}
}You do not name the tool yourself; the model picks it. Asking about US in the terms this source covers is enough for it to reach for VisaRequirements on its own — naming it explicitly also works, and is the way to force the call.
Connecting
One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp"
}
}
}https://api.vervecontext.com/v1/mcpPer-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.
Arguments
These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.
| Argument | Type | Description |
|---|---|---|
passportRequired | string | The passport's country: a two-letter ISO code such as US, or an English name such as United States length 0–60 |
destinationRequired | string | The destination country or territory: a two-letter ISO code such as JP, or an English name such as Japan length 0–60 |
What the model gets back
The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.
{
"status": "ok",
"error": null,
"data": {
"passport": "US",
"passportName": "United States",
"destination": "JP",
"destinationName": "Japan",
"requirement": "visa_free",
"requirementLabel": "Visa not required",
"visaRequiredInAdvance": false,
"allowedStayDays": 90,
"allowedStay": "90 days",
"updatedAt": "2026-10-22T09:00:00.000Z"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
passport | string | US | Passport country, ISO 3166 two-letter code |
passportName | string | United States | Passport country name |
destination | string | JP | Destination, ISO 3166 two-letter code |
destinationName | string | Japan | Destination name |
requirement | string | visa_free | visa_free, eta, evisa, visa_on_arrival, visa_required, restricted or unknown |
requirementLabel | string | Visa not required | Readable form of requirement, e.g. Visa not required |
visaRequiredInAdvance | boolean | false | Whether a visa must be obtained before travel; null when entry is restricted or unknown |
allowedStayDays | number | 90 | Allowed stay in days, or null when none is set or it is not a fixed number of days |
allowedStay | string | 90 days | Allowed stay as stated, e.g. 90 days or 3 months |
updatedAt | string | 2026-10-22T09:00:00.000Z | When this passport's requirements last changed in the dataset (ISO 8601) |
Why ground on it
A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.
Point an evaluation at passportName: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.
Failure modes
Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This source is not part of VerveContext. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 5 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- Travel Booking Checkout
- Booking sites warn travelers at checkout when their passport needs a visa or eVisa for the destination, before they pay for a non-refundable fare.
- Corporate Travel Approval
- Travel management tools flag trips where an employee's nationality needs a visa arranged weeks in advance, so the request goes to the visa team first.
- Trip Planning Apps
- Itinerary apps show the allowed stay next to each stop so a multi-country route stays within the visa-free days.
- Relocation and HR Tools
- Mobility platforms compare how many destinations each candidate's passport reaches without an advance visa when planning client visits.
Other ways to use Visa Requirements
Set up Visa Requirements on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.
Related
More in Transportation: