# Travellers Group — Regional Australia Hotels (remote · agent.travellersgroup.com.au)

Verified facts and direct-booking handoff for five Travellers Group hotels in regional Australia.

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

## Components

- remote · `agent.travellersgroup.com.au`: 65/100 (this document), [markdown](https://verifymcp.io/servers/au-com-travellersgroup-agent/v1-mcp.md), [page](https://verifymcp.io/servers/au-com-travellersgroup-agent/v1-mcp)

## Channel facts

- Endpoint: `https://agent.travellersgroup.com.au/v1/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**: 63/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 10 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 check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 881 tokens (~73/item across 12 items; 12 tools + 0 resources), lean.
  - 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**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 22% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http au-com-travellersgroup-agent https://agent.travellersgroup.com.au/v1/mcp
```

### Codex

```toml
[mcp_servers.au-com-travellersgroup-agent]
url = "https://agent.travellersgroup.com.au/v1/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add au-com-travellersgroup-agent --url https://agent.travellersgroup.com.au/v1/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  au-com-travellersgroup-agent:
    url: "https://agent.travellersgroup.com.au/v1/mcp"
```

### Other

```json
{
  "mcpServers": {
    "au-com-travellersgroup-agent": {
      "type": "http",
      "url": "https://agent.travellersgroup.com.au/v1/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 65, +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 64, +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 63, +2)

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

### 2026-07-30 (score 61, +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 60, +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 59, +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 58)

First indexed and scored.

## MCP tools (12)

### `search_content` (~92 tokens)

Search the published six-site Travellers Group corpus (guides, hubs, FAQs, pages). Returns ranked answer capsules (≤120 words) with canonical URLs.

Input parameters:

- `property` (string)
- `query` (string, required): What the traveller wants to know, in their own words
- `town` (string): Bundaberg | Rockhampton | Emerald | Orange | Dubbo
- `type` (string)

### `get_property` (~41 tokens)

Canonical entity record for a Travellers Group property: address, contacts, quick facts, policies, booking URL, parent entity.

Input parameters:

- `property` (string, required)

### `get_room_types` (~79 tokens)

Room catalogue for a property: occupancy, bedding, amenities, who-it-suits, booking deep link per room. traveller_context re-ranks honestly — it never invents inclusions.

Input parameters:

- `property` (string, required)
- `traveller_context` (string): e.g. 'crew of 4, weekly' or 'couple, wine weekend'

### `get_distances` (~73 tokens)

Measured distances from a property (km, drive/walk minutes) to hospitals, mines, airports, venues, wineries. Fuzzy destination filter ('the zoo', 'hospital'). Serves published measured figures only.

Input parameters:

- `destination` (string)
- `property` (string)
- `town` (string)

### `get_events` (~53 tokens)

Verified events for a town. Serves only entries published with explicit dates — never extrapolates a date.

Input parameters:

- `from_date` (string)
- `to_date` (string)
- `town` (string, required)

### `get_town_guide` (~66 tokens)

Town knowledge layer: open-late, essentials, eat, with-kids, working-in, hospital-visitor, itineraries. Unbuilt topic returns 'not yet published' plus the town guide root.

Input parameters:

- `topic` (string, required)
- `town` (string, required)

### `get_indicative_rates` (~73 tokens)

Indicative rate ranges from the published, commercially-signed rate module only — framed as indicative, never a quote. Where no figure is published, returns the booking link instead (never an estimate).

Input parameters:

- `property` (string, required)
- `room_type` (string)
- `stay_band` (string)

### `recommend_property` (~90 tokens)

Honest matching across the Travellers portfolio. If no Travellers property suits the need, says so plainly and names the accommodation category that does. Never oversells. [Templates DRAFT pending G1.]

Input parameters:

- `context` (string)
- `need` (string): e.g. 'towing a caravan', 'pet friendly', 'crew of 6 near the hospital'
- `town` (string)

### `check_availability` (~85 tokens)

Tier A handoff: returns a dated, pre-filled booking-engine link — LIVE availability and pricing are at that link. This tool never asserts that dates are available.

Input parameters:

- `adults` (integer)
- `check_in` (string, required): YYYY-MM-DD
- `check_out` (string, required): YYYY-MM-DD
- `children` (integer)
- `property` (string, required)

### `create_enquiry` (~124 tokens)

Sends a booking enquiry to the property team (groups, crews, blocks, weekly stays, functions). Requires the guest’s explicit consent to pass their details and conversation context to the property.

Input parameters:

- `consent_confirmed` (boolean, required): Must be true: the guest has consented to their details + context being sent to the property
- `contact` (object, required)
- `context_summary` (string, required): Party, dates, purpose, questions asked — so the team replies informed
- `dates` (string)
- `party` (string)
- `property` (string, required)

### `get_corporate_account_info` (~35 tokens)

The Travellers Group corporate-account answer as data: one account, five properties, direct billing and consolidated invoicing.

### `create_corporate_enquiry` (~70 tokens)

Corporate-account or group-booking enquiry, routed to the Travellers Group corporate team. Requires guest consent, as with create_enquiry.

Input parameters:

- `company` (string, required)
- `consent_confirmed` (boolean, required)
- `contact` (object, required)
- `context_summary` (string, required)

## Diagnostics

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

## Score history

- 2026-08-03: 65
- 2026-08-02: 64
- 2026-08-01: 64
- 2026-07-31: 63
- 2026-07-30: 61
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 58

## Links

- Remote endpoint: https://agent.travellersgroup.com.au/v1/mcp
- Website: https://agent.travellersgroup.com.au/developers
- Changelog RSS feed: https://verifymcp.io/servers/au-com-travellersgroup-agent/v1-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/au-com-travellersgroup-agent/v1-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/au-com-travellersgroup-agent/v1-mcp