Analytics
voyscout.com
Provides price history and trend analysis for destinations, identifying unusually cheap current prices.
ENDPOINT 1
https://voyscout.com/mcp
MCP server metadata
- Name
- voyscout-price-series
- Version
- 1.0.0
Known tools 4
list_destinationsList every destination with a published price series, with how many days each rail was actually measured and the calendar span those measurements fall in.
Inferred read-onlyprice_historyPrice series for one destination: measured span, stats, a downsampled sample of points and any regime breaks.
Inferred read-onlycurrent_vs_historyStats for one destination (min, median, and what share of the TRACKED DAYS were dearer than the last measurement) without the sample points.
Inferred read-onlyfind_opportunitiesRank 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.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.voyscout-price-series]
url = "https://voyscout.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"voyscout-price-series": {
"type": "http",
"url": "https://voyscout.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: voyscout-price-series
Remote MCP URL: https://voyscout.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"voyscout-price-series": {
"url": "https://voyscout.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"voyscout-price-series": {
"type": "http",
"url": "https://voyscout.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "voyscout-price-series",
"transport": "streamable-http",
"url": "https://voyscout.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.