wsdot-mcp-server
Registry code: df8a7278fcd76ca2
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; wsdot_get_ferry_routes lists the terminal pairs each route serves on a date, which are the pairs wsdot_get_ferry_schedule accepts. Ferry route IDs from wsdot_get_ferry_routes correspond to impactedRouteIds in wsdot_get_ferry_alerts.
- endpoint
- https://wsdot.caseyjhand.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is wsdot-mcp-server live?
- Yes — it answered the hub's last check (checked 3m ago). It answered 100% of checks over the last 30 days.
- Is wsdot-mcp-server free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does wsdot-mcp-server have?
- 12 tools: wsdot_get_border_waits, wsdot_get_ferry_schedule, wsdot_get_vessel_locations, wsdot_search_cameras, wsdot_get_toll_rates, wsdot_get_terminal_space, wsdot_get_travel_times, wsdot_get_mountain_passes, ….
- Is wsdot-mcp-server safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.6%· all time 99.6%
last good check
of 12 tools
- degraded → live
- live → degraded· HTTP 530
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- get border wait times
- get ferry alerts
- get ferry routes
- get ferry schedules
- get mountain pass conditions
- takes → gives
- text, data → data
- tools
- 12 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
wsdot_get_vessel_locations reads open 20h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {}, "additionalProperties": false }arguments 6 lineswsdot_search_cameras reads open 14h ago
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, milepost range, or words in the camera title ("Snoqualmie"). Results are ordered by cameraId and paged — pass offset/limit to page through the full set. A page ends at limit or at a 24,000-byte response budget, whichever comes first; the notice reports the next offset.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "maximum": 500, "minimum": 1, "description": "Maximum cameras to return in this page (1–500). Defaults to 50. A large page ends sooner, at the 24,000-byte response budget." }, "offset": { "type": "integer", "maximum": 9007199254740991, "minimum": 0, "description": "Zero-based index of the first camera to return, for paging. Defaults to 0." }, "region": { "type": "string", "maxLength": 200, "description": "WSDOT region code: NW (Northwest), SW (Southwest), OL (Olympic), ER (Eastern), SC (South Central), NC (North Central), OS (Oregon — the TripCheck cameras around Portland), or WA (airport cameras plus a few ferry-terminal cameras — most ferry-terminal cameras sit in NW and OL). Matching is case-insensitive; any other value is rejected. These are codes, not the region names wsdot_search_alerts takes." }, "stateRoute": { "type": "string", "maxLength": 200, "description": "State 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 is compared when the filter carries one too: \"SR 26\" excludes US 26, while a bare \"26\" returns both. A lettered suffix is part of the route, so \"US 97\" excludes US 97A. Omit to include all routes." }, "endMilepost": { "type": "number", "description": "End of the milepost range to filter cameras." }, "startMilepost": { "type": "number", "description": "Start of the milepost range to filter cameras. Either bound may be given alone; when both are given, startMilepost must not exceed endMilepost. Cameras reporting no milepost are always included." }, "titleContains": { "type": "string", "maxLength": 200, "description": "Words to find in the camera title, as WSDOT wrote it. Case-insensitive; every whitespace-separated word must appear, in any order — \"Snoqualmie\" returns \"Snoqualmie Summit\" and \"East Snoqualmie Summit\" but not a nearby camera titled \"Hyak\". Most titles lead with route and milepost (\"I-90 at MP 52: …\"), so filter a route with stateRoute rather than here. Combines with the other filters. Omit to include every title." } }, "additionalProperties": false }arguments 42 lineswsdot_get_toll_rates reads open 20h ago
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. A page ends at limit or at a 24,000-byte response budget, whichever comes first; the notice reports the next offset.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "maximum": 500, "minimum": 1, "description": "Maximum toll rates to return in this page (1–500). Defaults to 50. A large page ends sooner, at the 24,000-byte response budget." }, "offset": { "type": "integer", "maximum": 9007199254740991, "minimum": 0, "description": "Zero-based index of the first toll rate to return, for paging. Defaults to 0." }, "stateRoute": { "type": "string", "maxLength": 200, "description": "Tolled route to filter by. Accepts natural forms — \"SR 520\", \"520\", \"0520\", \"I-405\", \"405\" — matched case- and space-insensitively against each row's posted designation, so a route-type prefix must agree: \"SR 405\" matches nothing because the I-405 Express Lanes are an Interstate. A route with no tolled facility returns an empty page whose notice names the tolled routes. Omit to include every facility." } }, "additionalProperties": false }arguments 24 lineswsdot_get_terminal_space reads open 2h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "maximum": 20, "minimum": 1, "description": "Maximum terminals to return in this page (1–20). Defaults to 5. Counts terminals, not sailings." }, "offset": { "type": "integer", "maximum": 9007199254740991, "minimum": 0, "description": "Zero-based index of the first terminal to return, for paging. Defaults to 0." }, "departingTerminalId": { "type": "integer", "maximum": 9007199254740991, "description": "Filter to a specific terminal by numeric ID. Omit to return all terminals.", "exclusiveMinimum": 0 } }, "additionalProperties": false }arguments 25 lineswsdot_get_travel_times reads open 20h ago
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. A page ends at limit or at a 24,000-byte response budget, whichever comes first; the notice reports the next offset.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "maximum": 500, "minimum": 1, "description": "Maximum corridors to return in this page (1–500). Defaults to 50. A large page ends sooner, at the 24,000-byte response budget." }, "route": { "type": "string", "maxLength": 200, "description": "Optional 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 the corridor name as a case-insensitive substring, so \"Everett\" finds the Seattle-Everett corridors. Omit to return all corridors." }, "offset": { "type": "integer", "maximum": 9007199254740991, "minimum": 0, "description": "Zero-based index of the first corridor to return, for paging. Defaults to 0." } }, "additionalProperties": false }arguments 24 lineswsdot_get_mountain_passes reads open 2h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {}, "additionalProperties": false }arguments 6 lineswsdot_get_ferry_alerts reads open 17h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {}, "additionalProperties": false }arguments 6 lineswsdot_get_ferry_routes reads open 17h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "tripDate": { "type": "string", "description": "Date for which to list routes, in ISO 8601 format (YYYY-MM-DD). Defaults to today if omitted." } }, "additionalProperties": false }arguments 11 lineswsdot_search_alerts reads open 17h ago
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. A page ends at limit or at a 24,000-byte response budget, whichever comes first; the notice reports the next offset.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "maximum": 500, "minimum": 1, "description": "Maximum alerts to return in this page (1–500). Defaults to 20. A page of long alerts can end sooner, at the 24,000-byte response budget." }, "offset": { "type": "integer", "maximum": 9007199254740991, "minimum": 0, "description": "Zero-based index of the first alert to return, for paging. Defaults to 0." }, "region": { "type": "string", "maxLength": 200, "description": "WSDOT region name as it appears in alert data: \"Northwest\", \"Olympic\", \"Southwest\", \"South Central\", \"North Central\", or \"Eastern\". Matching is case-insensitive; any other value is rejected. These are names, not the two-letter codes wsdot_search_cameras takes." }, "stateRoute": { "type": "string", "maxLength": 200, "description": "State 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 sides carry one, so \"SR 26\" never matches US 26 while a bare \"26\" matches either. Omit to include all routes." }, "endMilepost": { "type": "number", "description": "End of the milepost range. Matched by extent overlap like startMilepost, so an alert beginning inside the range and continuing past it is returned." }, "startMilepost": { "type": "number", "description": "Start 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; when both are given, startMilepost must not exceed endMilepost. Alerts reporting no milepost are always included." } }, "additionalProperties": false }arguments 37 lineswsdot_get_ferry_terminals reads open 2h ago
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {}, "additionalProperties": false }arguments 6 lineswsdot_get_border_waits reads unknown never probed
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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {}, "additionalProperties": false }arguments 6 lineswsdot_get_ferry_schedule reads unknown 14h ago
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). 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 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.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "departingTerminalId", "arrivingTerminalId" ], "properties": { "tripDate": { "type": "string", "description": "Date in ISO 8601 format (YYYY-MM-DD). Defaults to today if omitted." }, "remainingOnly": { "type": "boolean", "description": "When true, returns only future sailings for today. Ignored for future dates. Default: false." }, "arrivingTerminalId": { "type": "integer", "maximum": 9007199254740991, "description": "Numeric ID of the arriving terminal.", "exclusiveMinimum": 0 }, "departingTerminalId": { "type": "integer", "maximum": 9007199254740991, "description": "Numeric ID of the departing terminal. Use wsdot_get_ferry_terminals to look up terminal IDs.", "exclusiveMinimum": 0 } }, "additionalProperties": false }arguments 31 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's iddf8a7278fcd76ca2.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/df8a7278fcd76ca2/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/df8a7278fcd76ca2?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- brapi.caseyjhand.com brapi-mcp-server
- usaspending.caseyjhand.com usaspending-mcp-server
- onebusaway.caseyjhand.com onebusaway-mcp-server
- secedgar.caseyjhand.com secedgar-mcp-server
- courtlistener.caseyjhand.com courtlistener-mcp-server
- openfda.caseyjhand.com openfda-mcp-server
- gbif-biodiversity.caseyjhand.com gbif-biodiversity-mcp-server
- openfec.caseyjhand.com openfec-mcp-server
101 more sit on this domain. All of them.