Home / MCP registry index / io.usefulapi/veeqo
Veeqo MCP by usefulapi
io.usefulapi/veeqo in the official MCP registry.
Endpoint https://veeqo.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read Veeqo orders, products, stock, warehouses, customers and POs; add notes, tag, set stock.
We read its 22 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
veeqo_get_company veeqo_list_stores veeqo_list_warehouses veeqo_get_warehouse veeqo_list_orders veeqo_get_order veeqo_get_order_returns veeqo_get_shipment_tracking veeqo_list_products veeqo_get_product veeqo_get_stock_entry veeqo_set_stock_level veeqo_list_customers veeqo_get_customer veeqo_list_suppliers veeqo_get_supplier veeqo_list_purchase_orders veeqo_get_purchase_order veeqo_list_tags veeqo_list_delivery_methods veeqo_add_order_note veeqo_tag_orders
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-veeqo)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.