Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.cyanheads/wsdot-mcp-server

REMOTE · WSDOT.CASEYJHAND.COM · 2 COMPONENTS · SCANNED AUG 3

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

+3 this week 68 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2538 tokens (~211/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · wsdot.caseyjhand.com

# add to Claude Code
claude mcp add --transport http cyanheads-wsdot-mcp-server https://wsdot.caseyjhand.com/mcp
# ~/.codex/config.toml
[mcp_servers.cyanheads-wsdot-mcp-server]
url = "https://wsdot.caseyjhand.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-wsdot-mcp-server": {
      "type": "remote",
      "url": "https://wsdot.caseyjhand.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-wsdot-mcp-server --url https://wsdot.caseyjhand.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-wsdot-mcp-server:
    url: "https://wsdot.caseyjhand.com/mcp"
// mcp.json
{
  "mcpServers": {
    "cyanheads-wsdot-mcp-server": {
      "type": "http",
      "url": "https://wsdot.caseyjhand.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −1
    • Tool “wsdot_get_toll_rates” rewrote its description, which is the text the model reads security
    • Tool “wsdot_search_cameras” rewrote its description, which is the text the model reads security
    • Tool “wsdot_get_ferry_alerts” rewrote its description, which is the text the model reads security
    • Tool “wsdot_get_ferry_schedule” rewrote its description, which is the text the model reads security
    • Tool “wsdot_search_alerts” rewrote its description, which is the text the model reads security
    • Tool “wsdot_get_travel_times” rewrote its description, which is the text the model reads security
    • Tool “wsdot_get_terminal_space” rewrote its description, which is the text the model reads security
    • Schema quality: 145 → 211 functional
    • Schema quality: 145 → 201 functional
    • Schema quality: 145 → 174 functional
    • Schema quality: 145 → 171 functional
    • Server version: 0.2.1 → 0.2.2 functional
    • Server version: 0.2.0 → 0.2.1 functional
    • Server version: 0.1.14 → 0.2.0 functional
    • “wsdot_search_alerts” added an optional parameter “limit” cosmetic
    • “wsdot_get_travel_times” added an optional parameter “limit” cosmetic
    • “wsdot_get_terminal_space” added an optional parameter “limit” cosmetic
    • “wsdot_get_terminal_space” added an optional parameter “offset” cosmetic
    • “wsdot_get_toll_rates” added an optional parameter “limit” cosmetic
    • “wsdot_get_toll_rates” added an optional parameter “offset” cosmetic
    • “wsdot_get_travel_times” added an optional parameter “offset” cosmetic
    • “wsdot_search_alerts” added an optional parameter “offset” cosmetic
    • “wsdot_search_alerts” reworded the description of “stateRoute” cosmetic
    • “wsdot_search_alerts” reworded the description of “startMilepost” cosmetic
    • “wsdot_search_alerts” reworded the description of “endMilepost” cosmetic
    • “wsdot_get_travel_times” reworded the description of “route” cosmetic
    • “wsdot_search_cameras” reworded the description of “stateRoute” cosmetic
  • 30 Jul 26 +1
    • MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
    • Server version: 0.1.13 → 0.1.14 functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://wsdot.caseyjhand.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caseyjhand.com CN=WE1,O=Google Trust Services,C=US 7 Jul 2026 5 Oct 2026 ECDSA 256 ECDSA-SHA256 5aad900eb2055a0b0ea55912ec19680c
SANs: caseyjhand.com, *.caseyjhand.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC secure

Validation of wsdot.caseyjhand.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
caseyjhand.com. present 2371 13 Verified
wsdot.caseyjhand.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://wsdot.caseyjhand.com/mcp Verified 200
http (plaintext) http://wsdot.caseyjhand.com/mcp HTTPS enforced 301 https://wsdot.caseyjhand.com/mcp
MCP tools — 12 exposed · ~2,436 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
wsdot_get_border_waits ~171

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
crossingsarrayyesAll WA/Canada border crossing wait times.
noticestringOptional notice when no crossing data is available. Absent on normal results.
totalCountnumberyesTotal number of crossings returned.

No examples provided.

wsdot_get_ferry_alerts ~121

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
alertsarrayyesActive ferry service alerts and disruptions.
noticestringOptional notice when no alerts are active. Absent when alerts are present.
totalCountnumberyesTotal number of active alerts.

No examples provided.

wsdot_get_ferry_routes ~125

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.

NameTypeReqDescription
tripDatestringDate for which to list routes, in ISO 8601 format (YYYY-MM-DD). Defaults to today if omitted.
NameTypeReqDescription
noticestringOptional notice when no routes are available for the date. Absent on normal results.
routesarrayyesFerry routes operating on the requested date.
totalCountnumberyesTotal number of routes returned.
tripDatestringyesDate for which routes were retrieved (ISO 8601).

No examples provided.

wsdot_get_ferry_schedule ~281

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.

NameTypeReqDescription
arrivingTerminalIdnumberyesNumeric ID of the arriving terminal.
departingTerminalIdnumberyesNumeric ID of the departing terminal. Use wsdot_get_ferry_terminals to look up terminal IDs.
remainingOnlybooleanWhen true, returns only future sailings for today. Ignored for future dates. Default: false.
tripDatestringDate in ISO 8601 format (YYYY-MM-DD). Defaults to today if omitted.
NameTypeReqDescription
arrivingTerminalNamestringArriving terminal name.
departingTerminalNamestringDeparting terminal name.
noticestringOptional notice when no sailings are found — e.g. invalid terminal pair or no service for this date. Absent when sailings are present.
remainingOnlybooleanyesWhether the result shows only remaining sailings.
sailingsarrayyesScheduled sailings for this route and date.
totalSailingsnumberyesTotal number of sailings returned.
tripDatestringyesDate of the schedule (ISO 8601).

No examples provided.

wsdot_get_ferry_terminals ~83

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
noticestringOptional notice when no terminal data is available. Absent on normal results.
terminalsarrayyesAll WSF ferry terminals.
totalCountnumberyesTotal number of terminals returned.

No examples provided.

wsdot_get_mountain_passes ~81

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
noticestringOptional notice when no pass data is available — e.g. API temporarily unavailable. Absent on normal results.
passesarrayyesAll WA mountain pass conditions.
totalCountnumberyesTotal number of passes returned.

No examples provided.

wsdot_get_terminal_space ~258

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.

NameTypeReqDescription
departingTerminalIdnumberFilter to a specific terminal by numeric ID. Omit to return all terminals.
limitintegerMaximum terminals to return in this page (1–20). Defaults to 5. Counts terminals, not sailings.
offsetintegerZero-based index of the first terminal to return, for paging. Defaults to 0.
NameTypeReqDescription
hasMorebooleanyesTrue when more terminals remain beyond the current page.
nextOffsetyesOffset to pass to retrieve the next page, or null when this is the last page.
noticestringInformational note about the page window, or guidance when no terminal space data is available, the filter matched nothing, or the offset ran past the end.
terminalFilternumberThe terminal ID filter applied, or absent if no filter was used.
terminalsarrayyesTerminal space availability by terminal.
totalCountnumberyesTotal terminals matching the filter across all pages (not just this page). Counts terminals, not sailings.

No examples provided.

wsdot_get_toll_rates ~176

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).

NameTypeReqDescription
limitintegerMaximum toll rates to return in this page (1–500). Defaults to 50.
offsetintegerZero-based index of the first toll rate to return, for paging. Defaults to 0.
NameTypeReqDescription
hasMorebooleanyesTrue when more toll rates remain beyond the current page.
nextOffsetyesOffset to pass to retrieve the next page, or null when this is the last page.
noticestringInformational note about the page window, or guidance when no toll rate data is available or the offset ran past the end.
ratesarrayyesCurrent toll rates for all active tolled facilities.
totalCountnumberyesTotal toll rate entries across all pages (not just this page).

No examples provided.

wsdot_get_travel_times ~278

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).

NameTypeReqDescription
limitintegerMaximum corridors to return in this page (1–500). Defaults to 50.
offsetintegerZero-based index of the first corridor to return, for paging. Defaults to 0.
routestringOptional filter. A route designation — "I-5", "5", "005", "SR 520", "520" — matches every corridor whose start or end point is on that route, whichever form the feed reports. Any text also matches th…
NameTypeReqDescription
corridorsarrayyesTravel time corridors matching the filter.
hasMorebooleanyesTrue when more corridors remain beyond the current page.
nextOffsetyesOffset to pass to retrieve the next page, or null when this is the last page.
noticestringInformational note about the page window, or guidance when no corridors matched the route filter or the offset ran past the end.
routeFilterstringThe route name filter applied (lowercased), or absent if no filter was used.
totalCountnumberyesTotal corridors matching the filter across all pages (not just this page).

No examples provided.

wsdot_get_vessel_locations ~77

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
noticestringOptional notice when no vessel data is available. Absent on normal results.
totalCountnumberyesTotal number of vessels returned.
vesselsarrayyesAll WSF vessels with real-time position data.

No examples provided.

wsdot_search_alerts ~416

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).

NameTypeReqDescription
endMilepostnumberEnd of the milepost range. Matched by extent overlap like startMilepost, so an alert beginning inside the range and continuing past it is returned.
limitintegerMaximum alerts to return in this page (1–500). Defaults to 50.
offsetintegerZero-based index of the first alert to return, for paging. Defaults to 0.
regionstringWSDOT region name as it appears in alert data: "Northwest", "Olympic", "Southwest", "South Central", "North Central", or "Eastern". Matching is case-insensitive.
startMilepostnumberStart of the milepost range. An alert matches when its extent overlaps the range, so a closure running from MP 10 to MP 30 is returned for a range starting at MP 20. Either bound may be given alone.…
stateRoutestringState route to filter by. Accepts natural forms — "I-90", "90", "090", "SR 520", "520" — matched case- and space-insensitively to the route number. A route-type prefix is compared only when both side…
NameTypeReqDescription
alertsarrayyesMatching highway alerts.
appliedFiltersobjectyesActive filters applied to the alert search.
hasMorebooleanyesTrue when more alerts remain beyond the current page.
nextOffsetyesOffset to pass to retrieve the next page, or null when this is the last page.
noticestringInformational note about the page window, or guidance when no alerts matched the filters or the offset ran past the end.
totalCountnumberyesTotal alerts matching the filters across all pages (not just this page).

No examples provided.

wsdot_search_cameras ~369

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).

NameTypeReqDescription
endMilepostnumberEnd of milepost range to filter cameras.
limitintegerMaximum cameras to return in this page (1–500). Defaults to 50.
offsetintegerZero-based index of the first camera to return, for paging. Defaults to 0.
regionstringWSDOT region code: NW (Northwest), SW (Southwest), OL (Olympic), ER (Eastern), SC (South Central), OS (Olympic South), NC (North Central), or WA (statewide). Matching is case-insensitive.
startMilepostnumberStart of milepost range to filter cameras.
stateRoutestringState route to filter by. Accepts natural forms — "I-90", "90", "090", "SR 520", "520" — matched case- and space-insensitively to the route number. Camera road names carry a route-type prefix, which…
NameTypeReqDescription
appliedFiltersobjectyesActive filters applied to the camera search.
camerasarrayyesCamera metadata and image URLs. Images are copyright WSDOT.
hasMorebooleanyesTrue when more cameras remain beyond the current page.
nextOffsetyesOffset to pass to retrieve the next page, or null when this is the last page.
noticestringInformational note about the page window, copyright, or empty results. Absent when not applicable.
totalCountnumberyesTotal cameras matching the filters across all pages (not just this page).

No examples provided.