Monterey-Salinas Transit (MST)

Top things to fix

Score by category

Over time

Overall score across the last 20 checks — down 0.3 since 2026-07-08.

What changed since your last check

• Correctness— no change
• Freshness▼ down 1.7
• Rider experience— no change
• Realtime quality— no change

What changed in this feed

Overall score fell 0.3 points since 2026-07-08.

Same feed file as 2026-07-08; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

What changed over time

On 2026-06-19 this feed started at grade D. On 2026-06-23 the grade moved from D to C. On 2026-06-30 the grade moved from C to D. On 2026-06-23 it cleared service_window_outside_feed_period, stop_without_stop_time. As of 2026-07-09 it holds grade D.

A plain-language history of this feed, newest first.

• 2026-06-30 Grade went C to D.
• 2026-06-23 Grade went D to C, correctness rose 5 points.

Everything we checked

• Error1 instance

  The trip updates realtime feed failed during sampling.

  When this feed is down, riders see scheduled times presented as if they were live.

  Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)

  Agencies here usually clear this within about 1 week (based on 11 observed fixes).

  Validator rule: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)

• Error1 instance

  The vehicle positions realtime feed failed during sampling.

  When this feed is down, riders see scheduled times presented as if they were live.

  Fix: Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)

  Agencies here usually clear this within about 1 week (based on 9 observed fixes).

  Validator rule: scorecard_rt_vehicle_positions_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)

• Error1 instance

  The service alerts realtime feed failed during sampling.

  When this feed is down, riders see scheduled times presented as if they were live.

  Fix: Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)

  Agencies here usually clear this within about 1 week (based on 5 observed fixes).

  Validator rule: scorecard_rt_service_alerts_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)

• Warning3267 instances

  3267 of 3267 trips don't say whether the vehicle is wheelchair accessible.

  Even with accessible stops, riders need to know the bus itself can take them.

  Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)

  Agencies here usually clear this within about 1 week (based on 5 observed fixes).

  Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

• Warning975 instances

  975 of 975 stops don't say whether a wheelchair user can board there.

  Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

  Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

  Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

• Warning43 instances

  43 of 43 trips scheduled during the sampling window had no live predictions.

  Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.

  Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)

  Agencies here usually clear this within about 1 week (based on 82 observed fixes).

  Validator rule: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

• 946 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Del Monte Center / Gate 1", "Del Monte Center / Gate 2", "Del Monte Center / Gate 3", and more).

  Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Some fixes we can make for you

These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.

• Trimmed surrounding whitespace 924 changes

  For example: 'stop_lat': ' 36.584630' -> '36.584630'

Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip