Check a specific vehicle for open NHTSA safety recalls, including glazing/windshield-camera/ADAS-related campaigns, before performing a calibration or glass replacement.
domain: api.nhtsa.gov · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call GET https://api.nhtsa.gov/recalls/recallsByVehicle?make={MAKE}&model={MODEL}&modelYear={YEAR} — free, no API key or auth required.
Read each recall's Component and Summary fields and filter client-side for glazing/windshield/camera/ADAS keywords; there is no server-side component filter on this endpoint.
If exact make/model/year values are unknown, first call api.nhtsa.gov/products/vehicle/modelYears?issueType=r, then .../makes?modelYear=...&issueType=r, then .../models?modelYear=...&make=...&issueType=r to enumerate valid values.
To pull full detail on one campaign already identified, call api.nhtsa.gov/recalls/campaignNumber?campaignNumber={NHTSA campaign number}.
Known gotchas
Recall search matches by Make/Model/ModelYear text, not VIN — the response does not include a VIN range, so you must still confirm the specific VIN is in the affected population.
There is no built-in 'component=glazing' filter; you must inspect the returned Component/Summary text yourself.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?