Home / MCP registry index / com.freightfa.mcp/freightfa
FreightFA
com.freightfa.mcp/freightfa in the official MCP registry.
Endpoint https://mcp.freightfa.com/mcp.
The registry describes it as: Freight rate benchmarks (truckload, LTL, rail, intermodal, barge), market outlooks, FMCSA checks.
We read its 27 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_freight_brief estimate_truckload_rate estimate_ltl_rate estimate_rail_rate estimate_intermodal_rate estimate_barge_rate recommend_mode ask_freight_analyst get_market_snapshot get_market_outlook get_rail_market_outlook get_freight_index_outlook get_barge_outlook lookup_carrier find_intermodal_hubs explain_freight_term get_freight_news calculate_margin check_freight_bill draft_pushback_email create_rfp list_rfps get_rfp estimate_network_cost list_rate_alerts create_rate_alert list_recent_searches
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-freightfa-mcp-freightfa)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.