_ registry / mcp http-sse · checked 54m ago

cruisify

https://www.cruisify.co.uk

Registry code: c5d9ff84b82e3b10

api record

Cruisify compares cruises sold to the UK market. Prices are in pounds, per person, "from" the cheapest fare we hold, and each comes with its basis (the cruise line's own wording) and the date it was checked. Some prices are converted from US dollars or euros by us (converted_from says which); these are estimates, and the cruise line's own UK price can differ. Booking happens with the cruise line, not Cruisify. Each cruise's url is its Cruisify page, which shows every date and the current price. Use search_cruises with structured fields where you can; months are YYYY-MM. To page through a…

endpoint
https://www.cruisify.co.uk/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 cruisify live?
Yes — it answered the hub's last check (checked 54m ago). It answered 100% of checks over the last 30 days.
Is cruisify free to use?
Yes — the hub reached it with no key and no payment.
What tools does cruisify have?
5 tools: search_cruises, list_destinations, get_cruise, list_cruise_lines, list_departure_ports.
Is cruisify 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
248ms

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
2 open 3 never probed 2 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_cruise_lines open 54m ago

    The cruise lines we cover and their ships, with how many upcoming cruises we hold for each and their Cruisify pages where there are some.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • list_departure_ports open 54m ago

    The ports the cruises we hold leave from, with UK ports marked, how many upcoming cruises leave from each and its Cruisify page where there is one. Set uk_only for UK ports only (no-fly cruises).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "uk_only": {
      "type": "boolean",
      "description": "true: UK ports only, the departures for no-fly cruises"
    }
  },
  "additionalProperties": false
}
    arguments 11 lines
  • search_cruises unknown never probed

    Search cruises sold to the UK market by destination, departure port, cruise line, ship, months or dates, length, budget, no-fly (UK departures) and ocean or river. Names or slugs both work, and anything we can't match comes back in not_understood. query takes free text ("a week in the fjords from Southampton next June"); structured fields win where both are given. Returns up to 20 cruises a page, with prices in pounds (each with its basis and the date it was checked), month counts and Cruisify links. The cursor holds only the page number, so for the next page call again with the same fields (applied_filters, without query) and next_cursor as cursor, up to 10 pages.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "kind": {
      "enum": [
        "ocean",
        "river"
      ],
      "type": "string",
      "description": "ocean or river cruises only"
    },
    "sort": {
      "enum": [
        "departure",
        "price",
        "price_per_night",
        "nights",
        "newest"
      ],
      "type": "string",
      "description": "departure (default), price, price_per_night, nights (shortest first) or newest"
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Free text, read into the fields above: \"a week in the fjords from Southampton next June\". Structured fields win where both are given. Leave it out when paging."
    },
    "ships": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 20,
      "description": "Ship names or slugs"
    },
    "cursor": {
      "type": "string",
      "maxLength": 64,
      "description": "next_cursor from the previous page. It holds only the page number, so send it with that page's applied_filters"
    },
    "months": {
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d{4}-(?:0[1-9]|1[0-2])$"
      },
      "maxItems": 24,
      "description": "Departure months, YYYY-MM"
    },
    "no_fly": {
      "type": "boolean",
      "description": "true: only cruises leaving from a UK port"
    },
    "date_to": {
      "type": "string",
      "format": "date",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      "description": "Latest departure date, YYYY-MM-DD"
    },
    "date_from": {
      "type": "string",
      "format": "date",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      "description": "Earliest departure date, YYYY-MM-DD"
    },
    "nights_max": {
      "type": "integer",
      "maximum": 365,
      "minimum": 1,
      "description": "Longest length, in nights"
    },
    "nights_min": {
      "type": "integer",
      "maximum": 365,
      "minimum": 1,
      "description": "Shortest length, in nights"
    },
    "round_trip": {
      "type": "boolean",
      "description": "true: round trips only; false: one-way only"
    },
    "cruise_lines": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 20,
      "description": "Cruise line names, slugs or short names: \"P&O\", \"fred-olsen\""
    },
    "destinations": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 20,
      "description": "Destination names or slugs: \"Caribbean\", \"norwegian-fjords\" (list_destinations has them all)"
    },
    "max_price_gbp": {
      "type": "integer",
      "maximum": 1000000,
      "minimum": 1,
      "description": "Highest price per person, in pounds"
    },
    "departure_ports": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 20,
      "description": "Departure port names or slugs: \"Southampton\" (list_departure_ports has them all)"
    }
  },
  "additionalProperties": false
}
    arguments 123 lines
  • list_destinations unknown never probed

    Every destination we know, ocean or river, with how many upcoming cruises we hold for each and its Cruisify page where there is one.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_cruise unknown 54m ago

    One cruise in full: the day-by-day itinerary, every future sailing with its price (or why there isn't one) and a booking link, and its Cruisify page. Give the url of a Cruisify cruise page, as search_cruises returns it, or the cruise's slug.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 500,
      "description": "A Cruisify cruise page URL, as search_cruises returns it"
    },
    "slug": {
      "type": "string",
      "maxLength": 200,
      "description": "A cruise's slug: the last part of its URL"
    }
  },
  "additionalProperties": false
}
    arguments 17 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 c5d9ff84b82e3b10.

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