Navifare MCP Serverofficial
F
licenseNot graded
qualityD
maintenanceEnables AI assistants to help users find better prices for flights they have already discovered, by comparing prices across multiple booking sources.
59
-
Ignav Flights
Server Details
Live flight prices and working booking links for AI agents and travel apps.
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
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- gusgordon/ignav-skill
- GitHub Stars
- 1
- Server Listing
- Ignav Flights MCP Server
Available Tools
2 toolssearch_airportsSearch airportsARead-onlyInspect
Find airport IATA codes by city, airport name, metro area, or code.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of airport results to return. | |
| query | Yes | Search query for airport names, city names, or airport codes. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes | List of airports matching the query. |
TDQS
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description adds minimal extra behavioral context. It aligns with the safe, read-only nature but does not disclose further traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the key purpose and input types. Every word is essential, no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of an output schema and simple input schema (2 params, all described), the description is complete. It covers the search scope and aligns with the tool's intended use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with both parameters described. The description adds meaning by explicitly listing 'metro area' and 'code' as searchable fields, which goes beyond the schema's generic description.
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 clearly states the tool's purpose: 'Find airport IATA codes by city, airport name, metro area, or code.' It specifies the verb and resource, and distinguishes from the sibling 'search_flights' which deals with flights.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear input types (city, airport name, metro area, code) but does not explicitly state when to use this tool versus the sibling 'search_flights'. The context is clear and no exclusions are needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_flightsSearch flightsARead-onlyInspect
Search one-way or round-trip flight prices between two IATA airport codes. Returns only itineraries with a preferred booking link and includes a top-level booking_url for each itinerary.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| adults | No | Number of adult passengers traveling. | |
| market | No | 2-letter market or country code affecting pricing and results. | US |
| origin | Yes | Origin airport or metro IATA code. | |
| children | No | Number of child passengers traveling. | |
| max_price | No | Maximum price in the selected market currency for flight results. | |
| max_stops | No | Maximum number of stops allowed in the flight itinerary. | |
| cabin_class | No | Preferred cabin class: economy, premium_economy, business, or first. | economy |
| destination | Yes | Destination airport or metro IATA code. | |
| max_results | No | Maximum number of flight results to return. | |
| return_date | No | Optional return date in YYYY-MM-DD format for round-trip flights. | |
| departure_date | Yes | Departure date in YYYY-MM-DD format. | |
| infants_on_lap | No | Number of infants traveling on an adult's lap. | |
| infants_in_seat | No | Number of infants traveling with their own seat. | |
| airlines_exclude | No | Airline codes to specifically exclude from search results. | |
| airlines_include | No | Airline codes to specifically include in search results. | |
| allow_self_transfer | No | Whether to include self-transfer flight options (true or false). |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| origin | Yes | Origin airport details for flight search. |
| destination | Yes | Destination airport details for flight search. |
| itineraries | Yes | List of flight itineraries. |
| return_date | No | Scheduled return date for round-trip flights (YYYY-MM-DD). |
| departure_date | Yes | Scheduled departure date (YYYY-MM-DD). |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context by stating that only itineraries with a preferred booking link are returned and that a top-level booking_url is included. This goes beyond the annotations and helps set expectations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no filler. The primary action and resource are front-loaded, and the result-filtering caveat is stated concisely. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the 16-parameter schema, full schema coverage, output schema, and annotations, the description does not need to explain every field. It provides the key behavioral caveat about booking links and top-level booking_url. A brief mention of when round-trip requires return_date would have been marginally useful, but the schema covers that.
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%, so the parameter schema fully documents each argument. The tool description does not need to repeat parameter details; the baseline of 3 is appropriate because the schema carries the semantic load and the description adds no additional parameter-level meaning.
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 states a specific verb ('Search'), a clear resource ('flight prices'), and explicit scope ('one-way or round-trip', 'between two IATA airport codes'). It clearly differentiates this tool from the sibling search_airports since it addresses flights rather than airport data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description makes the usage context clear by specifying the search type, route format, and result filtering. It does not explicitly mention alternatives or when-not-to-use conditions, but the resource distinction from search_airports is implicit and sufficient for basic selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
search_flights2 fields changed- changed
Input schema / properties / destination / descriptionPrevious value: -"Destination airport code for flight search."New value: +"Destination airport or metro IATA code." - changed
Input schema / properties / origin / descriptionPrevious value: -"Origin airport code for flight search."New value: +"Origin airport or metro IATA code."
1 tool update
- Changed
search_flights2 fields changed- added
Output schema / properties / itineraries / items / properties / price / properties / statusAdded value: +{ + "description": "Whether the price was confirmed or is an unverified search hint.", + "enum": [ + "verified", + "unverified" + ], + "type": "string" +} - changed
Output schema / properties / itineraries / items / properties / price / requiredPrevious value: -[ - "amount", - "currency" -]New value: +[ + "amount", + "currency", + "status" +]
2 tool updates
- First observed
search_airports - First observed
search_flights
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Flight search & booking for AI agents. 400+ airlines, $20-50 cheaper than OTAs.
Last-minute booking slots across 11 suppliers. Search, price, and execute bookings via AI agents.
AI marketplace — flights, tours, activities, transport & more via MCP. No auth required.
Google Flights search data: fares, routes, stops, and price insights via a hosted MCP server.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables live flight search and pricing via the Duffel Flights API, allowing AI agents to query flight data and pricing.17MIT
- AlicenseNot gradedqualityBmaintenanceFlight search for AI agents: flexible-date cheapest round-trips with a good-price verdict from historical data. Hosted remote MCP, free, no key.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables real-time flight fare searches across date ranges and multiple destinations, with historical price insights and booking links. Provides one-way and round-trip search tools through MCP.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.3/5.0
Disambiguation5/5
The two tools have entirely distinct purposes: one searches for airports and the other searches for flights. There is no overlap or ambiguity.
Naming Consistency5/5
Both tools follow a consistent 'search_' prefix pattern with a clear noun, making naming predictable and easy to understand.
Tool Count3/5
With only two tools, the server feels minimal for its stated purpose of flight searching. While it covers the essential operations, the small count is borderline for a travel-related server.
Completeness4/5
The server covers the core search functionality and provides booking links, but lacks additional flight management features like booking confirmation or cancellation, which are minor gaps.