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

floreal-holidays

https://mcp.florealholidays.be

Registry code: aaf9efbae138b8d9

api record

Today is Saturday, 10 October 2026 (2026-10-10, Europe/Brussels). Dates you pass must be on or after today; a month without a year means the next occurrence.

Floreal Holidays runs thirteen holiday locations in Belgium, grouped in five regions: coast (Belgian coast), ardennes (Belgian Ardennes), kempen (De Kempen), gaume (Gaume), wallonie-picarde (Wallonie picarde). Accommodation kinds: hotel room; studio; apartment; chalet or holiday home; mobile home; glamping or cabin (safari tent, ecolodge, tree house, hikers cabin); camping pitch (tent or motorhome). One location often combines several…

endpoint
https://mcp.florealholidays.be/mcp
protocol
http-sse ·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 floreal-holidays live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is floreal-holidays free to use?
Yes — the hub reached it with no key and no payment.
What tools does floreal-holidays have?
16 tools: get_stay_price, list_arrangements, bookings_search, get_menu, departures, flash_dashboard, arrivals, search_stays, ….
Is floreal-holidays 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 99.5%· all time 99.5%

latency
68ms

last good check

priced tools
0

of 16 tools

_ answered our checks, 90 days 437 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
maps travel & places travel & transport
used for
  • find holiday stays in belgium
  • get live price for a stay
  • list holiday park locations
  • get restaurant menus of a location
