Travelpayouts
NPM · @PIPEWORX/MCP-TRAVELPAYOUTS · 2 COMPONENTS
Travelpayouts MCP — wraps the Aviasales Flights Data API (travelpayouts.com)
Available components
Last scanned (22 hours ago)
Scores higher than 68% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-travelpayouts). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 862 tokens (~215/item across 4 items; 4 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 Management20
- Stability observed for 6 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 4 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-travelpayouts@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-travelpayouts |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-travelpayouts/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560545029 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d0aa4c89b2e91f5bba7759e08df0a67f2673587b4274c2e23e43c0187593286447df7d0feab323280b383e7313727b00c40c8cbc653748ac0beabaf3f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
travelpayouts_cheap_prices ~232
Get the cheapest cached flight tickets for a route (one per destination, cheapest first). Uses IATA city/airport codes. Example: travelpayouts_cheap_prices({ origin: "MOW", destination: "BCN", currency: "usd", _apiKey: "token:marker" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Travelpayouts key as "token:marker" (marker optional) |
| currency | string | – | Price currency code, e.g. "usd", "eur", "rub" (default rub) |
| depart_date | string | – | Departure date, format YYYY-MM or YYYY-MM-DD (optional) |
| destination | string | – | Arrival IATA city/airport code, e.g. "BCN", "HKT". Optional — omit for cheapest from origin to anywhere. |
| origin | string | yes | Departure IATA city/airport code, e.g. "MOW", "LON", "JFK" |
| return_date | string | – | Return date, format YYYY-MM or YYYY-MM-DD (optional, for round trips) |
No output schema declared.
No examples provided.
travelpayouts_cheapest_by_month ~199
Get the cheapest ticket price for each day of a month grouped by number of transfers (month matrix). Uses IATA city/airport codes. Example: travelpayouts_cheapest_by_month({ origin: "LED", destination: "HKT", month: "2026-08-01", currency: "usd", _apiKey: "token:marker" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Travelpayouts key as "token:marker" (marker optional) |
| currency | string | – | Price currency code, e.g. "usd" (default rub) |
| destination | string | yes | Arrival IATA city/airport code, e.g. "HKT" |
| month | string | – | Month start date, format YYYY-MM-DD, e.g. "2026-08-01" |
| origin | string | yes | Departure IATA city/airport code, e.g. "LED" |
No output schema declared.
No examples provided.
travelpayouts_popular_destinations ~135
Get the most popular destinations (with cheapest cached prices) reachable from a city. Uses IATA city codes. Example: travelpayouts_popular_destinations({ origin: "MOW", currency: "usd", _apiKey: "token:marker" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Travelpayouts key as "token:marker" (marker optional) |
| currency | string | – | Price currency code, e.g. "usd" (default rub) |
| origin | string | yes | Departure IATA city code (2-3 chars), e.g. "MOW" |
No output schema declared.
No examples provided.
travelpayouts_price_calendar ~239
Get the cheapest ticket price for each day of a month for a route (a price calendar). Uses IATA city/airport codes. Example: travelpayouts_price_calendar({ origin: "MOW", destination: "BCN", depart_date: "2026-08", currency: "usd", _apiKey: "token:marker" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Travelpayouts key as "token:marker" (marker optional) |
| calendar_type | string | – | Which date to key the calendar by: "departure_date" (default) or "return_date" |
| currency | string | – | Price currency code, e.g. "usd" (default rub) |
| depart_date | string | yes | Month to build the calendar for, format YYYY-MM or YYYY-MM-DD |
| destination | string | yes | Arrival IATA city/airport code, e.g. "BCN" |
| origin | string | yes | Departure IATA city/airport code, e.g. "MOW" |
| return_date | string | – | Return month/date, format YYYY-MM or YYYY-MM-DD (optional) |
No output schema declared.
No examples provided.
How do I install the Travelpayouts MCP server?
Travelpayouts runs locally as an npm package, launched with npx -y @pipeworx/mcp-travelpayouts. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-travelpayouts
claude mcp add pipeworx-io-travelpayouts -- npx -y @pipeworx/mcp-travelpayouts
What is the Travelpayouts MCP server?
Travelpayouts is an MCP server listed in the public MCP registry as io.github.pipeworx-io/travelpayouts. Travelpayouts MCP, wraps the Aviasales Flights Data API (travelpayouts.com). This page covers its npm package (@pipeworx/mcp-travelpayouts).
Is the Travelpayouts MCP server safe to use?
Travelpayouts scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Travelpayouts MCP server expose?
Travelpayouts exposes 4 tools: travelpayouts_cheap_prices, travelpayouts_price_calendar, travelpayouts_cheapest_by_month, travelpayouts_popular_destinations. Their descriptions and schemas cost roughly 805 tokens of context every time the server is loaded.
Is the Travelpayouts MCP server still maintained?
Travelpayouts is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Travelpayouts MCP server under?
Travelpayouts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.