Skip to content
External endpointresponds

wsdot-mcp-server

WA highway conditions, ferry schedules, vessel locations, toll rates, and border waits via MCP.

Endpoint URL
https://wsdot.caseyjhand.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
322 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.cyanheads/wsdot-mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
wsdot-mcp-server
Version
0.2.3
Capability keys
logging, resources, tools, prompts
Tool names
wsdot_get_mountain_passes, wsdot_search_alerts, wsdot_get_travel_times, wsdot_get_toll_rates, wsdot_get_border_waits, wsdot_search_cameras, wsdot_get_ferry_terminals, wsdot_get_ferry_routes, wsdot_get_ferry_schedule, wsdot_get_vessel_locations, wsdot_get_terminal_space, wsdot_get_ferry_alerts
Instructions excerpt

WSDOT Traveler Information server for Washington State. Traffic tools (mountain passes, alerts, travel times, toll rates, border waits, cameras) use the WSDOT Traffic API. Ferry tools use the WSF Ferry API. For ferry schedule and space lookups, first call wsdot_get_ferry_terminals to resolve terminal names to numeric IDs. Ferry route IDs from wsdot_get_ferry_routes correspond to impactedRouteIds in wsdot_get_ferry_alerts.

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 140ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 374ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 265ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 322ms
Back to MCP directory