INDIVIDUAL MCP TOOL
active_cyclones
Live tropical cyclones (typhoons/hurricanes) currently active on ocean trade lanes — name, basin, category, center position, max wind, pressure and movement, from CMA (NW-Pacific) + NHC (Atlantic/E-Pacific) + JTWC (Indian/Southern Hemisphere) + GDACS (global).
LIVE ENDPOINT
https://mcp.schedulesmcp.com/mcp
Connect to this endpoint to inspect the live schema for active_cyclones and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description suggests a financial action.
Parent server
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.ocean-schedules]
url = "https://mcp.schedulesmcp.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ocean-schedules": {
"type": "http",
"url": "https://mcp.schedulesmcp.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ocean-schedules
Remote MCP URL: https://mcp.schedulesmcp.com/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": {
"ocean-schedules": {
"url": "https://mcp.schedulesmcp.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ocean-schedules": {
"type": "http",
"url": "https://mcp.schedulesmcp.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ocean-schedules",
"transport": "streamable-http",
"url": "https://mcp.schedulesmcp.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
compare_lanes— Compare ocean carriers serving an origin→destination port pair, ranked by on-time reliability and transit time.carrier_reliability— On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.transit_time— Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.find_sailings— Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.get_schedules— Published forward sailing schedules on an origin→destination lane: carrier, vessel, voyage, ETD/ETA and cut-offs, soonest first.find_best_sailings— Decision query: the best upcoming sailings on a lane, ONE per carrier (next bookable departure), ranked.watch_lane— Watch a lane for schedule alerts (PAID): get emailed when a sailing on it is blanked, a booking cut-off is about to close, or a sailing slips.port_reliability— Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor.