Wsdot MCP Server

by cyanheads Your server? Claim it

answering

Wsdot MCP Server is answering right now. Last checked 12 min ago. 107 installs a week from npm. It exposes 12 tools. Last commit 25 Aug 2026.

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

Installs per day peak 272 · avg 24 · +30% w/w

a month agotoday

Uptime history 47 days of history · worst day 0%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

340 ms

Response time

average over 24h

107

Installs / week

npm and PyPI

What changed 13

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 August 2026. No other catalogue keeps this.

25 Aug 12 tools changed the parameters they ask for wsdot_get_border_waits, wsdot_get_ferry_alerts, wsdot_get_ferry_routes and 9 more

25 Aug a tool changed version

Nothing serious here today

Today is the operative word: we check Wsdot MCP Server every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add wsdot-mcp-server --transport http https://wsdot.caseyjhand.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "wsdot-mcp-server": {
      "url": "https://wsdot.caseyjhand.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.wsdot-mcp-server]
url = "https://wsdot.caseyjhand.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "wsdot-mcp-server": {
      "url": "https://wsdot.caseyjhand.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "wsdot-mcp-server": {
      "url": "https://wsdot.caseyjhand.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: WSDOT_ACCESS_CODE (WSDOT Traveler API access code. Register at wsdot.wa.gov/Traffic/api/.), MCP_HTTP_HOST (The hostname for the HTTP server.), MCP_HTTP_PORT (The port to run the HTTP server on.), MCP_HTTP_ENDPOINT_PATH (The endpoint path for the MCP server.), MCP_AUTH_MODE (Authentication mode to use: 'none', 'jwt', or 'oauth'.), MCP_LOG_LEVEL (Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').). The author declared them in the registry entry; get the values from the project itself.

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

wsdot

wsdot_get_border_waits

Returns current vehicle wait times at WA→Canada land border crossings: I-5 (Peace Arch, Blaine), SR 543 (Pacific Highway, Blaine), SR 539 (Lynden), and SR 9 (Sumas). Each crossing reports a general-purpose lane and a Nexus lane; SR 539 adds a truck lane and SR 543 adds truck and FAST truck lanes — eleven entries in crossings[], one per lane. crossingName is a route code (e.g. "I5", "I5Nexus", "SR543Trucks"); the readable name is in location.description. Wait times are in minutes. A crossing reporting no current data is still returned — only waitTimeInMinutes is omitted. Use for "how long is the border wait?" questions.

wsdot_get_ferry_alerts

Returns active WSF ferry service disruptions, delays, and bulletins. Each alert carries a one-line summary plus the bulletin title, kind, and full body — the body is where detail such as a replacement sailing appears. Each alert includes impacted route IDs — cross-reference with wsdot_get_ferry_routes to resolve route IDs to human-readable route names. Some IDs (seasonal, San Juan interisland, or international Sidney B.C. routes) may not appear in wsdot_get_ferry_routes for a given date.

wsdot_get_ferry_routes

Returns the main WSF ferry routes operating on a given date. Route IDs correspond to impactedRouteIds in ferry alerts from wsdot_get_ferry_alerts, though some alert route IDs (seasonal, San Juan interisland, or Sidney B.C.) may not appear in this list. To get terminal IDs for schedule and space lookups, use wsdot_get_ferry_terminals.

wsdot_get_ferry_schedule

Returns departure times for a specific WSF ferry route on a given date. Requires numeric terminal IDs — use wsdot_get_ferry_terminals to resolve terminal names to IDs. Set remainingOnly to true to show only future departures for today (useful for "next ferry" queries). For future dates, all sailings for that day are returned. Sailing times are ISO 8601 UTC while tripDate is the Pacific service day, so evening sailings carry the next UTC date — convert to America/Los_Angeles before quoting a clock time. Cancellations are not carried here — WSF drops a cancelled sailing from the schedule instead of flagging it, so a listed sailing is not confirmation that it will run. Check wsdot_get_ferry_alerts for disruptions; those are scoped to a route, not an individual sailing.

wsdot_get_ferry_terminals

Returns all WSF ferry terminals with their numeric IDs, names, and abbreviations. Call this first to resolve human-readable terminal names (e.g. "Bainbridge Island", "Seattle", "Kingston") to the numeric terminal IDs required by the schedule and space tools. The terminal list is small (20 terminals) and rarely changes.

wsdot_get_mountain_passes

Returns current road conditions for all Washington State mountain passes: status, weather, road condition, traction laws, temperature, and elevation. Includes all 16 passes (Snoqualmie, Stevens, White, Blewett, Cayuse, etc.). Use for "is the pass open?", traction law status, or winter driving planning.

wsdot_get_terminal_space

