Skip to content

wsdot-mcp-server

io.github.cyanheads/wsdot-mcp-servercyanheadsstreamable-httpv0.6.0Scanned

WA highway conditions, ferry schedules and fares, vessel locations, tolls, and border waits via MCP.

13 tools: 13 only read.

Tools: 0 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the wsdot-mcp-server can do

The wsdot-mcp-server is published by the GitHub account cyanheads. It has 13 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (wsdot_get_terminal_space).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 0.6.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Only reads 13Show 13 read-only tools
  • wsdot_get_border_waitsReturns 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).No findings

    Why it is in this group

    • The name "wsdot_get_border_waits" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_ferry_alertsReturns active WSF ferry service disruptions, delays, and bulletins.No findings

    Why it is in this group

    • The name "wsdot_get_ferry_alerts" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_ferry_faresReturns 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 m…No findings

    Why it is in this group

    • The name "wsdot_get_ferry_fares" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_ferry_routesReturns 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 name…No findings

    Why it is in this group

    • The name "wsdot_get_ferry_routes" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_ferry_scheduleReturns departure times for a specific WSF ferry route on a given date.No findings

    Why it is in this group

    • The name "wsdot_get_ferry_schedule" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_ferry_terminalsReturns all WSF ferry terminals with their numeric IDs, names, abbreviations, and coordinates.No findings

    Why it is in this group

    • The name "wsdot_get_ferry_terminals" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_mountain_passesReturns current road conditions for all Washington State mountain passes: status, weather, road condition, traction laws, temperature, and elevation.No findings

    Why it is in this group

    • The name "wsdot_get_mountain_passes" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_terminal_spaceReturns real-time drive-up and reservable vehicle space available at WSF terminals for upcoming sailings.Reads private dataNo findings

    Why it is in this group

    • The name "wsdot_get_terminal_space" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "drive": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_toll_ratesReturns 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 Br…No findings

    Why it is in this group

    • The name "wsdot_get_toll_rates" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_travel_timesReturns current vs.No findings

    Why it is in this group

    • The name "wsdot_get_travel_times" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_get_vessel_locationsReturns real-time AIS positions, speed, heading, ETA, and dock status for all active WSF vessels.No findings

    Why it is in this group

    • The name "wsdot_get_vessel_locations" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_search_alertsReturns active WA highway alerts: incidents, construction, closures, and restrictions.No findings

    Why it is in this group

    • The name "wsdot_search_alerts" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • wsdot_search_camerasReturns WSDOT highway camera locations, descriptions, owners, and image URLs.No findings

    Why it is in this group

    • The name "wsdot_search_cameras" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 7 changed.+1 added~7 changedView diff

Install

Pinned to version 0.6.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__wsdot__wsdot_get_mountain_passes",
      "mcp__wsdot__wsdot_search_alerts",
      "mcp__wsdot__wsdot_get_travel_times",
      "mcp__wsdot__wsdot_get_toll_rates",
      "mcp__wsdot__wsdot_get_border_waits",
      "mcp__wsdot__wsdot_search_cameras",
      "mcp__wsdot__wsdot_get_ferry_terminals",
      "mcp__wsdot__wsdot_get_ferry_routes",
      "mcp__wsdot__wsdot_get_ferry_schedule",
      "mcp__wsdot__wsdot_get_ferry_fares",
      "mcp__wsdot__wsdot_get_vessel_locations",
      "mcp__wsdot__wsdot_get_terminal_space",
      "mcp__wsdot__wsdot_get_ferry_alerts"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wsdot. Review it before you use it.

Capability tags behind 1 rule
  • mcp__wsdot__wsdot_get_terminal_space private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/wsdot-mcp-server/verify?hash=92c97e88f81a657f013aa77e9ed6c29cab89d0a183ed3345c172218a7ef52833" | jq -e '.changed == false'

Pinned hash 92c97e88f81a, from Nov 12, 2026, 13:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.cyanheads/wsdot-mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.cyanheads/wsdot-mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.cyanheads/wsdot-mcp-server.svg)](https://radar.anlyon.com/servers/io.github.cyanheads/wsdot-mcp-server)

Source: MCP Registry · repository. Synced Nov 12, 2026, 14:17 UTC.

wsdot-mcp-server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the wsdot-mcp-server safe?

No scan can promise that. What its definitions show: 13 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the wsdot-mcp-server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the wsdot-mcp-server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the wsdot-mcp-server have?

13 tools: 13 read. 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 and 5 more.

Does the wsdot-mcp-server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the wsdot-mcp-server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the wsdot-mcp-server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.