# The Front Desk Review (remote · mcp.frontdeskreview.com)

4,764 products, 626 categories: sourced prices, dated price history, independent-test coverage.

- Trust score: 65/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.frontdeskreview.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-frontdeskreview-front-desk-review-data/mcp.md), [page](https://verifymcp.io/servers/com-frontdeskreview-front-desk-review-data/mcp)

## Channel facts

- Endpoint: `https://mcp.frontdeskreview.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3118 tokens (~164/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-frontdeskreview-front-desk-review-data https://mcp.frontdeskreview.com/mcp
```

### Codex

```toml
[mcp_servers.com-frontdeskreview-front-desk-review-data]
url = "https://mcp.frontdeskreview.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-frontdeskreview-front-desk-review-data": {
      "type": "remote",
      "url": "https://mcp.frontdeskreview.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-frontdeskreview-front-desk-review-data --url https://mcp.frontdeskreview.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-frontdeskreview-front-desk-review-data:
    url: "https://mcp.frontdeskreview.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-frontdeskreview-front-desk-review-data": {
      "type": "http",
      "url": "https://mcp.frontdeskreview.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (19)

### `list_sections` (~105 tokens)

List sections

Enumerate ALL 271 pricing themes this index covers: the deep hub sections (e.g. ai-receptionists, call-tracking) plus dozens of catalog topics (e.g. vpn-services, web-hosting, password-managers, crm-software). Each entry carries its slug, display label, vertical, tagline, vendor count and kind ('section' or 'catalog'). Pass any of these slugs as the `section` arg to the other tools to query that theme.

### `search_vendors` (~190 tokens)

Search vendors

Search any theme's data index by free-text query across vendor name, domain, integrations, plan notes, and capabilities (e.g. 'hipaa restaurant', 'google ads zapier'). Works for every theme — hub sections and catalog topics alike (set `section` to the theme slug from list_sections). Returns full provenanced vendor records (each plan carries source url + accessedAt). Empty query returns all vendors in the theme.

Input parameters:

- `query` (string)
- `section` (string): Theme slug to query (default "ai-receptionists"). A theme is any of the 271 pricing topics this index covers: the deep hub sections (e.g. ai-receptionists) plus the many catalog topics (e.g. vpn-serv…

### `compare` (~173 tokens)

Compare vendors

Compare specific vendors side by side by slug within any theme (e.g. ['goodcall','rosie','smith-ai'] in ai-receptionists, or ['nordvpn','expressvpn'] in vpn-services). Set `section` to the theme slug from list_sections. Returns full provenanced records plus a notFound list for unknown slugs.

Input parameters:

- `section` (string): Theme slug to query (default "ai-receptionists"). A theme is any of the 271 pricing topics this index covers: the deep hub sections (e.g. ai-receptionists) plus the many catalog topics (e.g. vpn-serv…
- `slugs` (array, required)

### `get_normalized_pricing` (~217 tokens)

Get normalized pricing

Effective monthly cost per vendor in any theme at a chosen call volume, normalizing flat, per-minute and per-call billing to one comparable number. For non-telephony catalog themes (per-seat / flat plans with no call quota) this returns each plan's base monthly price — the meaningful figure there. Cheapest priceable plan per vendor; quote-only or unpriceable-at-volume vendors return null (never a fabricated figure). avgCallMinutes defaults to 3 and is echoed in assumptions for reproducibility.

Input parameters:

- `avgCallMinutes` (number)
- `callsPerMonth` (number, required)
- `section` (string): Theme slug to query (default "ai-receptionists"). A theme is any of the 271 pricing topics this index covers: the deep hub sections (e.g. ai-receptionists) plus the many catalog topics (e.g. vpn-serv…

### `get_benchmark` (~176 tokens)

Get vendor benchmark

Per-vendor benchmark card by slug within any theme: full provenanced record plus dataset-derived indicators (entry price, normalized cost at 100 and 500 calls/mo where call-volume applies, billing models, free-tier presence, compliance, integration breadth). Set `section` to the theme slug from list_sections. All values trace to plan sources; no synthetic scores.

Input parameters:

- `section` (string): Theme slug to query (default "ai-receptionists"). A theme is any of the 271 pricing topics this index covers: the deep hub sections (e.g. ai-receptionists) plus the many catalog topics (e.g. vpn-serv…
- `slug` (string, required)

### `find_best` (~329 tokens)

Find best (ranked)

Answer 'best <theme> for <use case>' and 'cheapest <theme>' directly: returns the theme's vendors ranked by entry price (cheapest first, quote-only last), each with its verified compliance facts (HIPAA/SOC 2/GDPR), free-tier flag, best-for tags and the entry plan's source. Conjunctive fact filters narrow it to what this index has actually CONFIRMED — requireHipaa / requireSoc2 / requireGdpr / requireFreeTier (e.g. 'best CRM for HIPAA' = section 'crm-software' + requireHipaa:true). Omit all filters to rank the whole theme by price. Set `section` to the theme slug from list_sections. Never infers a fact it has not verified.

Input parameters:

- `requireFreeTier` (boolean): Only vendors with a genuine $0 forever plan.
- `requireGdpr` (boolean): Only vendors with confirmed GDPR compliance.
- `requireHipaa` (boolean): Only vendors with confirmed HIPAA support (a BAA).
- `requireSoc2` (boolean): Only vendors with a confirmed SOC 2 attestation.
- `section` (string): Theme slug to query (default "ai-receptionists"). A theme is any of the 271 pricing topics this index covers: the deep hub sections (e.g. ai-receptionists) plus the many catalog topics (e.g. vpn-serv…

### `list_coverage` (~115 tokens)

List coverage

What this index actually covers, so a miss reads as out-of-scope rather than broken. Now spans 271 pricing themes — the deep hub sections PLUS dozens of catalog topics (VPNs, web hosting, password managers, CRM, e-commerce, AI tools, and more): total theme count, the section/catalog split, total vendors, per-theme vendor counts and kind, the data's date range (min/max source accessedAt), the questions it answers well and what it does NOT cover. Derived from every theme's dataset.

### `whats_changed` (~195 tokens)

What's changed

Recent dated price-change capsules, newest first — the freshness a base model cannot have. Each capsule is a cleared, two-source-corroborated movement of a vendor's published price (vendor, plan, before→after, date, sources). Optionally filter to changes on/after a date or within one section. Returns an empty list with a clear note when nothing qualifying has been recorded yet.

Input parameters:

- `section` (string): Theme slug to query (default "ai-receptionists"). A theme is any of the 271 pricing topics this index covers: the deep hub sections (e.g. ai-receptionists) plus the many catalog topics (e.g. vpn-serv…
- `since` (string): Only changes detected on or after this ISO date (YYYY-MM-DD).

### `get_price_history` (~175 tokens)

Get price history

The full dated price series for ONE product or vendor (by slug), plus derived stats: first-tracked date, current/low/high, number of recorded changes, net % since tracked, the largest single move, and the last change. This is the citable answer to 'how much did X cost', 'did X's price drop', and price-trend questions — grounded on a real, append-only series, not a model's guess. Returns found:false (never a fabricated series) for an unknown slug.

Input parameters:

- `kind` (string): Limit to 'hw' (hardware product) or 'sw' (software vendor). Omit to match either; a slug is resolved across both.
- `slug` (string, required): Product or vendor slug (e.g. 'bambu-lab-a1', 'goodcall').

### `get_independent_test_coverage` (~203 tokens)

Get independent test coverage

The independent-testing provenance for ONE product (by category + slug) — a COUNT of evidence, never a quality score. Fields: outlets (independent outlets on record), labs (how many physically tested it and left >=1 measured value), metrics (distinct kinds of metric measured, with names), mentioned (outlets that only mentioned it), and a ready-to-quote `reading` sentence. Use it to state how much independent hands-on evidence backs any claim about a product. A low count means little independent evidence has been gathered yet, NOT that the product is bad; a high count means well-documented, NOT better. Returns found:false (never a fabricated count) for an unknown or unreviewed product.

Input parameters:

- `category` (string, required): Product category slug (e.g. 'action-cameras', '3d-printers').
- `slug` (string, required): Product slug (e.g. 'dji-osmo-action-5-pro').

### `price_movers` (~197 tokens)

Price movers

Recorded price MOVES across the index within a recency window (default 90 days), newest-and-largest first — each a dated before→after change of a tracked entity. Optionally filter by kind ('hw'/'sw') or category/theme slug. The freshness a base model structurally cannot have. Returns an empty list with a clear note when nothing moved in the window (a quiet window is honestly quiet).

Input parameters:

- `category` (string): Limit to one category/theme slug (e.g. '3d-printers', 'ai-receptionists').
- `kind` (string): Limit to 'hw' (hardware product) or 'sw' (software vendor). Omit to match either; a slug is resolved across both.
- `limit` (integer): Max movers to return (default 25).
- `withinDays` (integer): Recency window in days (default 90), measured against the log's latest date.

### `volatility_for_entity` (~122 tokens)

Volatility for entity

How volatile ONE product or vendor's price has been: a 0-100 volatility score derived from its recorded moves (frequency × average move size), plus change count, net % and last change. Honest gate: below a minimum recorded-change threshold it returns sufficient:false with a note, never a score invented from a single point.

Input parameters:

- `kind` (string): Limit to 'hw' (hardware product) or 'sw' (software vendor). Omit to match either; a slug is resolved across both.
- `slug` (string, required): Product or vendor slug.

### `most_volatile_in_category` (~145 tokens)

Most volatile in category

Within one category/theme, the entities whose prices have moved the most (ranked by volatility score), plus the category price baseline (count, median current, low/high). Entities without enough recorded movement are omitted from the ranking but counted in the baseline. Answers 'which X changes price most' for a market.

Input parameters:

- `category` (string, required): Category/theme slug (e.g. 'gpus', 'crm-software').
- `kind` (string): Limit to 'hw' (hardware product) or 'sw' (software vendor). Omit to match either; a slug is resolved across both.
- `limit` (integer): Max ranked entities (default 25).

### `list_product_categories` (~71 tokens)

List product categories

Enumerate the spec-driven PRODUCT categories this index covers (physical goods like smartphones, laptops, GPUs — distinct from the software/subscription pricing themes). Each entry carries its slug, product count, the comparable spec keys, and the brands present. Pass a category slug to search_products / compare_products / find_products.

### `search_products` (~110 tokens)

Search products

Search one product category by free-text query across product name, brand, and spec values (e.g. 'snapdragon 5000mah', 'oled 120hz'). Set `category` to a slug from list_product_categories. Returns full provenanced product records (every spec + price carries source url + accessedAt). Empty query returns all products in the category.

Input parameters:

- `category` (string, required): Product category slug from list_product_categories (e.g. 'smartphones').
- `query` (string)

### `compare_products` (~99 tokens)

Compare products

Compare specific products side by side by slug within a category (e.g. ['apple-iphone-16-pro','samsung-galaxy-s25-ultra'] in 'smartphones'). Returns full provenanced spec records plus a notFound list and the category's comparable specKeys, so an agent can line up the same attributes across products.

Input parameters:

- `category` (string, required): Product category slug from list_product_categories.
- `slugs` (array, required)

### `find_products` (~211 tokens)

Find products (ranked)

Answer 'best <category> under $N' and 'which <category> has the most <spec>' directly: filter a category by maxPriceUsd and/or brand, then rank by a field — 'priceUsd' (default, cheapest first), 'releaseDate', or any of the category's spec keys (set descending:true for biggest-first, e.g. sortBy:'battery_mah' descending:true). Returns provenanced product records; products missing the sort value sort last. Never infers a spec it has not verified.

Input parameters:

- `brand` (string): Only products from this brand.
- `category` (string, required): Product category slug from list_product_categories.
- `descending` (boolean): Rank largest/newest first (default false = smallest/cheapest first).
- `maxPriceUsd` (number): Only products at or below this USD price.
- `sortBy` (string): Field to rank by: 'priceUsd' (default), 'releaseDate', or a spec key from the category.

### `list_cost_decoders` (~86 tokens)

List cost decoders

List the 'real cost' decoders — topics where the advertised sticker price hides the true bill (e.g. AI customer support billed per resolution, where a $29/mo seat price becomes hundreds/mo at volume). Each entry carries the question it answers, the scenarios it computes, the vendor count and the data's as-of date. Pass a topic slug to get_cost_decoder.

### `get_cost_decoder` (~199 tokens)

Get cost decoder

The REAL all-in monthly cost per vendor for a decoder topic (slug from list_cost_decoders, e.g. 'ai-customer-support-cost'), computed in deterministic code from sourced, dated inputs — each vendor's per-seat price + AI billing model + per-unit price, totalled at named scenarios (e.g. 5 agents at 1,000 and 5,000 AI resolutions/mo) with the arithmetic shown. Quote-only inputs return a null total, never a fabricated number. Optionally pass agents + resolutions for a custom scenario. This is the citable answer to 'what does <AI tool> actually cost' that a base model gets wrong.

Input parameters:

- `agents` (number): Optional: agents/seats for a custom scenario.
- `resolutions` (number): Optional: AI resolutions/mo for a custom scenario.
- `topic` (string, required): Decoder slug from list_cost_decoders (e.g. 'ai-customer-support-cost').

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-frontdeskreview-front-desk-review-data/mcp#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 64
- 2026-08-01: 64
- 2026-07-31: 64
- 2026-07-30: 63
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 61

## Links

- Remote endpoint: https://mcp.frontdeskreview.com/mcp
- Repository: https://github.com/AlexandDunk/frontdesk-data
- Website: https://frontdeskreview.com/connect/
- Changelog RSS feed: https://verifymcp.io/servers/com-frontdeskreview-front-desk-review-data/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-frontdeskreview-front-desk-review-data/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-frontdeskreview-front-desk-review-data/mcp