Wenmar Open

Free VIN decoder and vehicle catalog from NHTSA vPIC data. Read-only, no key.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
85%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~480Tokens (tool definitions)
~1.1 KBTypical response size
Minimal attention impact (0.38% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "wenmar-open": {
      "url": "https://open.wenmarpro.com/mcp"
    }
  }
}

Remote endpoints

https://open.wenmarpro.com/mcpstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢wenmar_vin(action, vin, vins, year)

Decode vehicle identification numbers into year, make, model, trim, engine, drivetrain, safety equipment and the matching catalog entry. action=decode takes `vin` (and optionally `year` to override the model year). action=batch takes `vins`, at most 50, and returns one result per VIN in order. A wrong check digit is not an error: the result has valid=false and a warning.

Input Schema

{
  "type": "object",
  "properties": {
    "action": {
      "enum": [
        "decode",
        "batch"
      ],
      "type": "string"
    },
    "vin": {
      "description": "A 17-character VIN. Spaces and dashes are ignored.",
      "type": "string"
    },
    "vins": {
      "items": {
        "type": "string"
      },
      "maxItems": 50,
      "type": "array"
    },
    "year": {
      "description": "Model year to use instead of the one worked out from the VIN.",
      "type": "integer"
    }
  },
  "required": [
    "action"
  ]
}
🟢wenmar_vehicles(action, id, limit, make, model, ...)

Look up vehicles by year, make, model, submodel and engine. Actions: years; makes (optional `year`); models (`make`, optional `year`); submodels (`make`, `model`, `year`); engines (`make`, `model`, `year`, optional `submodel`); search (`query`, such as "2019 civic si" or "chevy 1500"); entry (`id`, such as "2019_honda_civic_si"). `make` and `model` take a name, an alias or an id. `term` narrows a list to names starting with it. `scope` is light (cars, MPVs and trucks; the default), all, or a vPIC vehicle type id.

Input Schema

{
  "type": "object",
  "properties": {
    "action": {
      "enum": [
        "years",
        "makes",
        "models",
        "submodels",
        "engines",
        "search",
        "entry"
      ],
      "type": "string"
    },
    "id": {
      "type": "string"
    },
    "limit": {
      "type": "integer"
    },
    "make": {
      "type": "string"
    },
    "model": {
      "type": "string"
    },
    "query": {
      "type": "string"
    },
    "scope": {
      "type": "string"
    },
    "submodel": {
      "type": "string"
    },
    "term": {
      "type": "string"
    },
    "year": {
      "type": "integer"
    }
  },
  "required": [
    "action"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools