Home / MCP registry index / com.fromtocargo/mcp
com.fromtocargo/mcp
com.fromtocargo/mcp in the official MCP registry.
Endpoint https://mcp.fromtocargo.com/mcp. Source: github.com/coservices-ee/fromtocargo-mcp.
The registry describes it as: European road freight and moving prices: quotes, dated price index, glossary, order submission
We read its 19 tools on 2026-10-27. 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
search_routes get_route estimate_price list_countries get_cargo_tariff estimate_cargo_price get_pricing_rules get_terms list_languages get_company_info get_services get_faq get_price_index get_glossary get_pricing_methodology estimate_by_rooms estimate_by_items get_route_content create_inquiry
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-fromtocargo-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.