Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Wrench.Pro Vehicle Check is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Recalls, known issues, and honest maintenance costs for any US-market vehicle since 1990.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http wrench-pro-vehicle-check-mcp https://mcp.wrench.pro/mcp
# 2 — ask your agent for something these tools do
# resolve_vehicle, get_vehicle_summary, get_recalls and 2 more
Wrench.Pro Vehicle Check costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
WRAll 1 server
wrench1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http wrench-pro-vehicle-check-mcp https://mcp.wrench.pro/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free-text vehicle description, e.g. '2017 ford escape'. |
| year | string | no | 4-digit year, if already known. |
| make | string | no | Make, if already known. |
| model | string | no | Model, if already known. |
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 r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | string | yes | 4-digit model year from resolve_vehicle. |
| make | string | yes | Make slug from resolve_vehicle, e.g. 'ford'. |
| model | string | yes | Model slug from resolve_vehicle, e.g. 'f-150'. |
| mileage | integer | no | Current odometer miles, when the user mentioned it. |
| zip | string | no | 5-digit US ZIP code, only when the user mentioned one. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | string | yes | 4-digit model year from resolve_vehicle. |
| make | string | yes | Make slug from resolve_vehicle, e.g. 'ford'. |
| model | string | yes | Model slug from resolve_vehicle, e.g. 'f-150'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | string | yes | 4-digit model year from resolve_vehicle. |
| make | string | yes | Make slug from resolve_vehicle, e.g. 'ford'. |
| model | string | yes | Model slug from resolve_vehicle, e.g. 'f-150'. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | string | yes | 4-digit model year from resolve_vehicle. |
| make | string | yes | Make slug from resolve_vehicle, e.g. 'ford'. |
| model | string | yes | Model slug from resolve_vehicle, e.g. 'f-150'. |
| mileage | integer | no | Current odometer miles, when the user mentioned it. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Wrench.Pro Vehicle Check or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Wrench.Pro Vehicle Check can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.