Home / MCP registry index / com.frontdeskreview/front-desk-review-data
The Front Desk Review
com.frontdeskreview/front-desk-review-data in the official MCP registry.
Endpoint https://mcp.frontdeskreview.com/mcp. Source: github.com/AlexandDunk/frontdesk-data.
The registry describes it as: 4,764 products, 626 categories: sourced prices, dated price history, independent-test coverage.
We read its 19 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.
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
list_sections search_vendors compare get_normalized_pricing get_benchmark find_best list_coverage whats_changed get_price_history get_independent_test_coverage price_movers volatility_for_entity most_volatile_in_category list_product_categories search_products compare_products find_products list_cost_decoders get_cost_decoder
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-frontdeskreview-front-desk-review-data)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.