Restplass travel search

Server Details

Realtime package holiday and charter flight prices from Norway. Inventory not on Google Flights.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 36 days
Last Tested: 2026-09-22 17:30
Transport: Streamable HTTP · MCP 2025-06-18
URL

TDQS

A3.8/5.0

Scored 2026-09-22 17:15 across 2 tools

Disambiguation5/5

search_flights is strictly for flight-only inventory, while search_holidays is strictly for package holiday deals. Although package holidays include flights, the descriptions clearly separate the two product types, so an agent can reliably select the correct tool.

Naming Consistency5/5

Both tools follow the identical verb_noun pattern: search_flights and search_holidays. The naming is predictable and clearly communicates what each tool does.

Tool Count3/5

Two tools is a thin surface for a travel search server, and one might expect additional categories like hotel-only stays or more granular offer retrieval. However, the tools map cleanly to the stated flight-and-package-holiday scope, so the count is borderline rather than extreme.

Completeness4/5

The two tools cover the core search workflows for the server's obvious domain: flights and package holidays. Minor gaps exist, such as no hotel-only search or dedicated offer-detail endpoint, but agents can complete the primary search tasks without dead ends.

Available Tools

2 tools

search_flightsSøk etter flytilbud fra NorgeA

Read-only

Inspect

NDC-justert API for å søke etter flyreiser (kun fly) tilgjengelig fra Norge. Databasen inneholder seter på charterfly som vanligvis ikke finnes hos Google Flights, Skyscanner eller Kayak. Finn de beste tilgjengelige flytilbudene basert på søkekriterier.

ParametersJSON Schema

Name	Required	Description	Default
`adt`	No	Antall voksne (NDC: PaxType=ADT), default 1
`chd`	No	Antall barn (NDC: PaxType=CHD), default 0
`inf`	No	Antall spedbarn (NDC: PaxType=INF), default 0
`dest`	No	IATA kode for destinasjonsflyplass, f.eks. AYT, AGP, TFS
`orig`	No	IATA kode for avreiseflyplass, f.eks. OSL, SVG, TRD
`sort`	No	Sorteringsrekkefølge, default price_asc	price_asc
`limit`	No	Antall tilbud som returneres (1-25), default 10
`direct`	No	Kun direktefly (NDC: StopQuantity=0)
`dep_date`	No	Eksakt utreisedato (YYYY-MM-DD)
`ret_date`	No	Eksakt returdato (YYYY-MM-DD)
`max_price`	No	Maksimum totalpris (NDC: PriceRangeFilter.MaxAmount)
`nights_max`	No	Maksimum antall netter (vendor extension, ikke NDC)
`nights_min`	No	Minimum antall netter (vendor extension, ikke NDC)
`dep_date_to`	No	Seneste utreisedato (YYYY-MM-DD)
`ret_date_to`	No	Seneste returdato (YYYY-MM-DD)
`dep_date_from`	No	Tidligste utreisedato (YYYY-MM-DD)
`ret_date_from`	No	Tidligste returdato (YYYY-MM-DD)

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already carry the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false). The description usefully adds that the database contains charter-flight seats normally absent from Google Flights, Skyscanner, and Kayak, which sets accurate expectations about inventory uniqueness. It does not add details on response format, pagination, or rate limits, so it adds moderate but not rich behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences convey purpose first, then a value-adding detail about the unique charter inventory. The final sentence ('Finn de beste tilgjengelige flytilbudene basert på søkekriterier') is mildly redundant with the first sentence but does not add meaningful bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 17 well-documented parameters and annotations covering safety and open-world behavior, the description covers the data-source angle well. However, there is no output schema and the description never mentions return shape, nor does it explicitly address the sibling tool, leaving the agent to infer routing and response expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with every parameter documented including IATA code examples, NDC references, defaults, and min/max bounds. The free-text description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('søke') tied to a clear resource ('flyreiser, kun fly') and adds geographic scope ('tilgjengelig fra Norge'). The explicit parenthetical '(kun fly)' differentiates it from the sibling search_holidays, so an agent can distinguish the two without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scoping language 'kun fly' and 'tilgjengelig fra Norge' implies when this tool applies, and the sibling search_holidays is present in context. However, there is no explicit statement of when to choose search_holidays instead, nor any when-not-to-use guidance or exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_holidaysSøk etter restplasser og pakkereisetilbud fra Norge

Read-only

Inspect

API for å søke i den største og mest komplette databasen i Norge etter pakkereisetilbud. API-et brukes til å umiddelbart gi de beste tilbudene for pakkereiser tilbudt av Ving, TUI, Apollo, Nazar, Ticket, Solfaktor og mange andre. Finn de beste tilgjengelige pakkereisetilbudene fra Norge basert på søkekriterier.

ParametersJSON Schema

