# Viatsy (remote · viatsy.com)

Search Asia travel tours, browse guides, request quotes, find upcoming group departures.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `viatsy.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-viatsy-mcp/viatsy.md), [page](https://verifymcp.io/servers/com-viatsy-mcp/viatsy)

## Channel facts

- Endpoint: `https://viatsy.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 930 tokens (~116/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-viatsy-mcp https://viatsy.com/mcp
```

### Codex

```toml
[mcp_servers.com-viatsy-mcp]
url = "https://viatsy.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-viatsy-mcp": {
      "type": "remote",
      "url": "https://viatsy.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-viatsy-mcp --url https://viatsy.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-viatsy-mcp:
    url: "https://viatsy.com/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (8)

### `search_trips` (~148 tokens)

Search published tours. Filter by destination slug, free-text search, duration, or price.

Input parameters:

- `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

### `list_destinations` (~57 tokens)

List all published destinations this agency operates in (countries and sub-destinations).

Input parameters:

- `cursor` (string): Opaque pagination cursor from a previous response
- `limit` (number): Page size (default 50, max 100)

### `get_trip_details` (~56 tokens)

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.

Input parameters:

- `slug` (string, required): Trip slug from search_trips results

### `list_blog_articles` (~52 tokens)

Browse travel guides and articles. Returns published blog posts.

Input parameters:

- `cursor` (string): Opaque pagination cursor from a previous response
- `limit` (number): Page size (default 20, max 50)

### `list_upcoming_departures` (~155 tokens)

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.

Input parameters:

- `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.

### `request_quote` (~121 tokens)

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.

Input parameters:

- `departureDate` (string): Preferred departure date (YYYY-MM-DD)
- `email` (string, required): Contact email address
- `message` (string, required): Free-text message (required)
- `name` (string, required): Traveller full name
- `phone` (string): Phone with country code
- `travellers` (number): Number of adult travellers
- `tripSlug` (string): Trip slug the quote is about

### `subscribe_newsletter` (~65 tokens)

Subscribe the user to the travel newsletter. Sends a confirmation email — the subscription activates only after the user clicks the link.

Input parameters:

- `email` (string, required): Email address to subscribe
- `language` (string): Preferred content language
- `name` (string): Subscriber name (optional)

### `start_checkout` (~276 tokens)

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.

Input parameters:

- `adults` (number, required): 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.
- `email` (string, required): 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, required): Lead traveller full name
- `phone` (string): Customer phone (optional)
- `startDate` (string): Private-trip start date (YYYY-MM-DD). Required when tripSlug is used.
- `tripSlug` (string): Trip slug for a private booking (from search_trips). Provide this OR departureId; requires startDate.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-viatsy-mcp/viatsy#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 67
- 2026-07-30: 66
- 2026-07-29: 67
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://viatsy.com/mcp
- Repository: https://github.com/albertsabatemartinez/viatsy
- Changelog RSS feed: https://verifymcp.io/servers/com-viatsy-mcp/viatsy/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-viatsy-mcp/viatsy/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-viatsy-mcp/viatsy