Mu
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Remote MCP server for hotel rate monitoring, parity checks, and pricing intelligence via Apify.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 3/12 | Full marks for a release or code change within 30 days |
| Still answering | 8/8 | The cloud endpoint answered at the last check |
| Usage score | 11/100 |
Quality: Passed 3/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Hotel Rate Monitoring API. Follow https://mcp.popnx.com/i/veyvey45-eng-travel-monitor-launch.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/5 checks · What you ask goes through the maker’s server (mcp.apify.com) · ✓ Commands checked Nov 20, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Hotel Rate Monitoring APIhttps://mcp.apify.com?tools=actors,docs,travelmonitorlab/travel-monitor-launchClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsHotel Rate Monitoring API
Use Hotel Rate Monitoring API and tell me what you can do for me, then show me one thing✓ If Claude says it is using Hotel Rate Monitoring API or shows a Hotel Rate Monitoring API tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Hotel Rate Monitoring APIhttps://mcp.apify.com?tools=actors,docs,travelmonitorlab/travel-monitor-launchStart a new chat and pick Hotel Rate Monitoring API from your plugins before typing
Use Hotel Rate Monitoring API and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Hotel Rate Monitoring API or shows a Hotel Rate Monitoring API tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user travel-monitor-launch 'https://mcp.apify.com?tools=actors,docs,travelmonitorlab/travel-monitor-launch'You should see Hotel Rate Monitoring API listed as connected
Use Hotel Rate Monitoring API and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Hotel Rate Monitoring API or shows a Hotel Rate Monitoring API tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Hotel Rate Monitoring API and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Hotel Rate Monitoring API or shows a Hotel Rate Monitoring API tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Hotel Rate Monitoring API and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Hotel Rate Monitoring API or shows a Hotel Rate Monitoring API tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://mcp.apify.com?tools=actors,docs,travelmonitorlab/travel-monitor-launchJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user travel-monitor-launch 'https://mcp.apify.com?tools=actors,docs,travelmonitorlab/travel-monitor-launch'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"travel-monitor-launch": {
"url": "https://mcp.apify.com?tools=actors,docs,travelmonitorlab/travel-monitor-launch"
}
}
}VS Code (mcp.json)
{
"servers": {
"travel-monitor-launch": {
"type": "http",
"url": "https://mcp.apify.com?tools=actors,docs,travelmonitorlab/travel-monitor-launch"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account veyvey45-eng, which owns the repo
Code last changed 7 months ago, more than 6 months ago
No licence file found in the repo
Responded in 433 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/veyvey45-eng-travel-monitor-launch)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 7 months ago, and the latest version (1.0.0) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: Mu, Award Travel Finder, Killbottleneck, Gondola Award Travel Search, Whimsical
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Search award flight availability and points pricing across 27 airlines and 23 loyalty programs.
Free-to-self-host goal and process maps for humans and AI agents, with REST API and MCP.
Compare cash vs points on hotels, flights, and cars. Checkout supported hotels and rental cars.
Create and edit flowcharts, mind maps, wireframes, and docs in Whimsical, or search your workspace.
| This one Hotel Rate Monitoring API | Mu | Award Travel Finder | Killbottleneck | Gondola Award Travel Search | Whimsical | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | Yes | No | No |
| Add with + in Claude | No | No | No | No | No | Yes |
| Basic checks | 3/5 | 4/4 | 3/3 | 3/3 | 4/4 | 4/4 |
| License | – | AGPL-3.0 | MIT | MIT | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Ce document sert de README maître pour le dépôt GitHub public d’exemples autour de Hotel Rate Monitoring API sur Apify. Son objectif est double. D’une part, il agit comme une surface de découvrabilité hors Store pour les profils techniques et semi-techniques. D’autre part, il réduit le time to first success en donnant un chemin d’essai extrêmement simple, adossé à des sorties réelles déjà extraites de l’API.
Le positionnement retenu reste volontairement précis. Le produit n’est pas présenté comme une API travel générique, mais comme une API de monitoring tarifaire hôtelier et de price parity intelligence exposée via Apify, avec des sorties prêtes à être réutilisées dans des workflows de travel operations, de pricing analysis, de reporting, ou d’agents IA. Le nom marketing privilégié pour la découvrabilité publique est Hotel Rate Monitoring API, tandis que le slug technique de l’Actor reste travel-monitor-launch.
| Ce dépôt doit aider à faire | Pourquoi c’est utile commercialement |
|---|---|
| Comprendre la promesse en moins d’une minute | Réduit la friction avant le premier essai |
| Rejouer un appel API simple | Rend la valeur concrète et vérifiable |
| Voir un payload réel | Renforce la crédibilité produit |
| Télécharger des exemples prêts à intégrer | Facilite l’adoption par développeurs et analystes |
| Revenir vers la fiche Apify | Transforme GitHub en surface d’acquisition pour le Store |
Le rôle principal de ce dépôt n’est pas de remplacer la documentation complète du produit. Il doit fonctionner comme une porte d’entrée claire, plus courte et plus démonstrative, orientée vers un premier succès. Le bon lecteur doit pouvoir comprendre rapidement le cas d’usage, tester un endpoint, lire un exemple de sortie, puis décider s’il veut explorer davantage l’Actor sur Apify.
Short promise: Monitor hotel pricing and parity signals through a standby-ready Apify API, then reuse structured outputs in reporting, analytics, or AI workflows.
| Quick link | Purpose |
|---|---|
| Apify Actor page | https://apify.com/travelmonitorlab/travel-monitor-launch?utm_source=github&utm_medium=docs&utm_campaign=launch_april_2026 |
| First success guide | docs/first_success_under_1_minute.md |
| AI agents quickstart | docs/ai_agents_mcp_quickstart.md |
| MCP registry manifest | server.json |
| MCP publication notes | docs/mcp_registry_and_directory_next_steps.md |
| Claude review readiness | docs/claude_review_readiness.md |
| OpenAPI file | openapi/travel-monitor-launch.openapi.json |
| Example payload | examples/demo_feed_item.json |
| Annotated signal asset | assets/annotated_feed_item.svg |
| First success visual | assets/annotated_first_success_flow.svg |
| Audience prioritaire | Bénéfice attendu |
|---|---|
| Revenue managers | Voir rapidement des écarts OTA visibles et des opportunités tarifaires |
| Consultants travel | Obtenir des signaux structurés au lieu de simples pages brutes |
| Équipes produit / BI | Alimenter un pipeline analytique ou un dashboard interne |
| Builders IA / automation | Brancher une API claire sur un workflow agentique |
La structure ci-dessous est pensée pour rendre le dépôt immédiatement lisible. Elle sépare la démonstration métier, les snippets techniques et les exemples JSON réutilisables.
travel-monitor-launch-examples/
├── README.md ├── server.json ├── snippets/ │ ├── health_check.sh │ ├── opportunities_feed.sh │ ├── plan_catalog.sh │ └── delivery_bundle.sh ├── examples/ │ ├── demo_feed_item.json │ ├── demo_opportunities_feed_response.json │ ├── demo_top_opportunities_response.json │ ├── demo_delivery_bundle.json │ ├── demo_plan_catalog.json │ └── demo_product_offers.json ├── docs/ │ ├── first_success_under_1_minute.md │ ├── ai_agents_mcp_quickstart.md │ ├── claude_review_readiness.md │ ├── mcp_registry_and_directory_next_steps.md │ ├── integration_scenarios.md │ └── outbound_payload_examples.md ├── openapi/ │ └── travel-monitor-launch.openapi.json └── assets/ ├── annotated_feed_item.svg └── annotated_first_success_flow.svg
Le chemin d’essai le plus efficace consiste à commencer par un endpoint santé, puis à passer immédiatement à une route démonstrative plus métier. Comme le service est exposé en Standby mode sur Apify, l’appel doit inclure un jeton Apify valide. Certaines routes métier peuvent aussi dépendre d’une clé métier privée selon le mode d’accès activé.
| Étape | Action |
|---|---|
| 1 | Ouvrir la fiche publique de l’Actor Apify |
| 2 | Récupérer votre jeton Apify |
| 3 | Tester la route /health |
| 4 | Tester ensuite /travel/opportunities/feed |
| 5 | Comparer le résultat à l’exemple JSON réel fourni dans ce dépôt |
curl "https://travelmonitorlab--travel-monitor-launch.apify.actor/health?token=<YOUR_APIFY_TOKEN>"
curl -H "Authorization: Bearer <YOUR_APIFY_TOKEN>" \
-H "x-api-key: " \ "https://travelmonitorlab--travel-monitor-launch.apify.actor/travel/opportunities/feed"
curl -H "Authorization: Bearer <YOUR_APIFY_TOKEN>" \
-H "x-api-key: " \ "https://travelmonitorlab--travel-monitor-launch.apify.actor/travel/plans"
Cette surface GitHub doit maintenant jouer un rôle très simple. Elle aide un lecteur à comprendre rapidement le produit, puis l’oriente vers la bonne porte d’entrée selon son contexte : Apify Store pour le premier essai, MCP pour les assistants IA, OpenAPI pour l’intégration développeur, et les exemples JSON pour la réutilisation analytique ou reporting.
| Entrée | Ressource recommandée | Pourquoi c’est utile |
|---|---|---|
| Premier essai humain | Fiche Apify + docs/first_success_under_1_minute.md | Rejouer le chemin /health puis /travel/opportunities/feed sans friction inutile |
| Builders IA / MCP | docs/ai_agents_mcp_quickstart.md | Comprendre l’ordre d’appel agentique et la logique health → feed → export |
| Registry / directory publication | server.json + docs/mcp_registry_and_directory_next_steps.md | Préparer une découvrabilité MCP au-delà d’Apify sans redéployer un serveur séparé |
| Développeurs API | openapi/travel-monitor-launch.openapi.json | Inspecter rapidement la surface d’API et les routes disponibles |
| Workflows analytics / reporting | examples/ + snippets/ | Réutiliser des payloads réels et des appels copiables |
The intended path stays narrow: validate the API first, retrieve one useful pricing signal second, and move to exports or automation only after the value is clear.
Le dépôt expose désormais la spécification OpenAPI utilisée par l’Actor afin de rendre la surface plus crédible pour les intégrateurs, les reviewers techniques et les outils capables d’ingérer automatiquement un contrat d’API.
| Asset | Purpose |
|---|---|
server.json | Manifeste MCP distant prêt pour un référencement registre/annuaire |
docs/mcp_registry_and_directory_next_steps.md | Décide où publier ensuite la couche MCP sans redéploiement inutile |
openapi/travel-monitor-launch.openapi.json | Contrat de routes pour lecture développeur, génération client ou revue technique |
snippets/health_check.sh | Test liveness minimal |
snippets/opportunities_feed.sh | Premier appel métier démonstratif |
examples/demo_opportunities_feed_response.json | Réponse réaliste pour intégration ou comparaison |
docs/ai_agents_mcp_quickstart.md | Pont direct entre le dépôt GitHub et l’usage MCP / agents IA |
docs/claude_review_readiness.md | Note orientée revue Anthropic avec auth, support, privacy et preuves publiques |
Le dépôt inclut désormais un visuel réutilisable du parcours d’évaluation le plus simple. Il peut être repris tel quel dans un post social, un tutoriel court, une page communauté ou un message d’outreach léger.
L’exemple ci-dessous provient d’une sortie réelle déjà extraite du smoke test. Il est volontairement court, car il sert de preuve de valeur immédiate dans le dépôt, dans les messages d’outreach et dans les publications externes.
{
"feed_rank": 1, "opportunity_key": "group_644c57e536983898", "destination_label": "Wooster, Ohio", "entity_name": "Hampton Inn Wooster (Hotel)", "checkin_date": "2026-04-15", "checkout_date": "2026-04-16", "currency": "USD", "opportunity_type": "booking_parity_gap", "opportunity_priority": "medium", "opportunity_score": 48.82, "recommended_offer_tier": "parity", "market_leader_site": "trivago", "best_price": 136.0, "price_gap": 6.0, "price_gap_percent": 4.41, "booking_gap": 6.0, "booking_gap_percent": 4.41, "sites": ["booking", "trivago"], "commercial_summary": "Booking.com is 6.00 USD above the best observed market rate for Hampton Inn Wooster (Hotel); best visible site: trivago at 136.00 USD." }
| Champ clé | Pourquoi il compte |
|---|---|
| entity_name | Le signal porte sur un établissement concret |
| destination_label | Le contexte géographique est immédiatement lisible |
| opportunity_score | La priorisation est native |
| market_leader_site | La comparaison concurrentielle est explicite |
| price_gap | La valeur métier est quantifiée |
| commercial_summary | Le résultat est déjà lisible pour un décideur |
Le dépôt doit présenter le produit comme un ensemble de familles de résultats plutôt que comme une simple liste d’endpoints. Cette lecture aide beaucoup les prospects à se projeter dans un usage réel.
| Output family | Rôle principal | Fichier recommandé |
|---|---|---|
| Opportunities feed | Détection et priorisation des signaux | examples/demo_opportunities_feed_response.json |
| Single demo item | Preuve courte et partageable | examples/demo_feed_item.json |
| Top opportunities | Lecture prioritaire synthétique | examples/demo_top_opportunities_response.json |
| Delivery bundle | Réutilisation aval dans des workflows | examples/demo_delivery_bundle.json |
| Plan catalog | Clarification du cadrage produit | examples/demo_plan_catalog.json |
| Product offers | Support au packaging et au discours commercial | examples/demo_product_offers.json |
Il ne faut pas surcharger le dépôt avec trop de promesses. Trois scénarios d’intégration bien choisis suffisent pour rendre le produit concret et mémorisable.
| Scénario | Description courte | Audience cible |
|---|---|---|
| Daily hotel parity watch | Détecter chaque jour des écarts OTA visibles et remonter les signaux prioritaires | Revenue managers, consultants distribution |
| Travel analytics pipeline | Alimenter un flux analytique avec feed JSON, exports CSV et bundles | Analystes, équipes BI, travel ops |
| AI agent enrichment | Fournir à un agent IA des signaux structurés sur opportunités et prix | Builders IA, équipes produit, automation |
Le dépôt doit contenir des appels à l’action simples, sans ambiguïté. Le visiteur doit comprendre immédiatement quelle suite logique lui est proposée.
| Contexte | CTA conseillé |
|---|---|
| Fin de README | View the Actor on Apify and inspect the endpoints |
| Après le premier snippet