Skip to main content
Glama
sovorn-c

Vehicle Intelligence MCP Server

by sovorn-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Vehicle Intelligence MCP Server

No user-submitted related servers found.

    Related Servers

    • openvehicle-data

      mirkobechini
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only access to open, verified vehicle brand, model, and specification data (Italy first, later EU) through MCP tools, enabling AI agents and apps to query the dataset programmatically.
      1
      Apache 2.0

    • used-parts-mcp

      neko-no-otoko
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching current used car, truck, and motorcycle parts in the US, resolving vehicles via VIN, and retrieving part listings with source attribution, through read-only MCP tools.
      Apache 2.0

    • ECRVSP Veículos: Cadastro BIN

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying vehicle registration information (BIN RENAVAM) from the official ECRVSP source. Read-only, prepaid per use, works with any MCP client.
      MIT

    • ECRVSP Processos: Imprimir

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying the official Brazilian vehicle registration (CRLV-e) system with a single read-only tool. Works with any MCP client, featuring prepaid pay-per-use pricing.
      MIT

    • nhtsa-recalls-mcp

      chucks-lab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to look up US vehicle-safety data read-only — decoding VINs, and retrieving recalls, owner complaints, and 5-Star NCAP safety ratings by make, model, and year through NHTSA's public APIs.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role: browsing, current lookup, revision history, exact revision, raw observation, and field explanation. The closest pair is lookup_vehicle and get_vehicle_revision, but their current-vs-immutable distinction is clear from descriptions.

    Naming Consistency4/5

    Names follow a mostly consistent verb_noun snake_case pattern with list_* for collections and get_* for individual records. lookup_vehicle breaks the get_* convention slightly, but it is still readable and predictable.

    Tool Count5/5

    Six tools is well within the ideal range and each tool addresses a distinct part of vehicle intelligence. The set feels neither thin nor bloated.

    Completeness4/5

    The read-only workflow is well covered: discover vehicles, retrieve current and historical canonical states, fetch raw evidence, and explain field outcomes. A minor gap is the lack of a way to enumerate source observations for a vehicle directly rather than by known observation ID.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources