Skip to main content
Glama
joakes90

vin-decode-mcp

by joakes90

Related Servers

Alternatives to vin-decode-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to decode VINs, check stolen vehicle databases, and retrieve market valuations through natural language.
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides comprehensive vehicle reports by aggregating data from multiple public sources to decode VINs, check recalls, and view safety ratings. It enables users to validate VINs locally and retrieve technical specifications, fuel economy, and vehicle photos without requiring API keys.
      5 npm
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables access to comprehensive vehicle information including VIN decoding, license plate OCR, vehicle history checks (theft, title, salvage records), market valuations, specifications, and warranty data for vehicles across North America and Europe.
      61
      1
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Exposes a connected-vehicle OBD-II/telematics platform to AI agents, enabling vehicle health scoring, live data queries, DTC decoding, maintenance prediction, and gated remote commands via a pluggable data layer.
      9
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural-language querying of NHTSA vehicle safety data, including VIN decoding, recall searches, consumer complaints, crash-test ratings, and defect investigations via MCP.
      79 npm
      1
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action: decode_* covers VIN/WMI decoding, get_* covers lookup tables. The only potential confusion is between decode_vin and decode_partial_vin, since decode_vin already accepts short VINs, though the wildcard/pattern use case is explicitly distinguished.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern starting with decode_ or get_, and resource nouns are used predictably. The naming makes the set easy to scan and understand.

    Tool Count5/5

    Eight tools is well-scoped for a VIN decoding and vehicle reference server. Each lookup tool has a clear purpose and the count is neither too sparse nor bloated.

    Completeness5/5

    The server covers the core VIN decode workflow (full and wildcard partial VINs, WMI info) and the supporting reference queries needed to explore makes, models, model years, and vehicle types. There are no obvious dead ends for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues