# Voyscout Price History (remote · voyscout.com)

Historical flight and package price series for Czech origins. Honest stats, no verdicts. CC BY 4.0

- Trust score: 81/100 (high trust)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `voyscout.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-voyscout-price-history/voyscout.md), [page](https://verifymcp.io/servers/com-voyscout-price-history/voyscout)

## Channel facts

- Endpoint: `https://voyscout.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-22.

- **Endpoint Security**: 83/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 811 tokens (~162/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the Voyscout Price History MCP server?

Voyscout Price History is a hosted endpoint at https://voyscout.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-voyscout-price-history 'https://voyscout.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-voyscout-price-history": {
      "url": "https://voyscout.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-voyscout-price-history]
url = "https://voyscout.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-voyscout-price-history:
    url: "https://voyscout.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-voyscout-price-history": {
      "type": "http",
      "url": "https://voyscout.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-09-20 (score 81, +1)

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

### 2026-09-18 (score 80, +8)

- [security improvement] Authorization: unverified → partial

### 2026-09-16 (score 72, +1)

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

### 2026-09-14 (score 71, 0)

- [security] Tool “find_opportunities” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 127 → 162
- [cosmetic] “current_vs_history” reworded the description of “destination”
- [cosmetic] “price_history” reworded the description of “destination”

### 2026-09-13 (score 71, 0)

- [functional regression] Schema quality: pass → fail
- [functional] New tool “compare_destinations”

### 2026-09-11 (score 71, +1)

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

### 2026-09-09 (score 70, +1)

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

### 2026-09-07 (score 69, +1)

- [functional regression] Schema quality: 61 → 106
- [functional] New tool “find_opportunities”

## MCP tools (5)

### `list_destinations` (~40 tokens)

List destinations

List every destination with a published price series, with how many days each rail was actually measured and the calendar span those measurements fall in. Historical observations only.

### `price_history` (~114 tokens)

Price history

Price series for one destination: measured span, stats, a downsampled sample of points and any regime breaks. Historical observations only, never a live quote or a recommendation.

Input parameters:

- `destination` (string, required): destination slug, as returned by list_destinations. A RESORT key read off a rail (e.g. 'hurghada') also resolves, to its parent destination, and the answer then carries `resolved_from`; underscores a…
- `rail` (string): optional: restrict to one rail

### `current_vs_history` (~122 tokens)

Current price vs. history

Stats for one destination (min, median, and what share of the TRACKED DAYS were dearer than the last measurement) without the sample points. Percentages are over observed days, not over the calendar span. Descriptive only: it does not say whether to buy.

Input parameters:

- `destination` (string, required): destination slug, as returned by list_destinations. A RESORT key read off a rail (e.g. 'hurghada') also resolves, to its parent destination, and the answer then carries `resolved_from`; underscores a…

### `find_opportunities` (~324 tokens)

Find opportunities

Rank every published rail by how its LAST measurement compares with its own tracked history, so a caller can ask 'where is it unusually cheap right now?' in one call instead of one call per destination. Percentages are over observed days, not the calendar span. `latest_cheaper_than_pct_of_days` is the same number as `cheaper_than_pct` under a name that states its direction (higher = cheaper than more of the tracked days). `stale_rails` says how many of the rails THIS call matched are past their own freshness boundary today, with the day it was judged (`as_of`), so the caller need not subtract dates per row. Descriptive only: it ranks observations and gives no verdict. Rails with too little history are returned under `excluded`, never dropped silently.

Input parameters:

- `limit` (integer): optional (default 10): how many rows to return; 'matched' reports the count before the cap
- `min_history_days` (integer): optional (default 30): rails measured for fewer days are listed under 'excluded'
- `party` (string): optional: '<adults>-<children>', e.g. '2-2' - the same A-C shape the price streams are keyed on
- `rail` (string): optional: restrict to one rail
- `sort` (string): optional (default cheapest_vs_history): 'cheapest_vs_history' ranks by the share of tracked days that were dearer; 'most_below_median' ranks by how far the last measurement sits below the median, rel…

### `compare_destinations` (~211 tokens)

Compare destinations

Put 2-8 named destinations side by side on the same snapshot, each with the stats current_vs_history reports (last measurement, median, min, share of TRACKED DAYS that were dearer). Numbers are for the WHOLE party, not per person, and percentages are over observed days rather than the calendar span. Rows come back in the order you asked for - it does not rank, and gives no verdict; use find_opportunities to rank. A destination that yields no row is returned under `excluded` with the reason.

Input parameters:

- `destinations` (array, required): 2-8 destination slugs; the answer keeps this order
- `min_history_days` (integer): optional (default 30): rails measured for fewer days are listed under 'excluded'
- `party` (string): optional (default '2-2'): '<adults>-<children>', the same A-C shape the price streams are keyed on
- `rail` (string): optional (default both): restrict to one rail

## Diagnostics

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

## Score history

- 2026-09-22: 81
- 2026-09-21: 81
- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 70
- 2026-09-09: 70
- 2026-09-08: 69
- 2026-09-07: 69
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 67
- 2026-09-03: 67
- 2026-09-02: 66
- 2026-09-01: 66
- 2026-08-31: 65

## Common questions

### What is the Voyscout Price History MCP server?

Voyscout Price History is an MCP server listed in the public MCP registry as com.voyscout/price-history. Historical flight and package price series for Czech origins. Honest stats, no verdicts. CC BY 4.0. This page covers its hosted endpoint (https://voyscout.com/mcp).

### Is the Voyscout Price History MCP server safe to use?

Voyscout Price History scores 81 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 Voyscout Price History MCP server expose?

Voyscout Price History exposes 5 tools: list_destinations, price_history, current_vs_history, find_opportunities, compare_destinations. Their descriptions and schemas cost roughly 811 tokens of context every time the server is loaded.

### Does the Voyscout Price History MCP server require authentication?

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

### Is the Voyscout Price History MCP server still maintained?

Voyscout Price History is still listed as active in the MCP registry. We last reached this channel on 22 September 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://voyscout.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-voyscout-price-history/voyscout.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-voyscout-price-history/voyscout.json
- HTML version of this page: https://verifymcp.io/servers/com-voyscout-price-history/voyscout