A
licenseNot graded
qualityC
maintenanceEnables natural-language queries over U.S. vehicle records, including recalls, service bulletins, diagnostic trouble codes, VIN decoding, fuel economy, and crash ratings.
1
MIT
Wrench.Pro Vehicle Check
by pro.wrench
Server Details
Recalls, known issues, and honest maintenance costs for any US-market vehicle since 1990.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
A4.1/5.0
Scored across 5 tools
Disambiguation4/5
Each tool targets a distinct concern: known issues, maintenance, recalls, broad summary, and vehicle resolution. The only overlap is get_vehicle_summary, which handles broad questions like 'what goes wrong with it' that also fall under get_known_issues, but the descriptions clarify that summary is the catch-all and the others are specific queries.
Naming Consistency4/5
Four tools follow a clean get_noun snake_case pattern (get_known_issues, get_maintenance, get_recalls, get_vehicle_summary). resolve_vehicle deviates with a different verb, but the action is genuinely distinct (turning free text into slugs) and still snake_case, so the set remains predictable.
Tool Count4/5
Five tools is a tight, well-scoped surface for a vehicle-info domain with no obvious filler or redundancy. It sits at the lower end of the comfortable 3-15 range, which is reasonable given the narrow read-only scope.
Completeness4/5
The surface covers the core read-only lifecycle: resolve a vehicle, then pull issues, maintenance, recalls, and a summary, plus a mandated disclaimer path for recalls. Minor gaps exist (no standalone VIN decoder or shop-locator tool), but users can work around these via the summary card and external links.
Available Tools
5 toolsget_known_issuesHuman-reviewed Known Issues (clustered owner complaints)ARead-onlyInspect
Use when the user asks what commonly goes wrong, about reliability, or about a specific symptom. mode='reviewed' is Wrench.Pro's human-reviewed analysis — cite it. mode='raw' means no review yet: say 'no reviewed Known Issues yet' and present rawTopComponents. mode='none': say there's no complaint data. Never invent issues.
Inputs: make (required), year (required), model (required). Returns: object
get_maintenanceMaintenance schedule with Dealer/Shop/DIY price rangesARead-onlyInspect
Use when the user asks about service intervals, what's due, or what a service should cost. Pass mileage when known. Ranges are estimates and marked approximate — present them that way. 'Pro only' means the job isn't realistic DIY: recommend a shop instead of giving repair instructions.
Inputs: make (required), year (required), model (required), mileage. Returns: object
get_recallsNHTSA recalls for a vehicleARead-onlyInspect
Use when the user asks specifically about recalls or safety campaigns. Requires exact slugs from resolve_vehicle. Always tell the user to confirm against their own VIN at nhtsa.gov/recalls before acting on safety issues.
Inputs: make (required), year (required), model (required). Returns: object
get_vehicle_summaryFull vehicle report: recalls + known issues + maintenanceARead-onlyInspect
Use for broad questions about a vehicle ('should I buy it', 'what goes wrong with it', 'tell me about it'). Requires exact slugs from resolve_vehicle. Pass mileage when the user mentioned their odometer to get due-now service items, and zip when the user mentioned a US ZIP code so the card can link nearby shops. End your answer with the canonical Wrench.Pro link and the attribution line from the result.
Inputs: make (required), year (required), model (required), zip, +1 more. Returns: object
resolve_vehicleResolve a vehicle to exact year/make/modelARead-onlyInspect
Use FIRST whenever the user names a vehicle ('2017 Ford Escape', "'17 F150", 'my Honda Civic') unless you already have exact slugs from a previous call. Pass the user's words in query. Returns kind=exact (use the returned slugs), suggest (ask the user to confirm one), needsYear (ask ONE question listing availableYears), needsModel, or notFound (say Wrench.Pro doesn't cover it — never guess).
Inputs: make, year, model, query. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
US vehicle recalls, complaints, EPA figures, VIN decode and trouble codes, with sources.
Vehicle safety recalls, complaints, and crash data from NHTSA
US vehicle safety from NHTSA: recalls, owner complaints, crash-test ratings and VIN checks
Mechanic-grade used-car listing verdicts: risk score, failure points, repair costs, fair price.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables instant U.S. vehicle recall lookup by make, model, and year using official NHTSA data.MIT
- AlicenseAqualityBmaintenanceDecode VINs, look up specs, history, recalls, market value, and OBD codes. Recognize license plates and VINs from images. Access comprehensive vehicle data by year, make, and model to power automotive workflows.121MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying U.S. vehicle safety and specification data, including VIN decoding, recalls, complaints, investigations, and crash test ratings.335 npmMIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.