Viatsy
REMOTE · VIATSY.COM · SCANNED SEP 22
Search Asia travel tours, browse guides, request quotes, find upcoming group departures.
Available components
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 999 tokens (~124/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Viatsy MCP server?
Viatsy is a hosted endpoint at https://viatsy.com/mcp, 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.
remote · viatsy.com
claude mcp add --transport http com-viatsy-mcp 'https://viatsy.com/mcp'
{
"mcpServers": {
"com-viatsy-mcp": {
"url": "https://viatsy.com/mcp"
}
}
} {
"servers": {
"com-viatsy-mcp": {
"type": "http",
"url": "https://viatsy.com/mcp"
}
}
} [mcp_servers.com-viatsy-mcp] url = "https://viatsy.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-viatsy-mcp": {
"type": "remote",
"url": "https://viatsy.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-viatsy-mcp --url 'https://viatsy.com/mcp' --transport streamable-http
mcp_servers:
com-viatsy-mcp:
url: "https://viatsy.com/mcp" {
"McpServers": {
"com-viatsy-mcp": {
"Transport": "http",
"Url": "https://viatsy.com/mcp"
}
}
} assistant mcp add com-viatsy-mcp -t streamable-http -u 'https://viatsy.com/mcp'
{
"mcpServers": {
"com-viatsy-mcp": {
"type": "http",
"url": "https://viatsy.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Sept 26 0
- Stability: 0.97 → pass security
- 3 Sept 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Aug 26 0
- DNSSEC: unverified → pass ▲ security
- HTTPS: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.33 ▲ functional
- 4 Aug 26 0
- Stability: 0.27 → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- DNSSEC: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://viatsy.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=viatsy.com | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 780f510be437bbd00e59cf58a0de7f76 |
| SANs: viatsy.com, api.viatsy.com, *.api.viatsy.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of viatsy.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| viatsy.com. | present | 2371 | 13 | Verified |
| viatsy.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://viatsy.com/mcp | Verified | 200 | |
| http (plaintext) | http://viatsy.com/mcp | HTTPS enforced | 301 | https://viatsy.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_trip_details ~56
Get full trip details: description, duration, highlights, what is included/excluded, and a short itinerary summary. Use when the user asks about a specific trip.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Trip slug from search_trips results |
No output schema declared.
No examples provided.
list_blog_articles ~52
Browse travel guides and articles. Returns published blog posts.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response |
| limit | number | – | Page size (default 20, max 50) |
No output schema declared.
No examples provided.
list_destinations ~57
List all published destinations this agency operates in (countries and sub-destinations).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response |
| limit | number | – | Page size (default 50, max 100) |
No output schema declared.
No examples provided.
list_upcoming_departures ~155
Find open group-trip departures with future dates. Filter by destination slug, date range, or max price. Use when the user asks "when can I go to X?" or wants to compare dates.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response |
| destinationSlug | string | – | Destination slug — use list_destinations to get valid slugs |
| fromDate | string | – | Earliest departure date (YYYY-MM-DD). Defaults to today. |
| limit | number | – | Page size (default 20, max 50) |
| maxPrice | number | – | Max price per person (departure currency) |
| toDate | string | – | Latest departure date (YYYY-MM-DD). Optional. |
No output schema declared.
No examples provided.
request_quote ~121
Submit a quote request (inquiry) for a trip. Only use after the user has clearly asked for a quote and provided their name and email.
| Name | Type | Req | Description |
|---|---|---|---|
| departureDate | string | – | Preferred departure date (YYYY-MM-DD) |
| string | yes | Contact email address | |
| message | string | yes | Free-text message (required) |
| name | string | yes | Traveller full name |
| phone | string | – | Phone with country code |
| travellers | number | – | Number of adult travellers |
| tripSlug | string | – | Trip slug the quote is about |
No output schema declared.
No examples provided.
search_trips ~148
Search published tours. Filter by destination slug, free-text search, duration, or price.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response |
| destination | string | – | Destination slug — use list_destinations to get valid slugs |
| featured | boolean | – | – |
| limit | number | – | Page size (default 20, max 50) |
| maxDuration | number | – | Maximum duration in days |
| maxPrice | number | – | Maximum price per person |
| minDuration | number | – | Minimum duration in days |
| search | string | – | Free-text search over trip name, description, and destinations — matches any supported language, accent-insensitive |
No output schema declared.
No examples provided.
start_checkout ~309
Create a booking and get a secure payment link the customer opens to pay — card details never pass through you. Provide departureId for a group departure, or tripSlug + startDate for a private trip, plus the lead traveller name, email and traveller counts. Returns a bookingReference and paymentUrl; hand the paymentUrl to the customer to complete payment. Quote prices beforehand via get_trip_details or list_upcoming_departures — the payment page shows the authoritative total.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | number | yes | Number of adult travellers (1 or more) |
| children | number | – | Number of children (default 0) |
| departureId | string | – | Group-departure id (from list_upcoming_departures). Provide this OR tripSlug. |
| string | yes | Customer email — the payment link is tied to it | |
| infants | number | – | Number of infants (default 0) |
| locale | string | – | Preferred language for the payment page and confirmation |
| name | string | yes | Lead traveller full name |
| phone | string | – | Customer phone (optional) |
| startDate | string | – | Private-trip start date (YYYY-MM-DD). Required when tripSlug is used, and must then be at least 14 days out and no more than 18 months ahead. Ignored for departureId bookings — the departure row owns… |
| tripSlug | string | – | Trip slug for a private booking (from search_trips). Provide this OR departureId; requires startDate. |
No output schema declared.
No examples provided.
subscribe_newsletter ~65
Subscribe the user to the travel newsletter. Sends a confirmation email — the subscription activates only after the user clicks the link.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to subscribe | |
| language | string | – | Preferred content language |
| name | string | – | Subscriber name (optional) |
No output schema declared.
No examples provided.
What is the Viatsy MCP server?
Viatsy is an MCP server listed in the public MCP registry as com.viatsy/mcp. Search Asia travel tours, browse guides, request quotes, find upcoming group departures. This page covers its hosted endpoint (https://viatsy.com/mcp).
Is the Viatsy MCP server safe to use?
Viatsy scores 81 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 Viatsy MCP server expose?
Viatsy exposes 8 tools: search_trips, list_destinations, get_trip_details, list_blog_articles, list_upcoming_departures, and 3 more. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.
Does the Viatsy MCP server require authentication?
No. We connected to Viatsy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Viatsy MCP server still maintained?
Viatsy is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.