io.github.CloudCorpRecords/faregrid
NPM · @RENETURCIOS/FAREGRID · 2 COMPONENTS
Search one-way and round-trip flight fares across dates and destinations, with price verdicts.
Available components
Last scanned (17 hours ago)
Scores higher than 34% 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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2498 tokens (~1249/item across 2 items; 2 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 Management0
- Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.Unverified
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 66
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/@reneturcios/faregrid@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
search_oneway_flights FlightPowers: search one-way flights ~1,133
FlightPowers one-way fare search: live prices read from Google Flights. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- plus either one departure date or a date range. Returns each flight's price, airline, duration, stops, a bookable buy_link, and Google's historical price range (price_insights_low / price_insights_high), the band that shows whether a fare is actually a good deal. Suited to any one-way fare question, including open-ended ones. One call accepts a date range and several destinations and searches every combination: 'Cheapest flight to Sri Lanka anywhere in October' is one call, not thirty. That holds with the caller's own key. On the free sign-in allowance (10 searches a day, one per combination) a grid larger than what is left today is refused before anything runs; a grid within what is left runs, and a whole-month scan needs the caller's own key. Each date/destination combination is one search; the count comes back in `api_usage`. `by_destination` carries one entry per requested destination -- empty ones included, each with a `reason` that separates a destination with no flights from one that was not searched, whose search failed, or whose fares did not fit in `limit`. Fares go stale within minutes: a current price comes from a new search, not from an earlier result.
| Name | Type | Req | Description |
|---|---|---|---|
| airline_codes | – | – | Restricts the search to these airline codes, e.g. ["LY"]. |
| arrival_time_max | – | – | Latest arrival hour, 0-23. |
| arrival_time_min | – | – | Earliest arrival hour, 0-23. |
| currency | string | – | ISO currency code, default "usd". |
| departure_date | – | – | Single departure date, "YYYY-MM-DD". |
| departure_date_from | – | – | First date of a departure range. |
| departure_date_to | – | – | Last date of a departure range. |
| departure_time_max | – | – | Latest departure hour, 0-23. |
| departure_time_min | – | – | Earliest departure hour, 0-23. |
| exclude_airline_codes | – | – | Airline codes left out of the results. |
| from_airport | string | yes | Origin IATA code, e.g. "TLV". One origin per search; a second one is refused rather than searched. |
| limit | integer | – | Maximum flights to return, after merging and sorting. |
| max_price | – | – | Only flights at or below this price are returned. |
| max_searches | – | – | The searches this call may make, up or down. Unset is the normal behaviour: with the caller's own key the cap covers the request when the request is reasonable (a whole month at three trip lengths is… |
| max_stops | – | – | Maximum stops per flight. 0 means non-stop only. |
| passengers | – | – | One entry per traveller, not a count: 1 adult, 2 child (aged 2-11), 3 infant on lap, 4 infant in seat, e.g. [1, 1, 2] for two adults and a child. At least one adult, each infant on lap needs its own… |
| seat_type | – | – | 1 economy, 2 premium economy, 3 business, 4 first. |
| sort_by | string | – | "best" (the default) and "price" both order by price, cheapest first; "duration" orders shortest first. Applied across all results. |
| to_airport | – | yes | Destination airport. One IATA code ("BCN"), several separated by commas ("BCN,LIS,ATH"), or a list (["BCN","LIS","ATH"]) -- every shape is accepted and the destinations are compared in the same searc… |
| use_fallback | – | – | Default: unset. Switches the search to a second, independent flight data source instead of the usual Google Flights page read. Unset already escalates to that source once, automatically, after a sear… |
| verbose | boolean | – | Returns every field the upstream sends on each fare, and every fare that was selected, with no row bound. Off by default: a result carries the best rows by the requested sort_by in a compact shape (d… |
No output schema declared.
No examples provided.
search_roundtrip_flights FlightPowers: search round-trip flights ~1,365
FlightPowers round-trip fare search: live prices read from Google Flights, priced as paired legs rather than two separate one-ways. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- a departure date or range, and either a return date or a trip length in nights. Returns the total price for both legs, per-leg airline, stops and duration, and a single bookable buy_link for the trip. Suited to any return-trip fare question. A flexible search is ONE call: departure_date_from / departure_date_to set the outbound range and `nights`, in place of return_date, compares trip lengths -- '5 to 7 nights in Rome sometime in May' is one call. A WHOLE MONTH is one call too. departure_date_from "2026-10-01", departure_date_to "2026-10-31" and nights [3, 4, 5] prices every departure day in October at three trip lengths and shows which combination is cheapest. That is 93 date/night combinations and the cap rises to cover them by itself, so the whole grid runs in that one call. That holds with the caller's own key. On the free sign-in allowance (10 searches a day, one per combination) a grid larger than what is left today is refused before anything runs; a grid within what is left runs, and a whole-month scan needs the caller's own key. Each date/night/destination combination is ONE search, so a month at three trip lengths is 93 of them and the same month across two destinations is 186. A search that fails with a server error is retried once, so with the caller's own key the figure the plan is charged is `api_usage.hub_requests_billed` (retries included), not the combination count. `by_destination` carries one entry per requested destination -- empty ones included, each with a `reason` that separates a destination with no flights from one that was not searched, whose search failed, or whose fares did not fit in `limit`. Fares go stale within minutes: a current price comes from a new search, not from an earl…
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | ISO currency code, default "usd". |
| departure_airline_codes | – | – | Restricts the outbound leg to these airlines. |
| departure_date | – | – | Single outbound date, "YYYY-MM-DD". |
| departure_date_from | – | – | First date of an outbound range. |
| departure_date_to | – | – | Last date of an outbound range. |
| from_airport | string | yes | Origin IATA code, e.g. "TLV". One origin per search; a second one is refused rather than searched. |
| limit | integer | – | Maximum trips to return, after merging and sorting. |
| max_departure_stops | – | – | Maximum stops on the outbound leg. |
| max_price | – | – | Only trips at or below this total price are returned. |
| max_return_stops | – | – | Maximum stops on the return leg. |
| max_searches | – | – | The searches this call may make, up or down. Unset is the normal behaviour: with the caller's own key the cap covers the request when the request is reasonable (a whole month at three trip lengths is… |
| nights | – | – | Trip length in nights; a number, or a list like [5, 6, 7]. The return date is derived from each departure date. |
| passengers | – | – | One entry per traveller, not a count: 1 adult, 2 child (aged 2-11), 3 infant on lap, 4 infant in seat, e.g. [1, 1, 2] for two adults and a child. At least one adult, each infant on lap needs its own… |
| return_airline_codes | – | – | Restricts the return leg to these airlines. |
| return_date | – | – | Fixed return date. Mutually exclusive with `nights`. |
| returns_per_outbound | – | – | How many return flights to pair with each outbound flight, 1 to 5 (default 2). Each date/destination combination searched still returns at most 10 trips; at 5 they are picked from up to 50 pairings i… |
| seat_type | – | – | 1 economy, 2 premium economy, 3 business, 4 first. |
| sort_by | string | – | "best" (the default) and "price" both order by price, cheapest first; "duration" orders shortest first. Applied across all results. |
| to_airport | – | yes | Destination airport. One IATA code ("BCN"), several separated by commas ("BCN,LIS,ATH"), or a list (["BCN","LIS","ATH"]) -- every shape is accepted and the destinations are compared in the same searc… |
| use_fallback | – | – | Default: unset. Switches the search to a second, independent flight data source instead of the usual Google Flights page read. Unset already escalates to that source once, automatically, after a sear… |
| verbose | boolean | – | Returns every field the upstream sends on each fare, and every fare that was selected, with no row bound. Off by default: a result carries the best rows by the requested sort_by in a compact shape (d… |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/faregrid MCP server?
io.github.CloudCorpRecords/faregrid runs locally as an npm package, launched with npx -y @reneturcios/faregrid. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/faregrid
claude mcp add cloudcorprecords-faregrid -- npx -y @reneturcios/faregrid
What is the io.github.CloudCorpRecords/faregrid MCP server?
io.github.CloudCorpRecords/faregrid is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/faregrid. Search one-way and round-trip flight fares across dates and destinations, with price verdicts. This page covers its npm package (@reneturcios/faregrid).
Is the io.github.CloudCorpRecords/faregrid MCP server safe to use?
io.github.CloudCorpRecords/faregrid scores 66 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. 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 io.github.CloudCorpRecords/faregrid MCP server expose?
io.github.CloudCorpRecords/faregrid exposes 2 tools: search_oneway_flights, search_roundtrip_flights. Their descriptions and schemas cost roughly 2,498 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/faregrid MCP server still maintained?
io.github.CloudCorpRecords/faregrid 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 io.github.CloudCorpRecords/faregrid MCP server under?
io.github.CloudCorpRecords/faregrid declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.