Skip to main content
Glama
Sign In
TruckerFetch MCP

TruckerFetch MCP

Official
by truckerfetch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to TruckerFetch MCP

No user-submitted related servers found.

    Related Servers

    • mcp-fmcsa

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides keyless access to US FMCSA motor-carrier registry data, enabling lookup of DOT/MC numbers, names, operating authority, and safety information.
      311 npm
      1
      MIT

    • Bsoft TMS

      mcp-dir
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to read and write Brazilian carrier transportation management data, including fiscal documents (CT-e, MDF-e, NF-e), financial records, fleet and maintenance, trip control, and people registries via MCP over HTTP.
      MIT

    • B2B Compliance & Entity

      drewTuzson
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and compliance pipelines to run deterministic checks against FMCSA carrier authority, CMS NPI records, federal sanctions and exclusion lists, phone TCPA/DNC risk, SEC EDGAR, EU VAT, NHTSA VIN, and B2B email deliverability.
      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

    B3/5.0

    Scored across 22 tools

    Disambiguation3/5

    Most tools map to a distinct resource+action, but several pairs blur: `list_authorities` (authorities for one carrier) vs `list_authority_watch_targets` (resolved watch targets), `add_watch_target` (carrier) vs `add_authority_watch_target` (authority docket), and `get_latest_edition` vs `list_editions`, which both may publish due editions and queue notifications. The descriptions do disambiguate these, but the near-identical naming forces careful reading rather than instant selection.

    Naming Consistency5/5

    Every tool is snake_case verb_noun (get_/list_/search_/create_/add_/remove_/update_/request_/unlock_), including the export and watchlist families. The verb prefixes are used semantically consistently: get_ for single-object reads, list_ for collections, search_ for filtered queries.

    Tool Count3/5

    22 tools is on the heavy side for this domain; the editions, carriers/evidence, exports and watchlist families each legitimately need several operations, but the watchlist area alone carries seven tools. Some pruning (e.g. separate carrier-target vs authority-target addition, list_authority_watch_targets) would tighten the surface.

    Completeness4/5

    Core lifecycle is largely covered: editions (latest/list/unlock/search), carriers (search/profile/changes/authorities/insurance/renewals/evidence), exports (request/get state), and watchlists (create/get/list/rules/events). Gaps exist but are workable: no way to remove a plain carrier target from a watchlist (only authority targets have a remove_), no delete/rename watchlist, and no cancel for a pending export.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources