Remote MCP · Endpoint

Charter Boats MCP server

No. Charter Boats answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://charter.boats/mcp

The last check completed an MCP handshake.

Registry name
boats.charter/charter-boats
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
81 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search 14,000+ charter boats with live prices, plus marinas, anchorages, routes and itineraries.
Listing
From the official MCP registry (active).
Recent checks of Charter Boats
CheckedResultHandshake
2 hours agoHandshake completed81 ms
1 day agoHandshake completed54 ms
3 days agoHandshake completed71 ms
3 days agoHandshake completed76 ms
4 days agoHandshake completed75 ms
5 days agoHandshake completed94 ms
7 days agoHandshake completed69 ms
10 days agoHandshake completed206 ms
12 days agoHandshake completed117 ms
15 days agoHandshake completed119 ms
17 days agoHandshake completed76 ms
19 days agoHandshake completed183 ms
21 days agoHandshake completed88 ms
23 days agoHandshake completed119 ms
25 days agoHandshake completed117 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Charter Boats and makes no claim about it beyond what these checks measured.