# io.github.nicglazkov/commutescout (remote · mcp.commutescout.com)

Live California road conditions: CHP incidents, Caltrans closures, chain controls, and wildfires.

- Trust score: 64/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.commutescout.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/nicglazkov-commutescout/mcp.md), [page](https://verifymcp.io/servers/nicglazkov-commutescout/mcp)

## Channel facts

- Endpoint: `https://mcp.commutescout.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.24.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2792 tokens (~279/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http nicglazkov-commutescout https://mcp.commutescout.com/mcp
```

### Codex

```toml
[mcp_servers.nicglazkov-commutescout]
url = "https://mcp.commutescout.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nicglazkov-commutescout": {
      "type": "remote",
      "url": "https://mcp.commutescout.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nicglazkov-commutescout --url https://mcp.commutescout.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nicglazkov-commutescout:
    url: "https://mcp.commutescout.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "nicglazkov-commutescout": {
      "type": "http",
      "url": "https://mcp.commutescout.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +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.

### 2026-08-01 (score 63, +1)

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

### 2026-07-31 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 61, +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.

### 2026-07-28 (score 60, +1)

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

### 2026-07-27 (score 59, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (10)

### `check_route` (~362 tokens)

Check current conditions along a major California highway corridor.

    The flagship trip-check tool: give it a start and end place and it
    returns everything active along that stretch right now - CHP incidents,
    lane closures physically in place, chain controls, and wildfires within
    ~10 miles - ordered by miles from the start, plus a summary.

    ALWAYS pass from_coords and to_coords ("lat,lon") when you know where
    the places are - for landmarks, small towns, or anything not a major
    city they are required for a good answer. Coordinates do two things:
    they let unlisted places resolve to the nearest corridor (e.g. "Alice's
    Restaurant" snaps to I-280 on the Peninsula), and they CLIP the route to
    the span actually being driven, so a trip to a mid-corridor destination
    doesn't report events beyond it.

    Corridors covered: I-80 Sacramento-Reno, US-50 to South Lake Tahoe, I-5,
    US-101, SR-17, SR-99, SR-1, I-15 to Vegas, Bay Area freeways, Tahoe-area
    routes. This is NOT a general router: if nothing matches (even with
    coordinates), the response lists the covered corridors; fall back to the
    filtered tools with center= for anything else.

    Freshness: CHP incidents refresh about once a minute; closures, chain
    controls, and fires are on a 5-minute cache. Current conditions only -
    this cannot forecast tomorrow's weather or closures.

Input parameters:

- `from_coords`
- `from_place` (string, required)
- `to_coords`
- `to_place` (string, required)

### `check_region` (~192 tokens)

Full current-conditions report for a California region.

    Use this for area-scale questions ("how is the Bay Area?", "what's
    happening in SoCal?") instead of stitching together point queries. It
    sweeps every source over the whole region at once: CHP incidents
    (severity-sorted, worst first), lane closures in place (full closures
    called out), chain controls, and wildfires inside the region.

    Regions: Bay Area, Sacramento metro, Tahoe/Sierra, Central Valley,
    Southern California, San Diego, Central Coast, North State. An
    unrecognized region name returns the list.

    Large regions are capped to the most severe items; the counts are
    always exact and the response says when a list was truncated.
    Freshness: CHP ~1/min fetched live, everything else 5-minute cache.

Input parameters:

- `region` (string, required)

### `get_incidents` (~346 tokens)

Live CHP traffic incidents statewide, optionally filtered.

    Data: the California Highway Patrol statewide computer-aided dispatch
    feed - collisions, traffic hazards, disabled vehicles, closures as CHP
    logs them. Refreshes about once a minute; incidents disappear when CHP
    closes the log. Fetched live on every call.

    Filters (combinable):
    - highway: a route like "I-80", "US 50", "17", "Hwy 99". Matches
      incidents whose location text mentions that route.
    - center: "lat,lon" with radius_km - incidents within that circle. THIS
      IS THE RIGHT FILTER FOR A TOWN OR PLACE NAME: use your knowledge of
      where the place is (e.g. Coyote, CA -> "37.22,-121.74") with radius_km
      15-30. A circle catches every road around the place, not just one
      highway.
    - area: substring match on the CHP dispatch-area name. These are CHP
      communication-center names ("Hollister Gilroy", "East Sac", "Golden
      Gate"), NOT town names - do not pass a town here. There is no county
      filter because CHP's feed carries no county field; for a county, use
      center on the county seat with a radius covering the county.

    Limits: locations are free-text from dispatchers; a few incidents lack
    usable coordinates and are omitted. No history - current logs only.

Input parameters:

- `area`
- `center`
- `highway`
- `radius_km` (number)

### `get_lane_closures` (~413 tokens)

Caltrans lane and road closures physically in place RIGHT NOW.

    Data: the Caltrans Lane Closure System (LCS). Only closures that crews
    have actually established (CHP code 1097) and not yet picked up are
    returned - scheduled-but-not-started closures are excluded, so this is
    "what is blocking lanes now", not a construction calendar.
    Refresh: 5-minute cache over per-district Caltrans feeds.

    Filters: route (e.g. "I-80", "US 101", "1"); district (Caltrans district
    1-12, e.g. 3 = Sacramento/Tahoe, 4 = Bay Area, 7 = Los Angeles);
    center "lat,lon" with radius_km - closures whose begin or end point is
    inside the circle. For a town or place, center is the filter that
    catches work on EVERY road around it, including small state routes.

    Read closure_class on each record, it is what the closure means for
    through traffic:
    - "full-roadway": the road itself is closed in that direction. The only
      class that means "you can't drive through".
    - "ramp": a ramp or connector is closed (even when the raw record says
      "Full", that means the ramp is fully closed, not the highway).
    - "one-way-traffic": alternating single lane with flagging; passable
      with delays. Common on two-lane mountain roads.
    - "alternating-lanes", "moving", "traffic-break": rolling or brief work;
      minor delays.
    - "lane": some lanes closed; the lanes field says how many of how many.
    estimated_delay_minutes is present when crews reported one.
    Shoulder-only work is excluded entirely.

Input parameters:

- `center`
- `district`
- `radius_km` (number)
- `route`

### `get_chain_controls` (~251 tokens)

Current chain-control requirements on California mountain highways.

    Data: Caltrans chain-control status for fixed checkpoints on mountain
    routes (I-80 Donner, US-50 Echo Summit, SR-88, SR-89, and others).
    Levels: R-1 = chains OR snow tires required; R-2 = chains required
    except 4WD/AWD with snow tires on all four; R-3 = chains on ALL vehicles
    (rare, usually precedes closure). Refresh: 5-minute cache.

    Filters: route (e.g. "80", "US-50", "SR-88"); center "lat,lon" with
    radius_km for all checkpoints around a place (e.g. around Truckee),
    whatever highway they are on.

    Off-season (roughly May-October) there are usually no controls anywhere;
    the response says so explicitly rather than returning an empty list.
    Chain requirements can change hour to hour in storms - tell the user the
    data_as_of time and to carry chains anyway when snow is possible.

Input parameters:

- `center`
- `radius_km` (number)
- `route`

### `get_wildfires` (~296 tokens)

Active California wildfires, flagged when close to a major highway.

    Data: the interagency WFIGS current-wildfire feed (NIFC) - name, size in
    acres, percent contained, discovery date. Points are each fire's ORIGIN,
    not its perimeter: a large fire can affect roads far from this point.
    Refresh: 5-minute cache; size/containment typically update once or twice
    a day. Small, fast-moving local fires may appear in CHP incident logs
    (get_incidents, type "FIRE-Report of Fire") before this feed has them.

    Filters:
    - near_route (e.g. "I-5", "101") - only fires within ~10 miles of that
      highway's corridor line.
    - center "lat,lon" with radius_km - fires around a place, regardless of
      highway.
    Without either, every active CA fire is returned, each carrying a
    `near_highways` list of major corridors within ~10 miles (empty = not
    near a covered major highway; it may still affect local roads).

    This tool does NOT know about road closures caused by fires - cross-check
    get_incidents and get_lane_closures for the affected area.

Input parameters:

- `center`
- `near_route`
- `radius_km` (number)

### `rank_routes` (~172 tokens)

Which major corridors have the most going on right now.

    Answers broad questions like "what are the busiest routes", "where is
    traffic worst", or "which highways should I avoid today" across all 17
    tracked corridors. by="activity" ranks on live events (full closures
    weigh most, then incidents, lane closures, chain controls);
    by="congestion" ranks on measured speed vs free-flow at each
    corridor's midpoint and needs the traffic feed to be configured -
    if it is not, the ranking silently falls back to activity.

    Each entry carries the counts and a one-line reason, so the answer
    can say WHY a corridor ranks where it does, not just list names.

Input parameters:

- `by` (string)
- `limit` (integer)

### `get_cameras` (~203 tokens)

Live Caltrans roadside camera snapshots near a point or on a route.

    Data: ~3,000 in-service Caltrans cameras statewide. Every returned
    image_url was verified live moments ago (offline cameras that serve a
    placeholder frame are filtered out), so images can be shown directly.
    Snapshots refresh roughly every minute; stream_url (when present) is
    an HLS video stream.

    Filters: center "lat,lon" (required unless route is given) with
    radius_km; route (e.g. "I-80", "50") narrows to that highway. Results
    sort nearest-first when a center is given. Use a camera to let the
    user SEE conditions: fog on the pass, snow on the pavement, traffic
    density at an interchange.

Input parameters:

- `center`
- `limit` (integer)
- `radius_km` (number)
- `route`

### `get_road_signs` (~185 tokens)

What Caltrans changeable message signs are displaying right now.

    Data: statewide CMS sign text, blank and out-of-service signs already
    filtered - every record is a message a driver is physically seeing.
    Signs carry the road's operational truth ("CHAINS REQUIRED 10 MI
    AHEAD", "FULL CLOSURE HWY 96 DUE TO FIRE", "PREPARE TO STOP"), often
    before the event shows up in any other feed. Refresh: ~2-minute cache.

    Filters: route (e.g. "I-80") and/or center "lat,lon" with radius_km.
    Quote sign text verbatim to the user - it is the most current and
    most local signal this server has.

Input parameters:

- `center`
- `radius_km` (number)
- `route`

### `get_nearby_events` (~256 tokens)

Live road events near a point anywhere CommuteScout covers, not
    just California: 32 states today, growing.

    Data: the same multi-state feeds the live map shows, normalized -
    state DOT incidents, roadwork and closures, chain and traction
    advisories, and nationwide wildfires. Every event names its
    publishing agency in the source field. Coverage varies by state
    (some publish roadwork only; docs/state-coverage.md has the
    matrix); states added later appear here automatically.

    For CALIFORNIA questions prefer the dedicated tools above (richer
    detail: dispatch logs, lane counts, chain levels). Use THIS tool
    for any location outside California, near a state border, or as a
    supplement when a California tool comes back empty.

    center is "lat,lon". kinds is a comma list from: incident, closure,
    chain, fire, sign, rwis, camera, toll (toll adds live and fixed
    toll prices where agencies publish them). radius_km caps at 160.

Input parameters:

- `center` (string, required)
- `kinds` (string)
- `radius_km` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nicglazkov-commutescout/mcp#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 62
- 2026-07-30: 61
- 2026-07-29: 61
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 59

## Links

- Remote endpoint: https://mcp.commutescout.com/mcp
- Repository: https://github.com/nicglazkov/commutescout
- Changelog RSS feed: https://verifymcp.io/servers/nicglazkov-commutescout/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/nicglazkov-commutescout/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/nicglazkov-commutescout/mcp