Home / MCP registry index / io.usefulapi/track-pod
Track-POD MCP by usefulapi
io.usefulapi/track-pod in the official MCP registry.
Endpoint https://track-pod.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Track-POD orders, routes, drivers, vehicles and proof of delivery; create orders.
We read its 16 tools on 2026-10-21. 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
trackpod_list_orders trackpod_list_orders_changed_since trackpod_list_route_orders trackpod_get_order trackpod_find_orders_by_number trackpod_get_proof_of_delivery trackpod_list_reject_reasons trackpod_list_routes trackpod_get_route trackpod_get_route_track trackpod_list_drivers trackpod_get_driver trackpod_list_vehicles trackpod_get_vehicle trackpod_list_vehicle_checks trackpod_create_order
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-track-pod)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.