_ registry / mcp streamable-http · checked 1h ago

chateau-du-bu

https://chateaudubu.fr

Registry code: cccea621cacf7a66

api record

Read-only tools for Château du Bû, a château hotel in Aurseulles (Calvados, Normandy, France). Use them to answer guest questions about room availability, the estate, and public events.

IMPORTANT — do not compute availability yourself from raw counts. Call `check_room_availability`: a night can be free and still not be bookable (arrivals open from `earliest_check_in` — today or tomorrow depending on the day's same-day cut-off), and a multi-night stay needs the same room type free on every night. The tool applies both rules and returns a verdict.

endpoint
https://chateaudubu.fr/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is chateau-du-bu live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is chateau-du-bu free to use?
Yes — the hub reached it with no key and no payment.
What tools does chateau-du-bu have?
4 tools: check_room_availability, get_availability_calendar, get_hotel_info, list_public_events.
Is chateau-du-bu safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
198ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_availability_calendar open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_hotel_info open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_public_events open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "category": {
          "type": "string",
          "description": "Optional filter, e.g. cuisine, dj-dance, gaming-lan, kpop…"
        },
        "from_date": {
          "type": "string",
          "format": "date",
          "description": "Only events ending on/after this date. Defaults to today."
        }
      }
    }
    arguments 14 lines
  • check_room_availability unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "check_in"
      ],
      "properties": {
        "adults": {
          "type": "integer",
          "default": 2,
          "minimum": 1,
          "description": "Adults in the party."
        },
        "nights": {
          "type": "integer",
          "default": 1,
          "maximum": 30,
          "minimum": 1,
          "description": "Number of nights. Check-out is check_in + nights."
        },
        "check_in": {
          "type": "string",
          "format": "date",
          "description": "Arrival date, YYYY-MM-DD (the first night)."
        },
        "children": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "Children occupying a bed."
        }
      }
    }
    arguments 32 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id cccea621cacf7a66.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cccea621cacf7a66/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cccea621cacf7a66/badge.svg)](https://brick.blue/agent/cccea621cacf7a66?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.