Home / MCP registry index / com.podbenchmark/podbenchmark
POD Benchmark
com.podbenchmark/podbenchmark in the official MCP registry.
Endpoint https://podbenchmark.com/api/mcp. Source: github.com/FilipLjubic/podbenchmark-cli.
The registry describes it as: Compare print-on-demand supplier prices, shipping and delivered totals for the same product.
On 2026-10-31 we read its 10 tools, but part of what it advertised was cut before our rules saw it: a description or schema past the size we read, more tools than we read, or a tool list split across pages. Nothing in the part we read matched, but the rest was not checked: this is not a clean result.
Tools it advertises
search_products list_categories get_product get_product_options compare_product resolve_supplier_link list_suppliers get_supplier get_supplier_prices supplier_guide
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/com-podbenchmark-podbenchmark)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.