Returns real-time drive-up and reservable vehicle space available at WSF terminals for upcoming sailings. Use for "will I make the ferry?" or "how full is the next sailing?" questions. Optionally filter to a specific terminal by ID (use wsdot_get_ferry_terminals for the ID). driveUpSpaceCount is the key field — zero means the drive-up lane is full. Destinations are arrivingTerminalIds, not the itineraryLabel string: a sailing can serve several terminals, and those IDs are what wsdot_get_ferry_schedule accepts. Results are paged by terminal (default 5, max 20): offset/limit select whole terminals and totalCount counts matching terminals, not sailings — every sailing of a returned terminal is included, so page size varies with how many departures each terminal carries.

wsdot_get_toll_rates

Returns current dynamic toll rates for WA express lanes and tolled facilities: SR 99 (WSDOT Tunnel), SR 167 HOT Lanes, I-405 Express Lanes, SR 509 tolled segment, and the SR 520 Bridge. Rates are time-banded and change dynamically based on traffic conditions. stateRoute is a bare, zero-padded route number ("099", "405") — the posted designation is in the rendered text. Results are paged — pass offset/limit to page through the full set (the notice reports the next offset).

wsdot_get_travel_times

Returns current vs. average travel times for named WA highway corridors (I-5, I-90, SR 520, SR 99, I-405, SR 167, etc.). Use for "how congested is I-5?" or commute time estimates. The route filter matches two ways: a route designation ("I-5", "5", "SR 520") returns every corridor measured on that route, and any text also matches corridor names ("Everett"). When current time exceeds average, the corridor is congested. Results are paged — pass offset/limit to page through the full set (the notice reports the next offset).

wsdot_get_vessel_locations

Returns real-time AIS positions, speed, heading, ETA, and dock status for all active WSF vessels. Use for "where is the ferry now?", vessel tracking, or checking if a vessel is in service. Position data may lag by 30–60 seconds. Many fields are null for vessels not currently operating.

wsdot_search_alerts

Returns active WA highway alerts: incidents, construction, closures, and restrictions. Filter by state route ("I-90", "90", "SR 520", or "520" all work), WSDOT region (Northwest, Olympic, Southwest, South Central, North Central, Eastern), or milepost range, matched against the alert's full extent. Omit all filters to return all current statewide alerts. Results are ordered by alertId and paged — pass offset/limit to page through the full set (the notice reports the next offset).

wsdot_search_cameras

Returns WSDOT highway camera locations, descriptions, and image URLs. Camera images are copyright WSDOT — only metadata and image URLs are returned, not image bytes. Filter by state route ("I-90", "90", "SR 520", or "520" all work), WSDOT region, or milepost range. Results are ordered by cameraId and paged — pass offset/limit to page through the full set (the notice reports the next offset).

Endpoints

URL	Transport	State	Latency	Checked
https://wsdot.caseyjhand.com/mcp	streamable-http	answering	189 ms	12 min ago

Alternatives to Wsdot MCP Server

same job, measured the same way

Opencage Geocoding

by mcparmory

Convert addresses to coordinates and reverse-geocode locations worldwide

246 installs/wk local only

Water Conditions

by aybeeare

Real-time water temperature and tides for 8,000+ locations, by name or lat/long coordinates.

57 installs/wk local only

Weather MCP Server

by jaredco-ai

Fast - accurate weather conditions and forecasts by city or coordinates.

30 installs/wk local only

AgentHub - Lean MCP Orchestrator

by propstreet

Enables coding agents to coordinate edits, reviews, and escalations without file locking conflicts

16 installs/wk local only

UK Court Finder MCP Server from MCPBundles

by mcpbundles

Find UK courts and tribunals by location, name, or law area with addresses and contacts

answering

2b2t Atlas

by bobymicjohn

Search 2b2t locations, groups, highways, renders, Archive warps, and WDL metadata.

21 tools answering

Kroger

by pipeworx-io

Kroger MCP — grocery products, prices, and store locations (developer.kroger.com)

34 tools answering

VA Healthcare Facilities

by olyport

VA facility locations, services, wait times, and satisfaction scores

3 tools answering

Wsdot MCP Server — questions

Answers built from our own checks of this server.

What can Wsdot MCP Server do?

It exposes 12 tools, read directly from the server on our last check. Among them: wsdot_get_border_waits, wsdot_get_ferry_alerts, wsdot_get_ferry_routes, wsdot_get_ferry_schedule, wsdot_get_ferry_terminals, wsdot_get_mountain_passes and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Wsdot MCP Server working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 340 ms. The bar chart above shows every period we have measured.

How do I connect Wsdot MCP Server?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Wsdot MCP Server need an API key?

No. Wsdot MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Wsdot MCP Server?

It answers our handshake in 340 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Wsdot MCP Server?

The npm package @cyanheads/wsdot-mcp-server was installed 107 times in the last week. Week over week that is +30%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Wsdot MCP Server open source?

Yes — it is published under the Apache-2.0 licence, written in TypeScript, 1 stars on GitHub and 8 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.