Home / MCP registry index / io.github.mcp-dir/tiny-mcp
Tiny (Olist Tiny)
io.github.mcp-dir/tiny-mcp in the official MCP registry.
Endpoint https://api.mcp.ai/p_tiny. Source: github.com/mcp-dir/tiny-mcp.
The registry describes it as: Tiny (Olist Tiny) e-commerce ERP, one of the most used by online stores and marketplace sellers in B
We read its 20 tools on 2026-10-22. 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
tiny_list_accounts tiny_list_products tiny_get_product tiny_get_product_stock tiny_list_orders tiny_get_order tiny_list_contacts tiny_get_contact tiny_create_contact tiny_list_invoices tiny_get_invoice tiny_list_payables tiny_list_receivables tiny_list_sellers show_version report_bug connect toolkit_info marketplace authenticate
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-mcp-dir-tiny-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.