Voyscout Price History
REMOTE · VOYSCOUT.COM · SCANNED SEP 22
Historical flight and package price series for Czech origins. Honest stats, no verdicts. CC BY 4.0
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · voyscout.com
claude mcp add --transport http com-voyscout-price-history 'https://voyscout.com/mcp'
{
"mcpServers": {
"com-voyscout-price-history": {
"url": "https://voyscout.com/mcp"
}
}
} {
"servers": {
"com-voyscout-price-history": {
"type": "http",
"url": "https://voyscout.com/mcp"
}
}
} [mcp_servers.com-voyscout-price-history] url = "https://voyscout.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-voyscout-price-history": {
"type": "remote",
"url": "https://voyscout.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-voyscout-price-history --url 'https://voyscout.com/mcp' --transport streamable-http
mcp_servers:
com-voyscout-price-history:
url: "https://voyscout.com/mcp" {
"McpServers": {
"com-voyscout-price-history": {
"Transport": "http",
"Url": "https://voyscout.com/mcp"
}
}
} assistant mcp add com-voyscout-price-history -t streamable-http -u 'https://voyscout.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +8
- Authorization: unverified → partial ▲ security
- 16 Sept 26 +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.
- 14 Sept 26 0
- Tool “find_opportunities” rewrote its description, which is the text the model reads security
- Schema quality: 127 → 162 ▼ functional
- “current_vs_history” reworded the description of “destination” cosmetic
- “price_history” reworded the description of “destination” cosmetic
- 13 Sept 26 0
- Schema quality: pass → fail ▼ functional
- New tool “compare_destinations” functional
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +1
- Schema quality: 61 → 106 ▼ functional
- New tool “find_opportunities” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://voyscout.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=voyscout.com | CN=WE1,O=Google Trust Services,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 55e4f23d2869359e0ee4d1da29759469 |
| SANs: voyscout.com, *.voyscout.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of voyscout.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| voyscout.com. | present | 2371 | 13 | Verified |
| voyscout.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'nonce-k0Yk22mZBjxf7UFKdTMlIg==' 'self' https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; frame-src 'self' https://challenges.cloudflare.com; object-src 'none'; base-uri 'none'; frame-ancestors 'self'; report-uri /api/csp-report |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://voyscout.com/mcp | Verified | 200 | |
| http (plaintext) | http://voyscout.com/mcp | HTTPS enforced | 301 | https://voyscout.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_destinations Compare destinations ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destinations | array | yes | 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 |
No output schema declared.
No examples provided.
current_vs_history Current price vs. history ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | 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… |
No output schema declared.
No examples provided.
find_opportunities Find opportunities ~324
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
list_destinations List destinations ~40
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price_history Price history ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | 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 |
No output schema declared.
No examples provided.
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.