Home / MCP registry index / com.robotrunk/robotrunk
RoboTrunk
com.robotrunk/robotrunk in the official MCP registry.
Endpoint https://robotrunk.com/mcp.
The registry describes it as: Search independent stores, check recalls and product facts, and prepare checkout at the store.
We read its 23 tools on 2026-10-28. 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
search_catalog get_product check_product create_checkout get_checkout update_checkout complete_checkout cancel_checkout get_order get_trust_manifest submit_feedback get_tool_guide ask_product_manual watch_recalls get_recall_watch stop_recall_watch check_fit watch_back_in_stock get_back_in_stock_watch stop_back_in_stock_watch check_listing enrich_product compare_products
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-robotrunk-robotrunk)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.