Content Tools

viaive.com

Provides travel destination guides, hotel details, and curated travel content.

1 endpoint7 known toolsFirst detected July 24, 2026Last detected September 5, 2026

ENDPOINT 1

https://viaive.com/api/mcp

No auth detected

MCP server metadata

Name: viaive
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

VIAIVE is a private, quiet-luxury travel advisory (deepest coverage in East and Southeast Asia). These tools expose the same editorial judgment published on viaive.com — destination reads, hotel/villa/experience/cruise verdicts, {intent}×{city} field guides, and live travel signals. VIAIVE does not sell direct: every booking link routes through a disclosed Stay22 affiliate path (disclosure text is returned inline with every link — always surface it if you relay a link to a person). Start with list_destinations, search_stays, or list_field_guides to discover valid identifiers before calling a detail tool — do not guess slugs.

Known tools 7

list_destinations

List every VIAIVE-covered destination (city or country) with region, best travel months, and lead time.

Inferred read-only

get_destination_guide

Full VIAIVE advisory read for one destination: the geo answer (who it's for), the current hotel shortlist, 2026 openings/refurbishments/watch items, and editorial sections.

Inferred read-only

search_stays

Search VIAIVE hotel, villa, experience, and cruise placements for one destination.

Inferred read-only

get_stay_detail

Full VIAIVE decision detail for one hotel, villa, experience, or cruise: who it's for, who should avoid it, the editorial verdict, methodology, and a disclosed availability-check link.

Inferred read-only

list_field_guides

List every live VIAIVE field guide in the {intent}×{city} matrix (e.g.

Inferred read-only

get_field_guide

Full VIAIVE field guide for one {intent}×{city} pair (e.g.

Inferred read-only

get_live_signals

Current VIAIVE travel signals — opening windows, booking-window changes, seasonal compressions — each with a confidence score, freshness window, and sources.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.viaive]
url = "https://viaive.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "viaive": {
      "type": "http",
      "url": "https://viaive.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: viaive
Remote MCP URL: https://viaive.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "viaive": {
      "url": "https://viaive.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "viaive": {
      "type": "http",
      "url": "https://viaive.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "viaive",
  "transport": "streamable-http",
  "url": "https://viaive.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.