Home / MCP registry index / io.usefulapi/fleetio
Fleetio MCP by usefulapi
io.usefulapi/fleetio in the official MCP registry.
Endpoint https://fleetio.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Fleetio vehicles, work orders, service, issues, inspections, fuel, parts; log issues, meters.
We read its 44 tools on 2026-10-31. 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.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http fleetio https://fleetio.usefulapi.io/mcp{
"mcpServers": {
"fleetio": {
"url": "https://fleetio.usefulapi.io/mcp"
}
}
}code --add-mcp '{"name":"fleetio","type":"http","url":"https://fleetio.usefulapi.io/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
fleetio_list_accounts fleetio_list_vehicles fleetio_list_vehicle_meter_entries fleetio_list_meter_entries fleetio_list_vehicle_assignments fleetio_list_equipment fleetio_list_work_orders fleetio_list_service_entries fleetio_list_vehicle_service_entries fleetio_list_service_reminders fleetio_list_issues fleetio_list_faults fleetio_list_inspection_forms fleetio_list_submitted_inspections fleetio_list_fuel_entries fleetio_list_parts fleetio_list_part_stock fleetio_list_contacts fleetio_list_vendors fleetio_list_vehicle_renewal_reminders fleetio_list_comments fleetio_list_vehicle_statuses fleetio_list_vehicle_types fleetio_list_work_order_statuses fleetio_list_issue_priorities fleetio_list_groups fleetio_list_labels fleetio_list_service_tasks fleetio_list_places fleetio_get_vehicle fleetio_get_equipment fleetio_get_work_order fleetio_get_service_entry fleetio_get_part fleetio_get_contact fleetio_get_vendor fleetio_get_submitted_inspection fleetio_get_inspection_form fleetio_get_issue fleetio_list_work_order_line_items fleetio_list_service_entry_line_items fleetio_create_issue fleetio_create_meter_entry fleetio_add_comment
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-10-31):
9e4568ea62d7cebd. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-fleetio)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.