← Registry

General Tools

charter.boats

An MCP server that provides search tools for charter boats, marinas, points of interest, sailing routes, and curated itineraries to help plan sailing trips.

1 endpoint11 known toolsFirst detected October 11, 2026Last detected October 11, 2026

ENDPOINT 1

https://charter.boats/mcp

No auth detected

MCP server metadata

Name
Charter Boats
Version
1.0.0
Capabilities
resourcestoolsprompts

Known tools 11

search_boats

Search charter boats by location, name, type, dates, capacity, budget.

Inferred read-only
search_locations

Find marinas, harbours and anchorages three ways: by NAME (q), by POPULARITY within an area (region/country/city — ranked on observed AIS vessel traffic for a month), or by REACH from a place you already have (`from` + `within_nm`) — where boats are actually recorded sailing to from there, with measured passage times.

Inferred read-only
search_pois

Find restaurants, fuel, groceries, attractions near a location, or search by POI name.

Inferred read-only
search_routes

Find sailing passages between destinations with distance and difficulty.

Inferred read-only
search_trips

Find existing curated sailing itineraries by location, name, duration, activities.

Inferred read-only
search_content

Search articles and Q&A on charter.

Inferred read-only
get_boat_details

Get full details of a specific boat: security deposit, cancellation policy, amenities, fees, seasonal prices, check-in/out times, location details — and the dates it is actually free (priced date ranges plus bookable slots for the year ahead).

Inferred read-only
get_boat_standouts

What stands out about ONE boat for one week, measured against similar boats: its pros and its cons, each with how it compares ("47.

Inferred read-only
get_poi_details

Get full details of a point of interest by ID: description, opening hours, address, contact, nearby marinas, special offers.

Inferred read-only
get_location_details

Get full details of a marina, anchorage or bay by ID: description, amenities, contact, boat count and cheapest day rate, PLUS what only we know from tracked AIS traffic — how busy it is in each month of the year, how boats use it (share of overnight visits, typical day-stop length, what time it fills up), whether it is a hidden gem, the places boats actually sail to from there, most-travelled first with the share of the tracked trips each one takes and an estimated passage time, and the nearest bookable base for a spot with no fleet of its own.

Inferred read-only
get_trip_details

Get full details of a sailing itinerary/trip by ID: day-by-day stops, distances, activities, highlights, notes.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.charter-boats]
url = "https://charter.boats/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "charter-boats": {
      "type": "http",
      "url": "https://charter.boats/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: charter-boats
Remote MCP URL: https://charter.boats/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "charter-boats": {
      "url": "https://charter.boats/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "charter-boats": {
      "type": "http",
      "url": "https://charter.boats/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "charter-boats",
  "transport": "streamable-http",
  "url": "https://charter.boats/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.