Château du Bû
REMOTE · CHATEAUDUBU.FR
Read-only hotel server: room availability and prices, hotel facts, public events. Normandy, France.
Available components
Last scanned (15 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Nov 26 +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.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 71
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 5 Nov 2026 · Probed https://chateaudubu.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chateaudubu.fr | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 3 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | fcabdedd731f07040ebfa1a43ac8aba9 |
| SANs: chateaudubu.fr, *.chateaudubu.fr | ||||||
| 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 chateaudubu.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | DS published | 65381 | 13 | Verified |
| chateaudubu.fr. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chateaudubu.fr/mcp | Verified | 200 | |
| http (plaintext) | http://chateaudubu.fr/mcp | HTTPS enforced | 301 | https://chateaudubu.fr/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 →
check_room_availability Check room availability ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Adults in the party. |
| check_in | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| bookable | boolean | yes | – |
| booking_url | string|null | – | – |
| check_in | string | – | – |
| check_out | string | – | – |
| earliest_check_in | string | – | – |
| explanation | string | yes | 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 | yes | available · too_soon · too_far · invalid_date · not_bookable · party_exceeds_house · no_room_free_for_whole_stay |
No examples provided.
get_availability_calendar Get the raw availability calendar ~80
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_hotel_info Get hotel information ~83
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | yes | – |
| category | string | – | – |
| currency | string | – | – |
| geo | object | – | – |
| getting_there | object | – | – |
| languages | object | – | – |
| legal_name | string | – | – |
| locales | object | – | – |
| name | string | yes | – |
| offers | array | – | – |
| practical | object | yes | Check-in and check-out, breakfast, meals, pets, parking, Wi-Fi, charging, access… |
| rooms | object | – | – |
| urls | object | yes | – |
No examples provided.
list_public_events List public events ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| events | array | yes | – |
| from_date | string | – | – |
| note | string | – | – |
No examples provided.
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.
remote · chateaudubu.fr
claude mcp add --transport http fr-chateaudubu-chateau-du-bu 'https://chateaudubu.fr/mcp'
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.