by navifare
Navifare: Flight price comparison — compare flight prices across multiple booking sources for cheap flights comparison a
Compares flight prices across multiple booking platforms to find the best deals. Searches airlines, travel agencies, and booking sites in one query.
Navifare is an official MCP server published by navifare that provides AI assistants with tools and capabilities via the Model Context Protocol. Navifare: Flight price comparison — compare flight prices across multiple booking sources for cheap flights comparison a It is categorized under search web, developer tools.
You can install Navifare in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server supports remote connections over HTTP, so no local installation is required.
MIT
Navifare is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
I recommend Navifare for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired Navifare into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: Navifare is the kind of server we cite when onboarding engineers to host + tool permissions.
Navifare has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Strong directory entry: Navifare surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We evaluated Navifare against two servers with overlapping tools; this profile had the clearer scope statement.
Navifare is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Navifare for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired Navifare into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: Navifare surfaces stars and publisher context so we could sanity-check maintenance before adopting.
showing 1-10 of 69
Version: 0.1.5
Navifare finds a better price for a specific flight the user already found. Users should provide flight details conversationally, which will be structured into the required format.
This MCP server wraps the Navifare REST API as MCP tools for flight price comparison. It enables AI assistants like Claude to help users find better prices for flights they've already discovered.
https://mcp.navifare.com/mcphttps://www.navifare.com/mcp (Auto-updates from the MCP endpoint)format_flight_pricecheck_requestTitle: Format Flight Request
Parse and format flight details from natural language text or transcribed image content. Extracts flight information (airlines, flight numbers, dates, airports, prices) and structures it for price comparison. Returns formatted flight data ready for flight_pricecheck, or requests missing information if incomplete.
Annotations:
readOnlyHint: true - Tool only formats/parses data, no external callsdestructiveHint: false - Tool does not modify or delete dataInput Schema:
user_request (required): Flight details in natural language text. Include all available information: flight numbers, airlines, departure/arrival airports and times, dates, prices, passenger counts, and travel class.Example Request:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "format_flight_pricecheck_request",
"arguments": {
"user_request": "I found an Aeroitalia flight XZ2020 from FCO to MXP leaving tomorrow at 19.31 and returning with XZ2021 MXP to FCO next Friday at 10.11. 1 adult, economy, the best fare was 221 EUR"
}
}
}
flight_pricecheckTitle: Flight Price Check
Search multiple booking sources to find better prices for a specific flight the user has already found. Compares prices across different booking platforms to find cheaper alternatives for the exact same flight details.
Annotations:
readOnlyHint: false - Tool performs searches and may trigger external API callsdestructiveHint: false - Tool does not modify or delete dataInput Schema:
trip (required): Flight trip details including segments, passengers, and travel class
legs (required): Array of flight legs (one for outbound, one for return in round trips)travelClass (required): ECONOMY, PREMIUM_ECONOMY, BUSINESS, or FIRSTadults (required): Number of adult passengers (minimum: 1)children (required): Number of child passengers (minimum: 0)infantsInSeat (required): Number of infants requiring a seat (minimum: 0)infantsOnLap (required): Number of infants on lap (minimum: 0)source (required): Source identifier for the query (e.g., "Claude", "MCP", "ChatGPT")price (required): Reference price found by the user (e.g., "84.00", "200.50")currency (required): Three-letter ISO currency code (e.g., "EUR", "USD", "GBP")location (required): Two-letter ISO country code for user location (e.g., "ES", "IT", "US"). If unsure, default to "ZZ"Example Request:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "flight_pricecheck",
"arguments": {
"trip": {
"legs": [
{
"segments": [
{
"airline": "XZ",
"flightNumber": "2020",
"departureAirport": "MXP",
"arrivalAirport": "FCO",
"departureDate": "2025-12-16",
"departureTime": "07:10",
"arrivalTime": "08:25",
"plusDays": 0
}
]
}
],
"travelClass": "ECONOMY",
"adults": 1,
"children": 0,
"infantsInSeat": 0,
"infantsOnLap": 0
},
"source": "MCP",
"price": "84",
"currency": "EUR",
"location": "IT"
}
}
}
Revenue share available for qualified partners!
Earn commission on flight bookings made through your integration. Revenue share available for qualified partners.
This server complies with Anthropic's MCP Directory Policy. See docs/COMPLIANCE.md for details.
Privacy Policy and Terms of Service: https://navifare.com/terms
Contact: [email protected]
Privacy Inquiries: [email protected]
The only environment variable you typically need to document for this MCP server is:
GEMINI_API_KEY (required): Google Gemini API key for natural language parsing (used when your integration relies on Gemini for text/image understanding).See docs/USAGE_EXAMPLES.md for complete usage examples with detailed workflows.
Most documentation is in the docs/ directory (and a few files like this README.md and REPOSITORY_STRUCTURE.md live at the repo root):
Test files are located in the test/ directory. See test/README.md for details about available tests.
# Test with MCP Inspector
npx @modelcontextprotocol/inspector node dist/index.js
# Run specific test
node test/test-mcp.js
Helper scripts are in the scripts/ directory:
scripts/start-local.sh - Start local development serverscripts/deploy-to-render.sh - Prepare for Render deploymentscripts/start-servers.sh - Start multiple serversscripts/stop-servers.sh - Stop running serversnavifare-mcp/
├── src/ # TypeScript source code
├── dist/ # Compiled JavaScript (generated)
├── docs/ # Documentation
├── test/ # Test files
├── scripts/ # Helper scripts
└── [config files] # package.json, Dockerfile, etc.
See REPOSITORY_STRUCTURE.md for detailed structure.
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.