takes → gives
text → data
tools
16 reads
_ 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 16 tools
3 open 13 never probed 3 of 16 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_faq reads open 4d ago

    Published questions and answers about Floreal Holidays, optionally narrowed to one location. Answers are multilingual (Dutch, French, English).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Location slug; omit for the general questions"
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • list_locations reads open 17h ago

    All Floreal Holidays locations in Belgium with their slug, name, kind of site, town, region and coordinates. Use the "slug" as the `domain` argument of every other tool. The "type" is the kind of site, not the accommodation on it — a park can offer hotel rooms, studios, apartments, chalets and camping pitches at the same time; ask list_accommodation_types for that. Locations with bookable=false (the head office) cannot be priced.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • gift_card_info reads open 17h ago

    Information about Floreal Holidays gift cards: amounts, languages and where to buy one. Gift cards are valid at every location.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_stay_price reads unknown 3d ago

    Live all-in price and availability for a stay at one Floreal location, per accommodation type, for the given arrival date, number of nights and party. Each option carries its kind (hotel room, studio, apartment, chalet, glamping, camping pitch) and how many people it sleeps. Pass a packageId from list_arrangements to price that specific package. With flexibleDays the same call also prices the days around the arrival; when the exact date is full the answer already lists "alternatives" within three days. The answer carries a bookingUrl: the same search on our own booking site — always share it so the guest can book. When the guest has not chosen a location yet, use search_stays instead.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain",
    "arrival",
    "nights",
    "adults"
  ],
  "properties": {
    "lang": {
      "enum": [
        "nl",
        "fr",
        "en"
      ],
      "type": "string",
      "description": "Language for accommodation names; defaults to Dutch, the language they are maintained in"
    },
    "pets": {
      "type": "integer",
      "maximum": 5,
      "minimum": 0,
      "description": "Number of pets"
    },
    "adults": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Number of adults"
    },
    "babies": {
      "type": "integer",
      "maximum": 10,
      "minimum": 0,
      "description": "Number of babies (under 2)"
    },
    "domain": {
      "type": "string",
      "description": "Location slug from list_locations, e.g. \"floreal-blankenberge\""
    },
    "nights": {
      "type": "integer",
      "maximum": 30,
      "minimum": 1,
      "description": "Number of nights"
    },
    "arrival": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Arrival date (YYYY-MM-DD)"
    },
    "children": {
      "type": "integer",
      "maximum": 20,
      "minimum": 0,
      "description": "Number of children (under 12)"
    },
    "packageId": {
      "type": "string",
      "description": "Package id from list_arrangements (optional)"
    },
    "flexibleDays": {
      "type": "integer",
      "maximum": 14,
      "minimum": 0,
      "description": "Also search this many days before and after the arrival date, in the same call (0 = that day only). Use it for \"around the 12th\" or \"some weekend in July\". When the exact date has nothing, the tool already looks 3 days around it by itself."
    }
  },
  "additionalProperties": false
}
    arguments 71 lines
  • list_arrangements reads unknown 3d ago

    The bookable packages of one location: stay arrangements and add-on extras, with name, description and validity period. A package price depends on the stay and the party, so ask for it with get_stay_price and the packageId from this list.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Location slug, e.g. \"floreal-blankenberge\""
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • bookings_search reads unknown never probed

    Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns reservations in a date window, by room or booking number. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_menu reads unknown 9h ago

    The current restaurant and food & beverage menus of one Floreal location, as published by that location. Not every location publishes menus.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "lang": {
      "enum": [
        "nl",
        "fr",
        "en"
      ],
      "type": "string",
      "description": "Menu language (defaults to Dutch)"
    },
    "domain": {
      "type": "string",
      "description": "Location slug, e.g. \"floreal-blankenberge\" (see list_locations)"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • departures reads unknown 1h ago

    Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns the reservations departing on a day. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • flash_dashboard reads unknown 1h ago

    Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns occupancy, revenue and KPIs per day, month or year. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • arrivals reads unknown 17h ago

    Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns the reservations arriving on a day. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • search_stays reads unknown 2d ago

    Find where Floreal Holidays has a stay available, across every location in one call, with the live all-in price per accommodation type. Use this whenever the guest has not picked a location yet — "somewhere at the Belgian coast in July", "a hotel room in the Ardennes with a dog", "the cheapest week for a family of four". Narrow with `region` (coast, ardennes, kempen, gaume, wallonie-picarde), with `accommodation` (hotel_room, studio, apartment, chalet, mobile_home, glamping, camping_pitch, or plain words like "hotel", "appartement", "chalet") or with `maxPrice`; widen with `flexibleDays`. Results are sorted cheapest first, one cheapest option per accommodation type, and each result carries a bookingUrl for that location — always share it so the guest can book. When nothing matches, the answer lists "alternatives" within three days. For one known location get_stay_price gives the full picture.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "arrival",
    "nights",
    "adults"
  ],
  "properties": {
    "lang": {
      "enum": [
        "nl",
        "fr",
        "en"
      ],
      "type": "string",
      "description": "Language for accommodation names; defaults to Dutch, the language they are maintained in"
    },
    "pets": {
      "type": "integer",
      "maximum": 5,
      "minimum": 0,
      "description": "Number of pets"
    },
    "adults": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Number of adults"
    },
    "babies": {
      "type": "integer",
      "maximum": 10,
      "minimum": 0,
      "description": "Number of babies (under 2)"
    },
    "nights": {
      "type": "integer",
      "maximum": 30,
      "minimum": 1,
      "description": "Number of nights"
    },
    "region": {
      "type": "string",
      "description": "Region to limit the search to: coast, ardennes, kempen, gaume, wallonie-picarde (Dutch/French names work too)"
    },
    "arrival": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Arrival date (YYYY-MM-DD)"
    },
    "domains": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Location slugs to limit the search to; takes precedence over region"
    },
    "children": {
      "type": "integer",
      "maximum": 20,
      "minimum": 0,
      "description": "Number of children (under 12)"
    },
    "maxPrice": {
      "type": "number",
      "description": "Highest acceptable all-in price for the whole stay, in euro",
      "exclusiveMinimum": 0
    },
    "flexibleDays": {
      "type": "integer",
      "maximum": 14,
      "minimum": 0,
      "description": "Also search this many days before and after the arrival date, in the same call (0 = that day only). Use it for \"around the 12th\" or \"some weekend in July\". When the exact date has nothing, the tool already looks 3 days around it by itself."
    },
    "accommodation": {
      "type": "string",
      "description": "Accommodation kind (hotel_room, studio, apartment, chalet, mobile_home, glamping, camping_pitch) or a word from the type name, e.g. \"hotel\", \"apartment\", \"chalet\", \"tent\""
    }
  },
  "additionalProperties": false
}
    arguments 82 lines
  • reservation_detail reads unknown 9h ago

    Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns one reservation: dates, party size, room, status. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • tasks_overview reads unknown 9h ago

    Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns tasks per department and status. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • whoami reads unknown 4d ago

    Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns who you are and which locations you may look at. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • day_summary reads unknown 1h ago

    Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns arrivals, departures and guests in house for a day. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • list_accommodation_types reads unknown 34h ago

    What kinds of accommodation one Floreal Holidays location offers — hotel rooms, studios, apartments, chalets, glamping, camping pitches — each with how many people it sleeps and an indicative "from" price. Use this for questions about what a location has ("does Blankenberge have hotel rooms?", "are there apartments in Nieuwpoort?"). A location can combine several kinds. Without a date it probes the next two months and every length of stay up to a week, so it also finds types that need a fixed number of nights. The prices are samples; ask get_stay_price for the guest's own dates.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "lang": {
      "enum": [
        "nl",
        "fr",
        "en"
      ],
      "type": "string",
      "description": "Language for accommodation names; defaults to Dutch, the language they are maintained in"
    },
    "domain": {
      "type": "string",
      "description": "Location slug from list_locations, e.g. \"floreal-blankenberge\""
    },
    "arrival": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Optional sample arrival date; omit to probe the next two months (YYYY-MM-DD)"
    }
  },
  "additionalProperties": false
}
    arguments 28 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 aaf9efbae138b8d9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/aaf9efbae138b8d9/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/aaf9efbae138b8d9/badge.svg)](https://brick.blue/agent/aaf9efbae138b8d9?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
100%

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.