← Registry

API Tools

vistalink.com

An MCP server that searches the VistaLink hotel catalogue, supports conversational hotel comparisons, and retrieves detailed hotel profiles.

1 endpoint3 known toolsFirst detected October 3, 2026Last detected October 3, 2026

ENDPOINT 1

https://api.vistalink.com/mcp

No auth detected

MCP server metadata

Name
VistaLink Hotels
Version
1.30.0
Capabilities
experimentalpromptsresourcestools
Server instructions

Hotel search over the VistaLink catalogue. search_hotels finds hotels by city or coordinates with optional dates, budget, amenities and vibe; get_hotel_details returns one hotel's full profile. Both work without an API key (per-IP rate limit; prices only for given dates, from cache). chat_about_hotels answers natural-language hotel questions and requires signing in with a Parley account (OAuth) or an API key from https://vistalink.com/developers, sent as 'Authorization: Bearer <key>'.

Known tools 3

search_hotels

Search the VistaLink hotel catalogue in one city (or around a point).

Inferred read-only
chat_about_hotels

Conversational hotel search for natural-language requests, comparisons and subjective preferences.

Inferred read-only
get_hotel_details

Full profile of one hotel by its hotel_id from search_hotels: description, amenities, images, rooms, guest reviews and guest insights.

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.vistalink-hotels]
url = "https://api.vistalink.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "vistalink-hotels": {
      "type": "http",
      "url": "https://api.vistalink.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: vistalink-hotels
Remote MCP URL: https://api.vistalink.com/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": {
    "vistalink-hotels": {
      "url": "https://api.vistalink.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "vistalink-hotels": {
      "type": "http",
      "url": "https://api.vistalink.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "vistalink-hotels",
  "transport": "streamable-http",
  "url": "https://api.vistalink.com/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.