# Château du Bû (remote · chateaudubu.fr)

Read-only hotel server: room availability and prices, hotel facts, public events. Normandy, France.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `chateaudubu.fr`: 72/100 (this document), [markdown](https://verifymcp.io/servers/fr-chateaudubu-chateau-du-bu/chateaudubu.md), [page](https://verifymcp.io/servers/fr-chateaudubu-chateau-du-bu/chateaudubu)

## Channel facts

- Endpoint: `https://chateaudubu.fr/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 629 tokens (~157/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Château du Bû MCP server?

Château du Bû is a hosted endpoint at https://chateaudubu.fr/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.

### Claude

```bash
claude mcp add --transport http fr-chateaudubu-chateau-du-bu 'https://chateaudubu.fr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fr-chateaudubu-chateau-du-bu": {
      "url": "https://chateaudubu.fr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fr-chateaudubu-chateau-du-bu": {
      "type": "http",
      "url": "https://chateaudubu.fr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fr-chateaudubu-chateau-du-bu]
url = "https://chateaudubu.fr/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr-chateaudubu-chateau-du-bu": {
      "type": "remote",
      "url": "https://chateaudubu.fr/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fr-chateaudubu-chateau-du-bu --url 'https://chateaudubu.fr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fr-chateaudubu-chateau-du-bu:
    url: "https://chateaudubu.fr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fr-chateaudubu-chateau-du-bu": {
      "Transport": "http",
      "Url": "https://chateaudubu.fr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fr-chateaudubu-chateau-du-bu -t streamable-http -u 'https://chateaudubu.fr/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fr-chateaudubu-chateau-du-bu": {
      "type": "http",
      "url": "https://chateaudubu.fr/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-11-04 (score 72, +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-11-03 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 71)

First indexed and scored.

## MCP tools (4)

### `check_room_availability` (~176 tokens)

Check room availability

Answer 'can a party of N stay from DATE for N nights?'. Returns a verdict (bookable yes/no), the reason when no, the room COMBINATIONS that house the party, and the booking URL. Applies the house rules for you: the earliest arrival date (today or tomorrow, depending on the same-day cut-off), and a stay needs the same rooms free on every night. A party too large for one room is NOT a refusal — the house is sold as several rooms. Prefer this over reading the raw calendar.

Input parameters:

- `adults` (integer): Adults in the party.
- `check_in` (string, required): Arrival date, YYYY-MM-DD (the first night).
- `children` (integer): Children occupying a bed.
- `nights` (integer): Number of nights. Check-out is check_in + nights.

Output parameters:

- `bookable` (boolean)
- `booking_url` (string|null)
- `check_in` (string)
- `check_out` (string)
- `earliest_check_in` (string)
- `explanation` (string): A sentence you can relay to the guest.
- `house_capacity_free`
- `latest_check_in` (string)
- `nights` (integer)
- `options` (array): Room combinations that house the party, each priced in its rate plans (VAT included).
- `options_total` (integer)
- `party` (object)
- `reason` (string): available · too_soon · too_far · invalid_date · not_bookable · party_exceeds_house · no_room_free_for_whole_stay

### `get_availability_calendar` (~80 tokens)

Get the raw availability calendar

The full machine-readable availability feed: free room counts per night by room type, ~180 nights ahead, plus the semantics needed to read it. Use for overviews ('when is there space in October?'); for a specific stay use check_room_availability. Aggregate counts only, no personal data. Read `generated_at` for the real age.

### `get_hotel_info` (~83 tokens)

Get hotel information

Identity, postal address, coordinates, what the château offers, the practical facts of a stay (check-in and check-out times, breakfast, meals, pets, parking, Wi-Fi, charging, access), how to reach it, and the URLs to book, to read more or to get in touch — in English, with the prefixes for the thirteen other languages.

Output parameters:

- `address` (object)
- `category` (string)
- `currency` (string)
- `geo` (object)
- `getting_there` (object)
- `languages` (object)
- `legal_name` (string)
- `locales` (object)
- `name` (string)
- `offers` (array)
- `practical` (object): Check-in and check-out, breakfast, meals, pets, parking, Wi-Fi, charging, access…
- `rooms` (object)
- `urls` (object)

### `list_public_events` (~95 tokens)

List public events

Upcoming public events at the château (concerts, workshops, themed nights…) with dates, price per participant, optional dormitory bed, remaining places and a booking URL. These are separate from hotel rooms.

Input parameters:

- `category` (string): Optional filter, e.g. cuisine, dj-dance, gaming-lan, kpop…
- `from_date` (string): Only events ending on/after this date. Defaults to today.

Output parameters:

- `count` (integer)
- `events` (array)
- `from_date` (string)
- `note` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fr-chateaudubu-chateau-du-bu/chateaudubu#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71

## Common questions

### What is the Château du Bû MCP server?

Château du Bû is an MCP server listed in the public MCP registry as fr.chateaudubu/chateau-du-bu. Read-only hotel server: room availability and prices, hotel facts, public events. Normandy, France. This page covers its hosted endpoint (https://chateaudubu.fr/mcp).

### Is the Château du Bû MCP server safe to use?

Château du Bû scores 72 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 Château du Bû MCP server expose?

Château du Bû exposes 4 tools: check_room_availability, get_availability_calendar, get_hotel_info, list_public_events. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.

### Does the Château du Bû MCP server require authentication?

No. We connected to Château du Bû without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Château du Bû MCP server still maintained?

Château du Bû is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Château du Bû MCP server?

VerifyMCP ran 13 checks on Château du Bû, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://chateaudubu.fr/mcp
- Website: https://chateaudubu.fr/en/
- Changelog RSS feed: https://verifymcp.io/servers/fr-chateaudubu-chateau-du-bu/chateaudubu.xml
- Changelog JSON feed: https://verifymcp.io/servers/fr-chateaudubu-chateau-du-bu/chateaudubu/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fr-chateaudubu-chateau-du-bu/chateaudubu.json
- HTML version of this page: https://verifymcp.io/servers/fr-chateaudubu-chateau-du-bu/chateaudubu