VistaLink Hotels
REMOTE · API.VISTALINK.COM · SCANNED OCT 2
Search 650,000 hotels by place, vibe, photos and reviews. Search needs no key.
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1301 tokens (~260/item across 5 items; 3 tools + 2 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the VistaLink Hotels MCP server?
VistaLink Hotels is a hosted endpoint at https://api.vistalink.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 · api.vistalink.com
claude mcp add --transport http com-vistalink-hotels 'https://api.vistalink.com/mcp'
{
"mcpServers": {
"com-vistalink-hotels": {
"url": "https://api.vistalink.com/mcp"
}
}
} {
"servers": {
"com-vistalink-hotels": {
"type": "http",
"url": "https://api.vistalink.com/mcp"
}
}
} [mcp_servers.com-vistalink-hotels] url = "https://api.vistalink.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-vistalink-hotels": {
"type": "remote",
"url": "https://api.vistalink.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-vistalink-hotels --url 'https://api.vistalink.com/mcp' --transport streamable-http
mcp_servers:
com-vistalink-hotels:
url: "https://api.vistalink.com/mcp" {
"McpServers": {
"com-vistalink-hotels": {
"Transport": "http",
"Url": "https://api.vistalink.com/mcp"
}
}
} assistant mcp add com-vistalink-hotels -t streamable-http -u 'https://api.vistalink.com/mcp'
{
"mcpServers": {
"com-vistalink-hotels": {
"type": "http",
"url": "https://api.vistalink.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.
- 2 Oct 26 80
First indexed and scored.
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 2 Oct 2026 · Probed https://api.vistalink.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vistalink.com | CN=WE1,O=Google Trust Services,C=US | 12 Aug 2026 | 10 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 888aa1527a35a8b00e366eb7c0cff29c |
| SANs: vistalink.com, *.vistalink.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 insecure
Validation of api.vistalink.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| vistalink.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="vistalink", error_uri="https://vistalink.com/developers", resource_metadata="https://api.vistalink.com/.well-known/oauth-protected-resource/mcp", scope="hotels:read chat"
Bearer realm="vistalink", error_uri="https://vistalink.com/developers", resource_metadata="https://api.vistalink.com/.well-known/oauth-protected-resource/mcp", scope="hotels:read chat" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(self), microphone=(), camera=() |
Protected resource metadata
| Document | https://api.vistalink.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.vistalink.com/mcp |
| Authorisation server | https://meetparley.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.vistalink.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.vistalink.com/mcp | HTTPS enforced | 301 | https://api.vistalink.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 →
chat_about_hotels Chat about hotels ~349
Conversational hotel search for natural-language requests, comparisons and subjective preferences. Slower than search_hotels. Requires signing in (a linked Parley account) or an API key. Guest context (travel style, purpose, accessibility needs, loyalty programs, dietary needs) can be passed in the context parameter as a JSON object. Clarifications: if a previous response included a ``clarification_pending`` payload, show the question to the user and either pass ``clarification_id`` + ``clarification_option_id`` for the chosen option, or pass the user's free-text answer in ``message`` and leave the clarification params empty. Args: message: The user's message or question session_id: Session id from a previous response to continue the conversation (empty for a new session) currency: Currency code for prices (default EUR) context: JSON object with guest context (empty to skip). Example: {"travel_style": "luxury", "purpose": "honeymoon", "accessibility": "wheelchair", "loyalty_programs": ["Marriott Bonvoy"], "dietary": "vegetarian"} clarification_id: When replying to a prior clarification, the id from ``clarification_pending.clarification_id`` in that response. clarification_option_id: When replying to a prior clarification, the id of the option the user selected.
| Name | Type | Req | Description |
|---|---|---|---|
| clarification_id | string | – | – |
| clarification_option_id | string | – | – |
| context | string | – | – |
| currency | string | – | – |
| message | string | yes | – |
| session_id | string | – | – |
No output schema declared.
No examples provided.
get_hotel_details Get hotel details ~218
Full profile of one hotel by its hotel_id from search_hotels: description, amenities, images, rooms, guest reviews and guest insights. A price is included only when both check_in and check_out are given, as the all-inclusive total for that stay. Works without an API key (cached prices only).
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | string | – | Check-in date, YYYY-MM-DD (today or later). Prices need check_in and check_out. |
| check_out | string | – | Check-out date, YYYY-MM-DD, after check_in. |
| currency | string | – | ISO 4217 currency code for prices, e.g. 'EUR', 'USD', 'GBP'. |
| guests | integer | – | Number of adult guests (0 = default of 2). |
| hotel_id | string | yes | The hotel's id (a UUID), as returned in hotel_id by search_hotels. |
| rooms | integer | – | Number of rooms (0 = 1). Prices are only quoted for one room. |
No output schema declared.
No examples provided.
search_hotels Search hotels ~559
Search the VistaLink hotel catalogue in one city (or around a point). Needs city, latitude+longitude, or hotel_name; describe the stay in vibe. Returns hotels with ratings, location, amenities, images and guest-review insights. A price appears only when both check_in and check_out are given (the all-inclusive total for that stay). Works without an API key (at most 20 results, cached prices only). For open-ended questions use chat_about_hotels.
| Name | Type | Req | Description |
|---|---|---|---|
| amenities | string | – | Comma-separated amenities the hotel must have, e.g. 'wifi,pool'. |
| budget_max | number | – | Maximum price per night, in currency (0 = no maximum). |
| budget_min | number | – | Minimum price per night, in currency (0 = no minimum). |
| check_in | string | – | Check-in date, YYYY-MM-DD (today or later). Prices need check_in and check_out. |
| check_out | string | – | Check-out date, YYYY-MM-DD, after check_in. |
| city | string | – | City to search in, e.g. 'Lisbon'. A search needs city, latitude+longitude, or hotel_name. |
| country | string | – | ISO 3166-1 alpha-2 country code of the city, e.g. 'PT'. Use it for city names that exist in several countries (Paris FR vs Paris US). |
| currency | string | – | ISO 4217 currency code for prices, e.g. 'EUR', 'USD', 'GBP'. |
| guests | integer | – | Number of adult guests (0 = default of 2). |
| hotel_name | string | – | Hotel name or part of it, e.g. 'Four Seasons'. |
| include_rates | boolean | – | Fetch live rates for check_in/check_out (adds about 30-45s). Needs an API key and both dates; ignored otherwise. |
| latitude | number | – | Search centre latitude in decimal degrees, used with longitude (0 = not set). |
| limit | integer | – | Maximum number of results, 1-20 without an API key (1-50 with one). Larger values are reduced to the maximum. |
| longitude | number | – | Search centre longitude in decimal degrees, used with latitude (0 = not set). |
| radius_meters | integer | – | Radius around latitude/longitude in metres (0 = default). |
| rooms | integer | – | Number of rooms (0 = 1). Prices are only quoted for one room. |
| vibe | string | – | What the traveller is looking for, as free text or comma-separated tags, e.g. 'boutique design hotel' or 'romantic,quiet'. |
No output schema declared.
No examples provided.
What is the VistaLink Hotels MCP server?
VistaLink Hotels is an MCP server listed in the public MCP registry as com.vistalink/hotels. Search 650,000 hotels by place, vibe, photos and reviews. Search needs no key. This page covers its hosted endpoint (https://api.vistalink.com/mcp).
Is the VistaLink Hotels MCP server safe to use?
VistaLink Hotels scores 80 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 VistaLink Hotels MCP server expose?
VistaLink Hotels exposes 3 tools: search_hotels, chat_about_hotels, get_hotel_details. Their descriptions and schemas cost roughly 1,126 tokens of context every time the server is loaded.
Does the VistaLink Hotels MCP server require authentication?
Yes. VistaLink Hotels asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the VistaLink Hotels MCP server still maintained?
VistaLink Hotels is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.