Voyscout Price History MCP server

• compare_destinationswrite actionFree

  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.

• current_vs_historyFree

  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.

• find_opportunitiesFree

  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.

• list_destinationsFree

  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_historyFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 699ms20/20
• Tool poisoning5 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

Voyscout Price History: common questions

Is Voyscout Price History MCP server safe?

With care: it is graded C, so read the findings first (57/100). Read the Voyscout Price History safety report

How do I install Voyscout Price History?

It runs remotely at voyscout.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Voyscout Price History need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Voyscout Price History maintained?

The latest release is v1.0.0.

Is Voyscout Price History up?

100% of our last 7 checks got an answer. We check remote servers about four times a day.

What can I use instead of Voyscout Price History?

Servers from other publishers that do the same job: Piratefly Flight Price Judge MCP server, Piratefly MCP server and Phoenix Zero — L2 Health Oracle MCP server. Compare all Voyscout Price History alternatives.