Home / MCP registry index / io.github.warpfreight/warp-agent-mcp
io.github.warpfreight/warp-agent-mcp
io.github.warpfreight/warp-agent-mcp in the official MCP registry.
Endpoint https://mcp.wearewarp.com/api/mcp. Source: github.com/warpfreight/warp-agent-mcp.
The registry describes it as: Quote, book, and track LTL, FTL, cargo van, and box-truck freight via the Warp API.
We read its 37 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
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
freight_workflow compare_freight_costs van_quote box_truck_quote ftl_quote ltl_quote ltl_market_options compare_modes batch_quote book parcel_quote parcel_book batch_book multistop_quote multistop_book track lane_history list_bookings status events get_invoice get_documents quote_history login consolidate shipper_profile automate_lane manage_automation automation_receipts payment_status report_issue analytics price_check locations load_templates save_load_template delete_load_template
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-warpfreight-warp-agent-mcp)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.