_ registry / mcp http-sse · checked 5h ago

ocean-schedules

https://mcp.schedulesmcp.com

Registry code: b44a00ab8b714e18

api record

Compare ocean carrier sailing schedules, transit times, and on-time reliability before you book.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.schedulesmcp.com/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 ocean-schedules live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is ocean-schedules free to use?
Yes — the hub reached it with no key and no payment.
What tools does ocean-schedules have?
12 tools: transit_time, watch_lane, port_congestion, carrier_reliability, port_reliability, carrier_league, find_sailings, find_best_sailings, ….
Is ocean-schedules 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
99.6%

90 days 99.5%· all time 99.5%

latency
204ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 385 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
maps travel & places logistics & shipping
used for
  • compare ocean carriers on a lane
  • find the best upcoming sailings
  • check carrier on-time reliability
  • check port congestion
  • watch a lane for schedule alerts
takes → gives
text → data
tools
11 reads1 changes data
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 12 tools
12 never probed 0 of 12 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.

  • transit_time reads unknown never probed

    Observed transit-time distribution (median / p90, in days) for a carrier on an origin→destination lane.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "origin",
    "destination"
  ],
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE"
    },
    "carrier_code": {
      "type": "string",
      "description": "Optional carrier SCAC to filter"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • watch_lane changes data unknown never probed

    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. Also alerts on reliability drops. Returns the created watch.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "origin",
    "destination"
  ],
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE, e.g. CNNGB"
    },
    "alert_slip": {
      "type": "boolean",
      "description": "Alert when a sailing slips vs schedule (default true)"
    },
    "alert_blank": {
      "type": "boolean",
      "description": "Alert on suspected blank sailings (default true)"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. NLRTM"
    },
    "alert_cutoff": {
      "type": "boolean",
      "description": "Alert when a booking cut-off is closing (default true)"
    },
    "carrier_code": {
      "type": "string",
      "description": "Optional SCAC to scope the watch to one carrier"
    },
    "cutoff_lead_hours": {
      "type": "number",
      "description": "Hours before cut-off to alert (default 48)"
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • port_congestion reads unknown never probed

    Fused port-congestion signal for a port (UN/LOCODE): effective level (mild/moderate/severe), expected added wait in days (for ETA-band widening), a 0–1 confidence, and per-source detail — weiyun broad-AIS analysis + IMF PortWatch throughput + our own AIS wait/density.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "port"
  ],
  "properties": {
    "port": {
      "type": "string",
      "description": "Port UN/LOCODE, e.g. NLRTM"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • carrier_reliability reads unknown never probed

    On-time performance and delay distribution for a specific carrier (by SCAC), optionally on a given lane.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "carrier_code"
  ],
  "properties": {
    "carrier_code": {
      "type": "string",
      "description": "Carrier SCAC, e.g. MAEU"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • port_reliability reads unknown never probed

    Congestion and dwell signals for a port (UN/LOCODE) — average wait and vessels at anchor.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "port"
  ],
  "properties": {
    "port": {
      "type": "string",
      "description": "Port UN/LOCODE, e.g. NLRTM"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • carrier_league reads unknown never probed

    Carrier league table — ocean carriers ranked by overall on-time reliability across all tracked lanes.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • find_sailings reads unknown 20d ago

    Observed and derived upcoming departures on an origin→destination lane, with carrier and frequency.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "origin",
    "destination"
  ],
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • find_best_sailings reads unknown 14h ago

    Decision query: the best upcoming sailings on a lane, ONE per carrier (next bookable departure), ranked. Filter by date window, max transit days, min on-time reliability, cut-off still open, and direct-vs-transshipment. Use this to answer "what should I book?".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "origin",
    "destination"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Latest departure date YYYY-MM-DD (default: +60 days)"
    },
    "from": {
      "type": "string",
      "description": "Earliest departure date YYYY-MM-DD (default: today)"
    },
    "sort": {
      "enum": [
        "recommended",
        "reliability",
        "fastest",
        "soonest"
      ],
      "type": "string",
      "description": "Ranking (default recommended = reliability blended with transit)"
    },
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE or name resolves upstream, e.g. CNSHA"
    },
    "cutoff_open": {
      "type": "boolean",
      "description": "Only sailings whose booking cut-off has not passed"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. NLRTM"
    },
    "direct_only": {
      "type": "boolean",
      "description": "Exclude transshipment routings"
    },
    "max_transit_days": {
      "type": "number",
      "description": "Maximum transit time in days"
    },
    "reliability_floor": {
      "type": "number",
      "description": "Minimum 90-day on-time %, 0-100"
    }
  },
  "additionalProperties": false
}
    arguments 53 lines
  • get_schedules reads unknown 14h ago

    Published forward sailing schedules on an origin→destination lane: carrier, vessel, voyage, ETD/ETA and cut-offs, soonest first. Sourced from carrier connectors (and aggregator coverage). Use this to find concrete upcoming departures to book.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "origin",
    "destination"
  ],
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE, e.g. CNSHA"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. NLRTM"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • active_cyclones reads unknown never probed

    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). Use this to see which storms are at sea right now.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • lane_storm_exposure reads unknown never probed

    Whether an origin→destination ocean lane currently passes through an active cyclone's forecast gale field (a "storm-exposed" sailing at risk of weather delay). Omit ports to list every exposed lane.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE, e.g. CNSHA"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. USLAX"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • compare_lanes reads unknown never probed

    Compare ocean carriers serving an origin→destination port pair, ranked by on-time reliability and transit time. Use this to decide which line to book.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "origin",
    "destination"
  ],
  "properties": {
    "origin": {
      "type": "string",
      "description": "Origin port UN/LOCODE, e.g. CNSHA"
    },
    "destination": {
      "type": "string",
      "description": "Destination port UN/LOCODE, e.g. NLRTM"
    }
  },
  "additionalProperties": false
}
    arguments 19 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 b44a00ab8b714e18.

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

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.