Wrench.Pro Vehicle Check
REMOTE · MCP.WRENCH.PRO
Recalls, known issues, and honest maintenance costs for any US-market vehicle since 1990.
Available components
Last scanned (18 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 4 Nov 2026.
Category IoT and Hardware
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability41
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1086 tokens (~181/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.wrench.pro/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.wrench.pro | CN=YR2,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | RSA 2048 | SHA256-RSA | 6c32ef88c8cdcd3f6d55bf9b8e9fbdc7f7b |
| SANs: mcp.wrench.pro | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.wrench.pro. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 33289 | 8 | Verified |
| wrench.pro. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.wrench.pro/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.wrench.pro/mcp | HTTPS enforced | 308 | https://mcp.wrench.pro/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_known_issues Human-reviewed Known Issues (clustered owner complaints) ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Make slug from resolve_vehicle, e.g. 'ford'. |
| model | string | yes | Model slug from resolve_vehicle, e.g. 'f-150'. |
| year | string | yes | 4-digit model year from resolve_vehicle. |
Structured output declared, but exposes no named fields.
No examples provided.
get_maintenance Maintenance schedule with Dealer/Shop/DIY price ranges ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Make slug from resolve_vehicle, e.g. 'ford'. |
| mileage | integer | – | Current odometer miles, when the user mentioned it. |
| model | string | yes | Model slug from resolve_vehicle, e.g. 'f-150'. |
| year | string | yes | 4-digit model year from resolve_vehicle. |
Structured output declared, but exposes no named fields.
No examples provided.
get_recalls NHTSA recalls for a vehicle ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Make slug from resolve_vehicle, e.g. 'ford'. |
| model | string | yes | Model slug from resolve_vehicle, e.g. 'f-150'. |
| year | string | yes | 4-digit model year from resolve_vehicle. |
Structured output declared, but exposes no named fields.
No examples provided.
get_vehicle_summary Full vehicle report: recalls + known issues + maintenance ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | Make slug from resolve_vehicle, e.g. 'ford'. |
| mileage | integer | – | Current odometer miles, when the user mentioned it. |
| model | string | yes | Model slug from resolve_vehicle, e.g. 'f-150'. |
| year | string | yes | 4-digit model year from resolve_vehicle. |
| zip | string | – | 5-digit US ZIP code, only when the user mentioned one. |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_vehicle Resolve a vehicle to exact year/make/model ~159
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).
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | – | Make, if already known. |
| model | string | – | Model, if already known. |
| query | string | – | Free-text vehicle description, e.g. '2017 ford escape'. |
| year | string | – | 4-digit year, if already known. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Wrench.Pro Vehicle Check MCP server?
Wrench.Pro Vehicle Check is a hosted endpoint at https://mcp.wrench.pro/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.wrench.pro
claude mcp add --transport http pro-wrench-vehicle-check 'https://mcp.wrench.pro/mcp'
What is the Wrench.Pro Vehicle Check MCP server?
Wrench.Pro Vehicle Check is an MCP server listed in the public MCP registry as pro.wrench/vehicle-check. Recalls, known issues, and honest maintenance costs for any US-market vehicle since 1990. This page covers its hosted endpoint (https://mcp.wrench.pro/mcp).
Is the Wrench.Pro Vehicle Check MCP server safe to use?
Wrench.Pro Vehicle Check scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Wrench.Pro Vehicle Check MCP server expose?
Wrench.Pro Vehicle Check exposes 5 tools: resolve_vehicle, get_vehicle_summary, get_recalls, get_known_issues, get_maintenance. Their descriptions and schemas cost roughly 722 tokens of context every time the server is loaded.
Does the Wrench.Pro Vehicle Check MCP server require authentication?
No. We connected to Wrench.Pro Vehicle Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wrench.Pro Vehicle Check MCP server still maintained?
Wrench.Pro Vehicle Check is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.