Entry rules, long stay routes and settlement answers for 21 Asian countries.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
What a given passport gets at the border of an Asian destination: visa category, days on entry, whether it extends, and the instrument that grants it. Answers from 1,584 sourced rules.
Passport country, ISO two letter code or name, for example "gb", "GB", "United Kingdom"
Destination country name or slug, for example "Thailand"
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http mcp https://stayingasia.com/api/mcp/
What a given passport gets at the border of an Asian destination: visa category, days on entry, whether it extends, and the instrument that grants it. Answers from 1,584 sourced rules.
| Argument | Type | Description |
|---|---|---|
| passport* | string | Passport country, ISO two letter code or name, for example "gb", "GB", "United Kingdom" |
| destination | string | Destination country name or slug, for example "Thailand" |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"passport"
],
"properties": {
"passport": {
"type": "string",
"description": "Passport country, ISO two letter code or name, for example \"gb\", \"GB\", \"United Kingdom\""
},
"destination": {
"type": "string",
"description": "Destination country name or slug, for example \"Thailand\""
}
}
}Whether long stay in a country leads anywhere, plus the hub summary, route count and link to the full record.
| Argument | Type | Description |
|---|---|---|
| country* | string | Country name or slug, for example "Thailand" or "hong-kong" |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"country"
],
"properties": {
"country": {
"type": "string",
"description": "Country name or slug, for example \"Thailand\" or \"hong-kong\""
}
}
}Locate the long form guide for a question, for example "DTV bank balance", "Japan PR points", "MM2H property".
| Argument | Type | Description |
|---|---|---|
| query | string | Free text, for example "LTR tax" |
| country | string | Restrict to one country |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"query": {
"type": "string",
"description": "Free text, for example \"LTR tax\""
},
"country": {
"type": "string",
"description": "Restrict to one country"
}
}
}The long stay instruments for one country, or across all countries filtered by family: remote-work, retirement, investment, skilled, business, family.
| Argument | Type | Description |
|---|---|---|
| family | string | Filter by route family, for example "remote-work" or "retirement" |
| country | string | Country name or slug, omit for every country |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"family": {
"type": "string",
"description": "Filter by route family, for example \"remote-work\" or \"retirement\""
},
"country": {
"type": "string",
"description": "Country name or slug, omit for every country"
}
}
}Search guides, programmes and country records. Use when the question does not fit the other tools.
| Argument | Type | Description |
|---|---|---|
| query* | string | Free text, for example "digital nomad visa minimum income" |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Free text, for example \"digital nomad visa minimum income\""
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 2, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.