Skip to content

Viatsy MCP server

com.viatsy/mcpviatsy.comstreamable-httpv1.0.0Scanned

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

8 tools: 3 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 3 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 2
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Viatsy MCP server can do

The Viatsy MCP server is published by viatsy.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (3 tools: request_quote, subscribe_newsletter and start_checkout), but cannot delete data. 5 tools only read.

1 tool brings in text other people can write (list_blog_articles); 2 tools can send data out of your system (request_quote and start_checkout).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 3Claude Code: ask
  • request_quoteSubmit a quote request (inquiry) for a trip.Can send data outNo findings

    Why it is in this group

    • The name "request_quote" says "request": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.
  • start_checkoutCreate a booking and get a secure payment link the customer opens to pay — card details never pass through you.Can send data outNo findings

    Why it is in this group

    • The name "start_checkout" says "start": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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. Packages that include a flight cannot be booked here: their flight must be priced live on the website, so send the customer to the trip page or use request_quote instead.
  • subscribe_newsletterSubscribe the user to the travel newsletter.No findings

    Why it is in this group

    • The name "subscribe_newsletter" says "subscribe": a word for a change.
    Description, as the server wrote it
    Subscribe the user to the travel newsletter. Sends a confirmation email — the subscription activates only after the user clicks the link.
Only reads 5Show 5 read-only tools
  • get_trip_detailsGet full trip details: description, duration, highlights, what is included/excluded, and a short itinerary summary.No findings

    Why it is in this group

    • The name "get_trip_details" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_blog_articlesBrowse travel guides and articles.Reads text others writeNo findings

    Why it is in this group

    • The name "list_blog_articles" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Browse travel guides and articles. Returns published blog posts.
  • list_destinationsList all published destinations this agency operates in (countries and sub-destinations).No findings

    Why it is in this group

    • The name "list_destinations" says "list": a word for reading.
    Description, as the server wrote it
    List all published destinations this agency operates in (countries and sub-destinations).
  • list_upcoming_departuresFind open group-trip departures with future dates.No findings

    Why it is in this group

    • The name "list_upcoming_departures" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • search_tripsSearch published tours.No findings

    Why it is in this group

    • The name "search_trips" says "search": a word for reading.
    Description, as the server wrote it
    Search published tours. Filter by destination slug, free-text search, duration, or price. `priceFrom` is the cheapest "from" price per person; `bookable: false` marks an indicative price only (a group trip with no open departure yet — the traveller requests dates).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:49 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
404
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 404.

Posture changes

  1. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__viatsy__search_trips",
      "mcp__viatsy__list_destinations",
      "mcp__viatsy__get_trip_details",
      "mcp__viatsy__list_blog_articles",
      "mcp__viatsy__list_upcoming_departures"
    ],
    "ask": [
      "mcp__viatsy__request_quote",
      "mcp__viatsy__subscribe_newsletter",
      "mcp__viatsy__start_checkout"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as viatsy. Review it before you use it.

Capability tags behind 3 rules
  • mcp__viatsy__list_blog_articles untrusted-input
  • mcp__viatsy__request_quote outbound
  • mcp__viatsy__start_checkout outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.viatsy/mcp/verify?hash=02c87eaf8e51bedf84aa66aaf46e326e0fbac630392364e8206ef75efeb1fd51" | jq -e '.changed == false'

Pinned hash 02c87eaf8e51, from Oct 21, 2026, 18:37 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.viatsy/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.viatsy/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.viatsy/mcp.svg)](https://radar.anlyon.com/servers/com.viatsy/mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:10 UTC.

Viatsy MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Viatsy MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Viatsy MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Viatsy MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Viatsy MCP server have?

8 tools: 3 write, 5 read. request_quote, subscribe_newsletter, start_checkout, search_trips, list_destinations, get_trip_details, list_blog_articles and list_upcoming_departures.

Does the Viatsy MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Viatsy MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_quote and start_checkout.

Has the Viatsy MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.