Home / MCP registry index / io.usefulapi/farmbrite
Farmbrite MCP by usefulapi
io.usefulapi/farmbrite in the official MCP registry.
Endpoint https://farmbrite.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Farmbrite livestock, crops, tasks, inventory and orders; log records and tasks.
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 farmbrite https://farmbrite.usefulapi.io/mcp{
"mcpServers": {
"farmbrite": {
"url": "https://farmbrite.usefulapi.io/mcp"
}
}
}code --add-mcp '{"name":"farmbrite","type":"http","url":"https://farmbrite.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
farmbrite_list_animals farmbrite_get_animal farmbrite_list_livestock_groups farmbrite_get_livestock_group farmbrite_list_animal_measurements farmbrite_list_feedings farmbrite_list_grazing_summary farmbrite_list_plants farmbrite_list_crops farmbrite_get_crop farmbrite_list_plots farmbrite_get_plot farmbrite_list_harvests farmbrite_list_treatments farmbrite_list_notes farmbrite_list_contacts farmbrite_get_contact farmbrite_list_tasks farmbrite_get_task farmbrite_list_activities farmbrite_list_inventory_types farmbrite_get_inventory_type farmbrite_get_inventory_locations farmbrite_list_warehouses farmbrite_list_orders farmbrite_get_order farmbrite_list_transactions farmbrite_get_transaction farmbrite_create_contact farmbrite_update_contact farmbrite_create_task farmbrite_update_task farmbrite_create_transaction farmbrite_create_note farmbrite_add_inventory farmbrite_remove_inventory farmbrite_create_order farmbrite_update_order farmbrite_create_animal farmbrite_update_animal farmbrite_add_animal_measurement farmbrite_create_feeding farmbrite_create_harvest farmbrite_create_treatment
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):
fd9233f77af0aca4. 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-farmbrite)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.