@cyanheads/wsdot-mcp-server
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 0 of 5 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @cyanheads/wsdot-mcp-server@0.6.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
5 tools that take no input and look read-only were called once with nothing. 0 returned a result.
wsdot_get_mountain_passes | No usable answer tool reported an error: Error: Server config validation failed:\   - WSDOT_ACCESS_CODE (accessCode): Invalid input: expected string, received undefined |
wsdot_search_alerts | No usable answer tool reported an error: Error: Server config validation failed:\   - WSDOT_ACCESS_CODE (accessCode): Invalid input: expected string, received undefined |
wsdot_get_travel_times | No usable answer tool reported an error: Error: Server config validation failed:\   - WSDOT_ACCESS_CODE (accessCode): Invalid input: expected string, received undefined |
wsdot_get_toll_rates | No usable answer tool reported an error: Error: Server config validation failed:\   - WSDOT_ACCESS_CODE (accessCode): Invalid input: expected string, received undefined |
wsdot_get_border_waits | No usable answer tool reported an error: Error: Server config validation failed:\   - WSDOT_ACCESS_CODE (accessCode): Invalid input: expected string, received undefined |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
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_search_alerts stateRoute, region, startMilepost, endMilepost, offset, limit
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.wsdot_get_travel_times route, offset, limit
Returns current vs. average travel times for named WA highway corridors (I-5, I-405, I-90, SR 520, SR 167, and around Vancouver I-205 and SR 14). Use for "how congested is I-5?" or commute time estimates. A route designation filter ("I-5", "5", "SR 520") returns every corridor that starts or ends on that route or writes it in its name ("via 520"), never digits inside another number. Any other filter text matches corridor names ("Everett"), and the first number in it, read as a route, also matches every corridor that starts or ends on that route, in both directions — "I-405 southbound" returns northbound I-405 corridors too, since the direction word is not applied. When current time exceeds average, the corridor is congested. Results are paged — pass offset/limit to page through the full set.wsdot_get_toll_rates stateRoute, offset, limit
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. Filter to one facility with stateRoute ("SR 520", "520", "I-405", or "405" all work). Each row reports stateRoute as the bare, zero-padded number the feed carries ("099", "405") — the posted designation is in the rendered text. Results are paged — pass offset/limit to page through the matching set.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.
8 more tools
wsdot_search_cameras stateRoute, region, startMilepost, endMilepost, titleContains, offset, limit
Returns WSDOT highway camera locations, descriptions, owners, and image URLs. Camera images belong to the owner each camera lists, and to WSDOT when none is listed — 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, milepost range (matched against both the feed milepost and the milepost in the title), or words in the camera title ("Snoqualmie"). Results are ordered by cameraId and paged — pass offset/limit to page through the full set.wsdot_get_ferry_terminals
Returns all WSF ferry terminals with their numeric IDs, names, abbreviations, and coordinates. 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_ferry_routes tripDate
Returns the main WSF ferry routes operating on a given date, each with the directed terminal pairs it serves that day (terminalPairs) — departing and arriving terminal IDs and names, which are exactly the pairs wsdot_get_ferry_schedule accepts for that 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. For the full terminal list with coordinates, use wsdot_get_ferry_terminals.
wsdot_get_ferry_schedule departingTerminalId, arrivingTerminalId, tripDate, remainingOnly
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; terminalPairs on wsdot_get_ferry_routes lists the pairs with service on a date. Set remainingOnly to true to show only future departures for today (useful for "next ferry" queries); a query after midnight also includes the previous service day's sailings still to depart, listed first. Each sailing's serviceDate names the service day whose schedule lists it. For future dates, all sailings for that day are returned. Each sailing carries its vessel ID, WSF's loading-rule code, and the pair's annotations that apply to it — notes such as "No interisland vehicles" that decide whether a sailing takes a car. Sailing times are ISO 8601 UTC, each beside a Local sibling (departureTimeLocal, arrivalTimeLocal) holding the same instant in Pacific time with its UTC offset — quote the Local form as the clock time. tripDate is the Pacific service day, so an evening sailing's UTC time carries the next calendar date. 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_fares departingTerminalId, arrivingTerminalId, tripDate, roundTrip
Returns WSF's fares for one ferry trip between two terminals on a date: every fare line item — passenger, senior and youth, vehicle and driver by length, motorcycle, bicycle, and multi-ride cards — with its amount in dollars, plus WSF's statement of which terminal collects which fares. Requires numeric terminal IDs — use wsdot_get_ferry_terminals to resolve terminal names to IDs; terminalPairs on wsdot_get_ferry_routes lists the pairs with service on a date, the same pairs wsdot_get_ferry_schedule accepts. WSF collects most fares in one direction only, so a line reads 0 on a leg whose departing terminal does not collect it: read collectionDescription before quoting a 0 as free travel, and query the reverse direction for where that fare is charged.
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 absent for vessels not currently operating.
wsdot_get_terminal_space departingTerminalId, offset, limit
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. WSF publishes space for select terminals only, and at times for none: a terminal missing from the result has unconfirmed space, not a wrong ID — wsdot_get_ferry_schedule and wsdot_get_ferry_alerts still show its sailings. 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, at most 20 per page): 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_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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | Apache-2.0 |
|---|---|
| Needs | node >=24.0.0 |
| Source | github.com/cyanheads/wsdot-mcp-server |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-OsFLhWIgLCjsfWyglFyyXG/c1tWHZCN2qFsN/R/YkfJUYnGVkyWWIKxz0fWQ1GYHg4OiPFwt+zrkP1NhUkyK/g== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40cyanheads/wsdot-mcp-server)
New version out? Ask for a fresh report.