TruckerFetch MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRUCKERFETCH_API_KEY | Yes | Narrowly scoped TruckerFetch REST API key (`tf_…`) used by the local stdio bridge to call https://truckerfetch.com/api/v1. Load it securely into the process environment; do not commit real keys in client JSON. | |
| TRUCKERFETCH_ALLOW_LOCAL_TEST | No | Set to 1 only to allow loopback HTTP for local fixtures. Leave unset in normal use. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_latest_editionA | Get the latest published carrier edition and its source date. May publish already-due daily editions and queue their normal opt-in notifications using the server clock (at most 32 dates per call). |
| list_editionsB | List published editions in the rolling 90 Eastern calendar dates, plus the latest during a source delay, without spending an archive unlock. May publish already-due daily editions and queue their normal opt-in notifications using the server clock (at most 32 dates per call). |
| search_carriersB | Search the published carrier catalog with state, classification and fleet filters. |
| search_editionB | Search the latest edition or a previously unlocked edition still within the rolling 90 Eastern calendar dates. Expired editions return archive_expired. |
| get_carrierB | Read an authorized carrier's published profile by USDOT. |
| list_changesC | Read published material changes for one visible carrier. |
| list_authoritiesC | List published operating authorities for one carrier. |
| list_insurance_filingsC | List observed insurance filings and independently supported dates. |
| search_renewalsC | Search approved policy evidence by the requested date basis. |
| get_evidenceC | Read the redacted source reference for an authorized fact. |
| list_watchlistsA | List your own carrier watchlists. |
| get_watchlistB | Read an owned watchlist and its visible carrier IDs. |
| list_authority_watch_targetsB | List the exact resolved authorities followed by this watchlist. |
| add_authority_watch_targetA | Follow one evidence-backed authority in an owned watchlist. Confirm the docket and authority type with the user first. The local REST bridge additionally requires confirm_action=true after user approval. |
| remove_authority_watch_targetA | Remove a specific authority target from an owned watchlist after confirming the target with the user. The local REST bridge additionally requires confirm_action=true after user approval. |
| update_watch_rulesB | Pause or resume an owned watchlist or change its future matched event types. Confirm the change with the user. The local REST bridge additionally requires confirm_action=true after user approval. |
| list_watch_eventsC | Read published events matching the watch targets and current permissions. |
| create_watchlistB | Create a named watchlist for the current owner. Confirm the requested name with the user before invoking. The local REST bridge additionally requires confirm_action=true after user approval. |
| add_watch_targetB | Add a carrier to an owned watchlist. The local REST bridge additionally requires confirm_action=true after user approval. |
| request_exportA | Request a pinned CSV export. Follow the owner approval link and repeat with the same key. The local REST bridge additionally requires confirm_action=true after user approval. |
| unlock_editionA | Request explicit owner confirmation to open a date within the rolling 90 Eastern calendar dates. The latest published edition is included; an expired date cannot be reopened. The local REST bridge additionally requires confirm_action=true after user approval. |
| get_exportC | Read the state of your own export. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Field definitions | |
| Supported carrier filters |
TDQS
Scored across 22 tools
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.
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.
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.
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.