Combien d'outils expose com.iconic-expeditions/concierge ?

com.iconic-expeditions/concierge expose 23 outil(s). Le coût de contexte pour les charger tous est d'environ 5626 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Recherche & Web / com.iconic-expeditions/concierge

com.iconic-expeditions/concierge

serveur MCP (Model Context Protocol) · iconic-concierge 2.0.0

▸ Recherche & Web

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

streamable-httpType / transport

directAccès

~5626 tokensCoût de contexte

23Outils

Est-ce que com.iconic-expeditions/concierge est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.iconic-expeditions/concierge » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 23 outils

add_activity≈ 378 tokens
Add an activity to a specific day and time slot (morning/afternoon/evening). Optionally link to a content item using its type and id. Requires a bearer token.
Paramètres, retour & exemple (8)
Paramètres
- slot · string · requis · morning | afternoon | evening
- title · string · requis
  Short title for the activity
- day_id · string · requis
  The day UUID to add the activity to
- description · string · optionnel
- itinerary_id · string · requis
  Parent itinerary UUID
- wp_content_id · integer · optionnel
  Source content id
- wp_content_type · string · optionnel · itinerary | activity | destination | post
  Content type to link
- duration_minutes · integer · optionnel
Exemple d'appel
```
{"name": "add_activity", "arguments": {"slot": "morning", "title": "texte", "day_id": "texte", "itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
add_day≈ 164 tokens
Append an extra day to a concierge itinerary and increment num_days. Requires a bearer token.
Paramètres, retour & exemple (3)
Paramètres
- notes · string · optionnel
- title · string · optionnel
  Optional day label, e.g. 'Drive to Hwange'
- itinerary_id · string · requis
Exemple d'appel
```
{"name": "add_day", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
create_itinerary≈ 198 tokens
Create a new (empty) itinerary attributed to the Iconic Expeditions concierge, made public and returned with its share link. Days are created automatically. Requires a bearer token.
Paramètres, retour & exemple (4)
Paramètres
- title · string · requis
  Itinerary title, e.g. '7-Day Hwange Safari'
- num_days · integer · requis
  Number of days
- start_date · string · optionnel
  Optional ISO date string for day 1, e.g. '2025-06-01'
- description · string · optionnel
  Optional short description
Exemple d'appel
```
{"name": "create_itinerary", "arguments": {"title": "texte", "num_days": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
delete_activity≈ 130 tokens
Remove an activity from a concierge itinerary day. Requires a bearer token.
Paramètres, retour & exemple (1)
Paramètres
- activity_id · string · requis
Exemple d'appel
```
{"name": "delete_activity", "arguments": {"activity_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
delete_itinerary≈ 137 tokens
Permanently delete a concierge itinerary and all its days and activities. Requires a bearer token.
Paramètres, retour & exemple (1)
Paramètres
- itinerary_id · string · requis
Exemple d'appel
```
{"name": "delete_itinerary", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
generate_itinerary_from_places≈ 376 tokens
Give at least 3 places plus optional traveller preferences and let the AI concierge build a full, bespoke day-by-day itinerary. It mines Iconic Expeditions content for real detail and synthesizes an ORIGINAL plan tailored to the guest (never a copy of a published itinerary). Attributed to the Iconic Expeditions account and made public. Returns immediately with the itinerary id + share link; poll get_itinerary for progress (generation_status: pending -> building -> complete). Requires a bearer token.
Paramètres, retour & exemple (5)
Paramètres
- title · string · requis
  Itinerary title, e.g. 'Highlights of Zimbabwe'
- places · array · requis
  At least 3 place names, e.g. ['Victoria Falls', 'Hwange', 'Mana Pools']
- language · string · optionnel · en | ru | zh
  Language for day titles, notes, and activity text: 'en' (English), 'ru' (Russian), or 'zh' (Chinese). Defaults to English.
- num_days · integer · requis
  Number of days for the trip
- preferences · string · optionnel
  Traveller preferences that should shape the plan: pace, interests, budget, travel style
Exemple d'appel
```
{"name": "generate_itinerary_from_places", "arguments": {"title": "texte", "places": [], "num_days": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_content≈ 141 tokens
Fetch a single content item by type and id, walking the content chain (WordPress -> cache). Returns the item with its `source`.
Paramètres, retour & exemple (2)
Paramètres
- id · integer · requis
  Source content id (WordPress post id)
- type · string · requis · itinerary | activity | destination | post
Exemple d'appel
```
{"name": "get_content", "arguments": {"id": 1, "type": "itinerary"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_destination≈ 90 tokens
Get full details for a single destination by slug or id.
Paramètres, retour & exemple (1)
Paramètres
- identifier · string · requis
  Either a destination id or its URL slug
Exemple d'appel
```
{"name": "get_destination", "arguments": {"identifier": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_itinerary≈ 166 tokens
Get a full itinerary with all days and activities, sorted by day number and time slot. Public itineraries are readable without a token; private ones require the owning token.
Paramètres, retour & exemple (1)
Paramètres
- itinerary_id · string · requis
  The UUID of the itinerary
Exemple d'appel
```
{"name": "get_itinerary", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_itinerary_dossier≈ 177 tokens
Read an itinerary's planning dossier: its legs, month-by-month seasonality, cost model, booking order, field notes and open choices. Public — no token needed. Returns nulls for blocks the itinerary doesn't have; older itineraries have none of them.
Paramètres, retour & exemple (1)
Paramètres
- itinerary_id · string · requis
Exemple d'appel
```
{"name": "get_itinerary_dossier", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_pricing≈ 98 tokens
List the paid concierge service tiers and their prices: itinerary verification, verification + full booking, and full guided service. Read-only and public — use this to quote a traveller before they buy.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "get_pricing", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_wp_content≈ 131 tokens
Alias of get_content, kept for backwards compatibility. Prefer get_content.
Paramètres, retour & exemple (2)
Paramètres
- id · integer · requis
  Source content id (WordPress post id)
- type · string · requis · itinerary | activity | destination | post
Exemple d'appel
```
{"name": "get_wp_content", "arguments": {"id": 1, "type": "itinerary"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_destinations≈ 132 tokens
List destinations from the database, optionally filtered by region or category.
Paramètres, retour & exemple (3)
Paramètres
- limit · integer · optionnel
- region · string · optionnel
  Filter by region name, e.g. 'Matabeleland North'
- category · string · optionnel
  Filter by category, e.g. 'National Park'
Exemple d'appel
```
{"name": "list_destinations", "arguments": {"limit": 1, "region": "texte", "category": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_itineraries≈ 76 tokens
List itineraries created by the Iconic Expeditions concierge, most recent first. Requires a bearer token.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "list_itineraries", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
price_itinerary≈ 329 tokens
Price an itinerary's cost model against a selection: a comfort tier, any per-line choices, a trip length and a traveller count. Returns the per-person line breakdown and the group total. Public — no token needed. Amounts are in minor units. Call get_itinerary_dossier first for the tier and option ids.
Paramètres, retour & exemple (5)
Paramètres
- nights · integer · optionnel
  Defaults to the cost model's reference length
- tier_id · string · optionnel
  Defaults to the cheapest tier
- option_ids · array · optionnel
  One entry per cost option group you want to choose in
- travellers · integer · optionnel
- itinerary_id · string · requis
Exemple d'appel
```
{"name": "price_itinerary", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
request_bookings≈ 212 tokens
Start a PAID booking service: verification PLUS we make all the bookings (lodges, transfers, activities, permits). Returns a Stripe checkout URL. Requires a bearer token.
Paramètres, retour & exemple (3)
Paramètres
- notes · string · optionnel
- itinerary_id · string · requis
- contact_email · string · optionnel
Exemple d'appel
```
{"name": "request_bookings", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
request_full_service≈ 232 tokens
Start a PAID full-service, fully-guided expedition with Iconic Expeditions guides. This $500 is a deposit; the final custom price is quoted by an expert afterward based on the itinerary. Returns a Stripe checkout URL. Requires a bearer token.
Paramètres, retour & exemple (3)
Paramètres
- notes · string · optionnel
- itinerary_id · string · requis
- contact_email · string · optionnel
Exemple d'appel
```
{"name": "request_full_service", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
request_verification≈ 262 tokens
Start a PAID itinerary verification. Our travel experts manually confirm availability, seasonality, routing and current lodge rates, then return a feasibility report and final price. Returns a Stripe checkout URL. Requires a bearer token.
Paramètres, retour & exemple (3)
Paramètres
- notes · string · optionnel
  Anything the experts should know (dates, group size, budget)
- itinerary_id · string · requis
- contact_email · string · optionnel
  Where to send the report + receipt
Exemple d'appel
```
{"name": "request_verification", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
search_content≈ 196 tokens
Search Iconic Expeditions content across itineraries, activities, destinations, and posts. Flows through the content chain (WordPress -> local cache -> AI fallback), so gaps WordPress doesn't cover are filled with clearly-labeled AI-synthesized results. Each item includes a `source` field (wordpress | cache | ai).
Paramètres, retour & exemple (3)
Paramètres
- type · string · requis · itinerary | activity | destination | post
  Content type to search
- search · string · optionnel
  Search keyword
- per_page · integer · optionnel
Exemple d'appel
```
{"name": "search_content", "arguments": {"type": "itinerary"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
search_wp_content≈ 141 tokens
Alias of search_content, kept for backwards compatibility. Prefer search_content.
Paramètres, retour & exemple (3)
Paramètres
- type · string · requis · itinerary | activity | destination | post
  Content type to search
- search · string · optionnel
  Search keyword
- per_page · integer · optionnel
Exemple d'appel
```
{"name": "search_wp_content", "arguments": {"type": "itinerary"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
set_itinerary_dossier≈ 1636 tokens
Write the planning layer above an itinerary's day-by-day. Every block is optional — send only the ones you mean to write. Each block you DO send REPLACES that block entirely, so restate it in full: a partial legs list silently deletes the rest of the legs. Requires a bearer token.
Paramètres, retour & exemple (8)
Paramètres
- legs · array · optionnel
  The route's chapters. Every day must belong to exactly one leg, and legs must not overlap.
- choices · array · optionnel
  Either/ors deliberately left open for the traveller
- countries · integer · optionnel
  How many countries the route crosses
- cost_model · object · optionnel
  Per-person breakdown lines, amounts per comfort tier, and any per-line choices
- field_notes · array · optionnel
  Visas, certificates, luggage limits, kit
- seasonality · object · optionnel
  One row per thing the trip is timed around, scored 0-3 across all twelve months, plus a verdict per month worth arguing about
- itinerary_id · string · requis
- booking_order · array · optionnel
  What to book, in the order it has to happen
Exemple d'appel
```
{"name": "set_itinerary_dossier", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
update_itinerary≈ 188 tokens
Update metadata (title, description, dates, public status) on a concierge itinerary. Requires a bearer token.
Paramètres, retour & exemple (5)
Paramètres
- title · string · optionnel
- is_public · boolean · optionnel
  Set false to unpublish the shareable link
- start_date · string · optionnel
- description · string · optionnel
- itinerary_id · string · requis
Exemple d'appel
```
{"name": "update_itinerary", "arguments": {"itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
write_itinerary_day_detail≈ 323 tokens
Write one day out at length — why it is shaped this way, what its timing depends on, what the alternatives cost — plus up to three callouts. Replaces that day's existing narrative and callouts. Requires a bearer token.
Paramètres, retour & exemple (4)
Paramètres
- callouts · array · optionnel
- narrative · string · requis
  Two or three short paragraphs, separated by blank lines. Plain text, no markup.
- day_number · integer · requis
- itinerary_id · string · requis
Exemple d'appel
```
{"name": "write_itinerary_day_detail", "arguments": {"narrative": "texte", "day_number": 1, "itinerary_id": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://concierge.iconic-expeditions.com/mcp