# Veritaset (remote · veritaset.com)

Verified, sourced mobile plan prices in 32 European markets and the US, ranked by public rules.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-19

## Components

- remote · `veritaset.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-veritaset-mcp/veritaset.md), [page](https://verifymcp.io/servers/com-veritaset-mcp/veritaset)

## Channel facts

- Endpoint: `https://veritaset.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.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-10-19.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 48/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2571 tokens (~428/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Veritaset MCP server?

Veritaset is a hosted endpoint at https://veritaset.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-veritaset-mcp 'https://veritaset.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-veritaset-mcp": {
      "url": "https://veritaset.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-veritaset-mcp": {
      "type": "http",
      "url": "https://veritaset.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-veritaset-mcp]
url = "https://veritaset.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-veritaset-mcp": {
      "type": "remote",
      "url": "https://veritaset.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-veritaset-mcp --url 'https://veritaset.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-veritaset-mcp:
    url: "https://veritaset.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-veritaset-mcp": {
      "Transport": "http",
      "Url": "https://veritaset.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-veritaset-mcp -t streamable-http -u 'https://veritaset.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-veritaset-mcp": {
      "type": "http",
      "url": "https://veritaset.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-10-18 (score 68, +1)

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

### 2026-10-16 (score 67, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-10-15 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 61)

First indexed and scored.

## MCP tools (6)

### `compare_mobile_plans` (~938 tokens)

Compare mobile plans

Consumer mobile phone plans (SIM-only and prepaid) in these markets: Belgium, Netherlands, Luxembourg, France, Iceland, Hungary, Finland, Slovenia, Ireland, Slovakia, Estonia, Latvia, Croatia, Greece, Malta, Liechtenstein, Portugal, Lithuania, Romania, Bulgaria, Cyprus, Czechia, Norway, Sweden, Austria, Poland, Italy, Denmark, United Kingdom, Switzerland, Spain, Germany, United States (preview), including mobile data while travelling from there. Returns the plans that meet every stated need, ranked by effective monthly cost including promos, one-off fees and the cost of covering their trips (EU allowance and surcharges, or Canada and Mexico for US plans; operator roaming passes, travel eSIMs), each with its source link and check date (collected_by_hand where a person read the price on the operator's own website), plus questions worth asking the person (missing_inputs).

Input parameters:

- `accept_contract` (boolean): false = only plans without a minimum contract. Prepaid packs paid several months up front are not contracts (each result says so); use max_term_months to limit them.
- `accept_prepaid` (boolean)
- `age` (number): Only needed for youth and senior plans.
- `autopay` (boolean): false = the person won't use AutoPay; advertised AutoPay discounts are added back. Default true.
- `country` (string): Market, ISO 3166-1 alpha-2 (BE, NL, LU, FR, IS, HU, FI, SI, IE, SK, EE, LV, HR, GR, MT, LI, PT, LT, RO, BG, CY, CZ, NO, SE, AT, PL, IT, DK, GB, CH, ES, DE, US). Prices are in that market's currency.
- `data_gb_month` (number|string, required): Mobile data the person uses per month, in GB, or "unlimited".
- `has_home_internet_with` (string): Operator group the person has home internet with (e.g. Proximus, Orange or Telenet in Belgium), which unlocks bundle prices.
- `horizon_months` (number): Months to average costs over, including promos. Default 12.
- `hotspot_gb_month` (number): Mobile hotspot (tethering) data needed per month, in GB. Plans that don't state enough hotspot data don't fit.
- `limit` (number): Number of results, default 5, max 20.
- `lines` (number): Number of lines (e.g. a family of 4). Default 1. Costs are then the total for all lines; each line has the data/minutes need above.
- `max_monthly_eur` (number): Budget per month in the market's currency (despite the name), as advertised; for all lines together.
- `max_term_months` (number): Longest term the person accepts, in months: a contract or months paid up front (e.g. an annual prepaid pack). 1 = month to month only; 12, 24, 36… Omit for any.
- `minutes_month` (number|null): National call minutes per month; null = unlimited. Default 100.
- `needs_5g` (boolean)
- `needs_esim` (boolean)
- `sms_month` (number|null): National SMS per month; null = unlimited. Default 0. Plans that charge per SMS beyond their allowance are costed at the stated rate, so a rough figure is fine.
- `special_eligibility` (boolean): True if the person qualifies for offers limited to some customers (students, social tariffs, porting from a named operator, existing customers of another service). Default false: such plans are liste…
- `travel` (array): Specific trips per year, when the person knows them. Takes precedence over travel_profile. Omit both if unknown (the result then lists travel under missing_inputs); pass [] if the person does not tra…
- `travel_profile` (string): How the person travels, when they describe it loosely: eu_occasional = a couple of weeks a year in the EU, eu_frequent = about two months a year in the EU. Costed with the published assumptions (see…
- `travels_outside_eu` (boolean): True if the person sometimes travels outside the EU. Each result then lists the plan's own options there (passes, included countries, pay-per-use rate) without costing a specific trip.

### `find_better_plan` (~751 tokens)

Find a better plan from my usage

Checks whether a cheaper mobile plan fits someone's actual usage (from a bill, an app screenshot or their own estimate) in their market. Takes a few months of usage and, if known, the current plan; returns plans that cover most of their months, ranked by effective monthly cost including trips, with the yearly saving against their current plan, sources and check dates. Send only numbers: no names, phone numbers or bills.

Input parameters:

- `accept_contract` (boolean): false = only plans without a minimum contract. Prepaid packs paid several months up front are not contracts (each result says so); use max_term_months to limit them.
- `age` (number): Only needed for youth and senior plans.
- `autopay` (boolean): false = the person won't use AutoPay; advertised AutoPay discounts are added back. Default true.
- `country` (string): Market, ISO 3166-1 alpha-2 (BE, NL, LU, FR, IS, HU, FI, SI, IE, SK, EE, LV, HR, GR, MT, LI, PT, LT, RO, BG, CY, CZ, NO, SE, AT, PL, IT, DK, GB, CH, ES, DE, US). Prices are in that market's currency.
- `current_offer_id` (string): Veritaset offer_id of the current plan, if it can be identified (see get_mobile_plan_details / compare results).
- `current_plan_name` (string): Current operator and plan name as on the bill, e.g. 'Proximus Mobile Smart'.
- `current_price_month` (number): What the person pays per month today, in the market's currency as advertised, if the plan can't be identified.
- `has_home_internet_with` (string): Operator group the person has home internet with (e.g. Proximus, Orange or Telenet in Belgium), which unlocks bundle prices.
- `hotspot_gb_month` (number): Mobile hotspot (tethering) data needed per month, in GB. Plans that don't state enough hotspot data don't fit.
- `limit` (number): Number of results, default 5, max 20.
- `lines` (number): Number of lines (e.g. a family of 4). Default 1. Costs are then the total for all lines; each line has the data/minutes need above.
- `max_term_months` (number): Longest term the person accepts, in months: a contract or months paid up front (e.g. an annual prepaid pack). 1 = month to month only; 12, 24, 36… Omit for any.
- `needs_5g` (boolean)
- `needs_esim` (boolean)
- `special_eligibility` (boolean): True if the person qualifies for offers limited to some customers (students, social tariffs, porting from a named operator, existing customers of another service). Default false: such plans are liste…
- `travel_profile` (string): How the person travels, when they describe it loosely: eu_occasional = a couple of weeks a year in the EU, eu_frequent = about two months a year in the EU. Costed with the published assumptions (see…
- `travels_outside_eu` (boolean): True if the person sometimes travels outside the EU. Each result then lists the plan's own options there (passes, included countries, pay-per-use rate) without costing a specific trip.
- `usage_months` (array, required): One entry per month, most recent first if known.

### `get_mobile_plan_details` (~109 tokens)

Mobile plan details

Full published record of one mobile plan or travel eSIM by offer_id, in any covered market: allowances, roaming (EU allowance, or Canada and Mexico for US plans), roaming passes, promo terms, source URL, source type (manual = collected by hand from the operator's own website in a normal browser) and check date.

Input parameters:

- `country` (string): Market of the offer, ISO 3166-1 alpha-2, if known.
- `offer_id` (string, required)

### `explain_ranking_method` (~32 tokens)

Ranking method

The public Veritaset ranking rules and assumptions, with version, so a recommendation can be explained or audited.

### `list_supported_countries` (~52 tokens)

Supported countries

Markets covered by Veritaset for mobile plans and for home internet, with status (published or preview), brand and offer counts, how many were collected by hand, and the date of the last data check.

### `compare_home_internet` (~439 tokens)

Compare home internet

Consumer home internet offers (fixed broadband alone or with TV, landline or mobile) in these markets: Belgium, Netherlands, Germany, France, United Kingdom, Italy, Spain. Returns the offers that meet the stated speed, region, TV / landline and contract needs, ranked by average monthly cost over the horizon (promos for their stated months, one-off fees, modem rental, and bundle discounts when the household has that operator's mobile), each part shown, with the source link, check date and the operator's address-check link. List prices are national; availability depends on the address.

Input parameters:

- `accept_contract` (boolean): false = only offers without a minimum term.
- `country` (string, required): Market, ISO 3166-1 alpha-2.
- `download_mbps_min` (number): Minimum advertised download speed in Mbps.
- `has_mobile_with` (string): Operator or group the household has mobile with (e.g. Telenet, Proximus, KPN); counts that operator's bundle discounts.
- `horizon_months` (number): Months to average costs over. Default 24.
- `limit` (number): Number of results, default 5, max 20.
- `max_monthly` (number): Budget per month in the market's currency, averaged over the horizon.
- `max_term_months` (number): Longest minimum term accepted, in months.
- `region` (string): City, province or region (e.g. Gent, Liège, Wallonia, Utrecht, Friesland). Regional operators are matched on it.
- `special_eligibility` (boolean): True if the household qualifies for social tariffs or other restricted offers.
- `technology` (string): Only offers sold on this technology.
- `upload_mbps_min` (number): Minimum advertised upload speed in Mbps.
- `wants_landline` (boolean)
- `wants_mobile` (boolean): True if offers that include mobile lines may be shown.
- `wants_mobile_with` (string): Operator the household would take mobile from as well; counts that operator's bundle discounts.
- `wants_tv` (boolean)

## Diagnostics

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

## Score history

- 2026-10-19: 68
- 2026-10-18: 68
- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 62
- 2026-10-14: 61

## Common questions

### What is the Veritaset MCP server?

Veritaset is an MCP server listed in the public MCP registry as com.veritaset/mcp. Verified, sourced mobile plan prices in 32 European markets and the US, ranked by public rules. This page covers its hosted endpoint (https://veritaset.com/mcp).

### Is the Veritaset MCP server safe to use?

Veritaset scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Veritaset MCP server expose?

Veritaset exposes 6 tools: compare_mobile_plans, find_better_plan, get_mobile_plan_details, explain_ranking_method, list_supported_countries, compare_home_internet. Their descriptions and schemas cost roughly 2,321 tokens of context every time the server is loaded.

### Does the Veritaset MCP server require authentication?

No. We connected to Veritaset without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Veritaset MCP server still maintained?

Veritaset is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://veritaset.com/mcp
- Repository: https://github.com/Veritaset-tech/veritaset
- Website: https://veritaset.com/agents/
- Changelog RSS feed: https://verifymcp.io/servers/com-veritaset-mcp/veritaset.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-veritaset-mcp/veritaset.json
- HTML version of this page: https://verifymcp.io/servers/com-veritaset-mcp/veritaset