# Wrench.Pro Vehicle Check

> Recalls, known issues, and honest maintenance costs for any US-market vehicle since 1990.

- name: pro.wrench/vehicle-check
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 89/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/pro.wrench%2Fvehicle-check
- tools: https://api.protogrid.dev/v1/servers/pro.wrench%2Fvehicle-check/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "vehicle-check": {
      "type": "http",
      "url": "https://mcp.wrench.pro/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-17d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 89/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_known_issues (destructiveHint, idempotentHint, openWorldHint); get_maintenance (destructiveHint, idempotentHint, openWorldHint); resolve_vehicle (destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,119 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 5 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 1,119 tokens to load them all
- tool set hash: 2a631f269fb81e94ed655a411582540d
- tools last changed: 2026-10-03T21:24:16.862Z
- badge: [![protogrid quality](https://protogrid.dev/badge/pro.wrench/vehicle-check.svg)](https://protogrid.dev/servers/pro.wrench/vehicle-check)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-03 `get_maintenance` changed (annotations)
- 2026-10-03 `get_known_issues` changed (annotations)
- 2026-10-03 `get_recalls` changed (annotations)
- 2026-10-03 `get_vehicle_summary` changed (annotations)
- 2026-10-03 `resolve_vehicle` changed (annotations)

Full history: https://api.protogrid.dev/v1/servers/pro.wrench%2Fvehicle-check/changes

## Remotes

- https://mcp.wrench.pro/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (5)

- `get_known_issues`: 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.
- `get_maintenance`: 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.
- `get_recalls`: 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.
- `get_vehicle_summary`: 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.
- `resolve_vehicle`: 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).