[cyrusmg]

What this adds

CruiseHops, plugin (content/plugins/cruisehops.md): a hosted, read-only MCP server for searching Carnival and Royal Caribbean cruises (more cruise companies pending - I will add a PR later to update it once it's available), comparing itineraries and cabin offers, and inspecting recorded offer price history.

Checklist

• This PR adds exactly ONE new file under content/ (plus assets for this entry, if any).
• It follows CONTRIBUTING.md — required fields + the golden rules (G1–G8).
• npm run validate passes locally (schema, slug, vocabularies).
• slug is kebab-case and exactly matches the filename.
• I ran / used this myself end to end — it works today.
• Every URL in the frontmatter resolves to real, relevant content.
• The prompt body is the real, complete prompt — not a summary or a teaser.
• The entry body is plain markdown — no raw HTML (<script>, <iframe>, <style>, <form>, inline event handlers). CI rejects it (§8.5).
• I did NOT set verified_at or status: live — a maintainer sets those during verification (§10.1).
• This is not an ad. A listing that exists to funnel traffic to your product gets closed. Sponsor slots will exist for that — this isn't one.
• If this is someone else's work: author is the original creator, the origin is linked (source_url for a plugin, source_tweets[] for a use case), and scouted_by is me. (Not applicable: this is our own project.)
• If the source is a YouTube video: primary_source is kind: youtube-video with a youtube.com/watch, youtu.be/ or youtube.com/shorts/ URL, plus the video's real title and channel — those two are required because they are what the page shows if the player never loads. timestamp is optional and is written mm:ss. (Not applicable: the source is our public integration documentation.)
• I license this contribution under CC BY 4.0 (attribution: entry author + grokbot.dev).

Where it came from

This is my own project to provide MCP server to search for cruises.

• Project: https://cruisehops.com
• Public integration writeup and connection instructions: https://cruisehops.com/integrations
• MCP endpoint: https://cruisehops.com/mcp
• Operator and service terms: https://cruisehops.com/terms

The server uses Streamable HTTP and requires no account or API key. Tools are read-only; prices are captured observations rather than guaranteed live quotes or availability. Booking and payment remain with the cruise provider.