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

discover-tours-booking-discover-canal-cruises

https://book.discovertours.nl

Registry code: 0eeab8f1d88c8c6e

api record

Book private tours in Leiden, the Netherlands, by Discover Canal Cruises. Every tour is private: one group per boat or guide, the price is for the whole group, never per person: always say for how many guests a price is (e.g. '€199 for 1 to 2 guests, +€29 for each additional guest'), or use get_price for the exact group size. Prices are in euros and include VAT. Times are local time in Leiden (Europe/Amsterdam).

How to help a guest: 1) list_tours to find a fitting tour; 2) check_availability for their dates; 3) get_price for the group size (and options); 4) create_booking_link with the chosen…

endpoint
https://book.discovertours.nl/mcp/discover-canal-cruises
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 discover-tours-booking-discover-canal-cruises live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is discover-tours-booking-discover-canal-cruises free to use?
Yes — the hub reached it with no key and no payment.
What tools does discover-tours-booking-discover-canal-cruises have?
5 tools: get_tour, create_booking_link, check_availability, get_price, list_tours.
Is discover-tours-booking-discover-canal-cruises 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
237ms

last good check

priced tools
0

of 5 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 5 tools
1 open 4 never probed 1 of 5 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.

  • list_tours open 8h ago

    All private tours of Discover Canal Cruises that can be booked in Leiden, the Netherlands. Returns per tour: id, title, description, duration, group size, starting price, departure point and booking page.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_tour unknown never probed

    Full details of one tour: description, departure point, duration, group size, prices (incl. seasonal prices), regular start times, optional extras with their ids and prices, cancellation policy and contact details.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tour"
      ],
      "properties": {
        "tour": {
          "type": "string",
          "description": "Tour id (the \"tour\" value from list_tours, e.g. \"cosy-tour\")."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • create_booking_link unknown never probed

    Checks that the time is still free and returns a secure booking link with tour, date, time, guests and extras already filled in. Give this link to the guest: they enter their own name, e-mail and phone and pay there. Nothing is reserved or charged by this tool.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tour",
        "date",
        "time",
        "guests"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Tour date, YYYY-MM-DD."
        },
        "time": {
          "type": "string",
          "pattern": "^\\d{2}:\\d{2}$",
          "description": "Start time HH:MM, one of the free times from check_availability."
        },
        "tour": {
          "type": "string",
          "description": "Tour id (the \"tour\" value from list_tours, e.g. \"cosy-tour\")."
        },
        "guests": {
          "type": "integer",
          "maximum": 255,
          "minimum": 1,
          "description": "Number of guests in the group (adults and children together)."
        },
        "options": {
          "type": "object",
          "description": "Optional extras, keyed by option id (or option name) from get_tour. Value: the chosen text for a choice, true for a yes/no extra, a number for a quantity.",
          "additionalProperties": {
            "type": [
              "string",
              "boolean",
              "integer"
            ]
          }
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • check_availability unknown 8h ago

    Free start times of a tour per day. Tours can be booked far ahead (usually up to a year; the result says until when in bookable_until). Each call covers at most 31 days from date_from (default 14); date_from can be any date up to bookable_until, so call again for later periods. Times are local Leiden time. When nothing is free in the range, next_available_date tells the first day with a free time.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tour"
      ],
      "properties": {
        "tour": {
          "type": "string",
          "description": "Tour id (the \"tour\" value from list_tours, e.g. \"cosy-tour\")."
        },
        "guests": {
          "type": "integer",
          "maximum": 255,
          "minimum": 1,
          "description": "Number of guests in the group (adults and children together)."
        },
        "date_to": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Last day, YYYY-MM-DD (inclusive)."
        },
        "date_from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "First day, YYYY-MM-DD, any date up to bookable_until. Default: today."
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • get_price unknown 8h ago

    Exact price for a group on a date (prices can depend on the season), including chosen extras and the VAT breakdown. Same calculation as the booking page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tour",
        "date",
        "guests"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Tour date, YYYY-MM-DD."
        },
        "tour": {
          "type": "string",
          "description": "Tour id (the \"tour\" value from list_tours, e.g. \"cosy-tour\")."
        },
        "guests": {
          "type": "integer",
          "maximum": 255,
          "minimum": 1,
          "description": "Number of guests in the group (adults and children together)."
        },
        "options": {
          "type": "object",
          "description": "Optional extras, keyed by option id (or option name) from get_tour. Value: the chosen text for a choice, true for a yes/no extra, a number for a quantity.",
          "additionalProperties": {
            "type": [
              "string",
              "boolean",
              "integer"
            ]
          }
        }
      },
      "additionalProperties": false
    }
    arguments 37 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 0eeab8f1d88c8c6e.

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

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.