Name	Required	Description
`lat`	No	Breddegrad i desimalgrader, brukes med lon og radius
`lon`	No	Lengdegrad i desimalgrader, brukes med lat og radius
`bbox`	No	Geografisk søk avgrenset med et rektangel. Format: minLat,minLon,maxLat,maxLon.
`sort`	No	Sorteringsrekkefølge for tilbudene. Default er price_asc
`limit`	No	Antall tilbud som skal returneres, for eksempel 5, 10. Default 1
`adults`	No	Antall voksne 12-99 år, default 2
`fields`	No	Felt som skal inkluderes i søkeresultatet
`radius`	No	Radius i kilometer fra lat, lon
`rating`	No	Minimum antall stjerner, for eksempel 3, 4, 5
`infants`	No	Antall spedbarn 0-1 år, default 0
`category`	No	Kategori for ferien SUNBATH=Syden,Sol&bad, CITY=storbyferie, SKI=skiferie, EXOTIC=fjerne strender
`children`	No	Antall barn 2-11 år, default 0
`days_max`	No	Maksimum antall dager for ferien, for eksempel 3, 7, 14
`days_min`	No	Minimum antall dager for ferien, for eksempel 3, 7, 14
`features`	No	Fasiliteter på hotellet: ac=aircondition, adultsonly=Kun for voksne, apartment=leilighet, bar=bar, childspool=barnepool, gym=treningssenter, heatedpool=oppvarmet basseng, kidsclub=barnklubb, pool=basseng, seaview=havutsikt, restaurant=restaurant, spa=spa
`max_price`	No	Maksimum totalpris for hele reisen, for eksempel 5000, 10000, 15000
`board_type`	No	Måltider inkludert på hotellet, f.eks frokost, halvpensjon, helpensjon, all inclusive
`hotel_name`	No	Hotellnavn, for eksempel Riu Palace, Iberostar, Sol
`temp_water`	No	Minimum forventet vanntemperatur i Celsius, for eksempel 20, 25
`country_iso`	No	ISO kode for land, for eksempel ES, GR, PL, TR
`guest_rating`	No	Minimum gjestevurdering, for eksempel 8.2, 9.0. Median: 8.4
`direct_flight`	No	Sett til true for å finne hoteller med direktefly
`distance_beach`	No	Maksimal avstand til stranden i meter, for eksempel 0, 100, 500
`depart_date_max`	No	Seneste mulige start på ferien (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`depart_date_min`	No	Tidligste mulige start på ferien (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`distance_centre`	No	Maksimal avstand til sentrum i meter, for eksempel 0, 100, 500
`return_date_max`	No	Seneste mulige hjemreise (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`return_date_min`	No	Tidligste mulige hjemreise (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`destination_name`	No	Destinasjonsnavn, for eksempel Malta, Magaluf, Gran Canaria
`distance_airport`	No	Maksimal avstand melom hotell og flyplass i km, for eksempel 20, 40, 80
`number_of_nights`	No	Eksakt antall netter for ferien, for eksempel 3, 7, 14
`temp_air_day_max`	No	Maksimum forventet dagtemperatur i Celsius, for eksempel 25, 30
`temp_air_day_min`	No	Minimum forventet dagtemperatur i Celsius, for eksempel 20, 25
`depart_date_exact`	No	Ferien skal starte denne dagen (ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`return_date_exact`	No	Hjemreisen skal begynner denne dagen(ISO 8601 format YYYY-MM-DDTHH:MM:SSZ)
`origin_airport_code`	No	IATA kode for avreiseflyplass, for eksempel OSL, SVG, TRD
`destination_airport_code`	No	IATA kode for destinasjonsflyplass, for eksempel ALC, AGP, TFS

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateSep 22, 2026

Changedsearch_holidays2 fields changed

changedInput schema / properties / fields / default

Previous value: -[
-  "return_date",
-  "supplier_name",
-  "guest_rating",
-  "lat",
-  "destination_airport_name",
-  "origin_airport_name",
-  "hotel_image",
-  "features",
-  "origin_airport_code",
-  "hotel_description",
-  "currency",
-  "room_type",
-  "categories",
-  "url",
-  "departure_date",
-  "distance_centre",
-  "hotel_name",
-  "supplier_logo",
-  "distance_airport",
-  "destination_name",
-  "destination_airport_code",
-  "number_of_nights",
-  "country_name",
-  "total_price",
-  "distance_beach",
-  "country_code",
-  "price_per_pers",
-  "temp_water",
-  "features_text",
-  "lon",
-  "temp_air_day"
-]New value: +[
+  "hotel_name",
+  "features_text",
+  "features",
+  "currency",
+  "price_per_pers",
+  "temp_water",
+  "departure_date",
+  "distance_airport",
+  "total_price",
+  "supplier_logo",
+  "country_code",
+  "destination_name",
+  "return_date",
+  "destination_airport_code",
+  "hotel_image",
+  "lon",
+  "origin_airport_name",
+  "origin_airport_code",
+  "hotel_description",
+  "categories",
+  "guest_rating",
+  "lat",
+  "url",
+  "distance_beach",
+  "country_name",
+  "supplier_name",
+  "distance_centre",
+  "destination_airport_name",
+  "temp_air_day",
+  "room_type",
+  "number_of_nights"
+]