com.iconic-expeditions/concierge
REMOTE · CONCIERGE.ICONIC-EXPEDITIONS.COM · SCANNED OCT 4
Search Africa safari destinations, generate day-by-day itineraries, and price expert travel work.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 23 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1957 tokens (~85/item across 23 items; 23 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_itinerary" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.iconic-expeditions/concierge MCP server?
com.iconic-expeditions/concierge is a hosted endpoint at https://concierge.iconic-expeditions.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · concierge.iconic-expeditions.com
claude mcp add --transport http com-iconic-expeditions-concierge 'https://concierge.iconic-expeditions.com/mcp'
{
"mcpServers": {
"com-iconic-expeditions-concierge": {
"url": "https://concierge.iconic-expeditions.com/mcp"
}
}
} {
"servers": {
"com-iconic-expeditions-concierge": {
"type": "http",
"url": "https://concierge.iconic-expeditions.com/mcp"
}
}
} [mcp_servers.com-iconic-expeditions-concierge] url = "https://concierge.iconic-expeditions.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-iconic-expeditions-concierge": {
"type": "remote",
"url": "https://concierge.iconic-expeditions.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-iconic-expeditions-concierge --url 'https://concierge.iconic-expeditions.com/mcp' --transport streamable-http
mcp_servers:
com-iconic-expeditions-concierge:
url: "https://concierge.iconic-expeditions.com/mcp" {
"McpServers": {
"com-iconic-expeditions-concierge": {
"Transport": "http",
"Url": "https://concierge.iconic-expeditions.com/mcp"
}
}
} assistant mcp add com-iconic-expeditions-concierge -t streamable-http -u 'https://concierge.iconic-expeditions.com/mcp'
{
"mcpServers": {
"com-iconic-expeditions-concierge": {
"type": "http",
"url": "https://concierge.iconic-expeditions.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://concierge.iconic-expeditions.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=concierge.iconic-expeditions.com | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 5e12554895b68648da44d19ad614244a1fc |
| SANs: concierge.iconic-expeditions.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of concierge.iconic-expeditions.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| iconic-expeditions.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://concierge.iconic-expeditions.com/mcp | Verified | 200 | |
| http (plaintext) | http://concierge.iconic-expeditions.com/mcp | HTTPS enforced | 308 | https://concierge.iconic-expeditions.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_activity Add Activity to Day ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| day_id | string | yes | The day UUID to add the activity to |
| description | string | – | – |
| duration_minutes | integer | – | – |
| itinerary_id | string | yes | Parent itinerary UUID |
| slot | string | yes | – |
| title | string | yes | Short title for the activity |
| wp_content_id | integer | – | Source content id |
| wp_content_type | string | – | Content type to link |
No output schema declared.
No examples provided.
add_day Add Day to Itinerary ~60
Append an extra day to a concierge itinerary and increment num_days. Requires a bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| itinerary_id | string | yes | – |
| notes | string | – | – |
| title | string | – | Optional day label, e.g. 'Drive to Hwange' |
No output schema declared.
No examples provided.
create_itinerary Create Itinerary ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional short description |
| num_days | integer | yes | Number of days |
| start_date | string | – | Optional ISO date string for day 1, e.g. '2025-06-01' |
| title | string | yes | Itinerary title, e.g. '7-Day Hwange Safari' |
No output schema declared.
No examples provided.
delete_activity Delete Activity ~30
Remove an activity from a concierge itinerary day. Requires a bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | – |
No output schema declared.
No examples provided.
delete_itinerary Delete Itinerary ~35
Permanently delete a concierge itinerary and all its days and activities. Requires a bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| itinerary_id | string | yes | – |
No output schema declared.
No examples provided.
generate_itinerary_from_places Generate Itinerary from Places ~232
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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language for day titles, notes, and activity text: 'en' (English), 'ru' (Russian), or 'zh' (Chinese). Defaults to English. |
| num_days | integer | yes | Number of days for the trip |
| places | array | yes | At least 3 place names, e.g. ['Victoria Falls', 'Hwange', 'Mana Pools'] |
| preferences | string | – | Traveller preferences that should shape the plan: pace, interests, budget, travel style |
| title | string | yes | Itinerary title, e.g. 'Highlights of Zimbabwe' |
No output schema declared.
No examples provided.
get_content Get Content Item ~58
Fetch a single content item by type and id, walking the content chain (WordPress -> cache). Returns the item with its `source`.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Source content id (WordPress post id) |
| type | string | yes | – |
No output schema declared.
No examples provided.
get_destination Get Destination ~35
Get full details for a single destination by slug or id.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Either a destination id or its URL slug |
No output schema declared.
No examples provided.
get_itinerary Get Itinerary ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| itinerary_id | string | yes | The UUID of the itinerary |
No output schema declared.
No examples provided.
get_itinerary_dossier Get Itinerary Dossier ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| itinerary_id | string | yes | – |
No output schema declared.
No examples provided.
get_pricing Get Concierge Pricing ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_wp_content Get Content Item (alias) ~45
Alias of get_content, kept for backwards compatibility. Prefer get_content.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Source content id (WordPress post id) |
| type | string | yes | – |
No output schema declared.
No examples provided.
list_destinations List Destinations ~66
List destinations from the database, optionally filtered by region or category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category, e.g. 'National Park' |
| limit | integer | – | – |
| region | string | – | Filter by region name, e.g. 'Matabeleland North' |
No output schema declared.
No examples provided.
list_itineraries List Concierge Itineraries ~31
List itineraries created by the Iconic Expeditions concierge, most recent first. Requires a bearer token.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price_itinerary Price an Itinerary ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| itinerary_id | string | yes | – |
| nights | integer | – | Defaults to the cost model's reference length |
| option_ids | array | – | One entry per cost option group you want to choose in |
| tier_id | string | – | Defaults to the cheapest tier |
| travellers | integer | – | – |
No output schema declared.
No examples provided.
request_bookings Request Verification + Bookings ($100) ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | – | – |
| itinerary_id | string | yes | – |
| notes | string | – | – |
No output schema declared.
No examples provided.
request_full_service Request Full Guided Service ($500 deposit) ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | – | – |
| itinerary_id | string | yes | – |
| notes | string | – | – |
No output schema declared.
No examples provided.
request_verification Request Itinerary Verification ($50) ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | – | Where to send the report + receipt |
| itinerary_id | string | yes | – |
| notes | string | – | Anything the experts should know (dates, group size, budget) |
No output schema declared.
No examples provided.
search_content Search Content ~102
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).
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | integer | – | – |
| search | string | – | Search keyword |
| type | string | yes | Content type to search |
No output schema declared.
No examples provided.
search_wp_content Search Content (alias) ~51
Alias of search_content, kept for backwards compatibility. Prefer search_content.
| Name | Type | Req | Description |
|---|---|---|---|
| per_page | integer | – | – |
| search | string | – | Search keyword |
| type | string | yes | Content type to search |
No output schema declared.
No examples provided.
set_itinerary_dossier Write an Itinerary's Dossier ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_order | array | – | What to book, in the order it has to happen |
| choices | array | – | Either/ors deliberately left open for the traveller |
| cost_model | object | – | Per-person breakdown lines, amounts per comfort tier, and any per-line choices |
| countries | integer | – | How many countries the route crosses |
| field_notes | array | – | Visas, certificates, luggage limits, kit |
| itinerary_id | string | yes | – |
| legs | array | – | The route's chapters. Every day must belong to exactly one leg, and legs must not overlap. |
| seasonality | object | – | One row per thing the trip is timed around, scored 0-3 across all twelve months, plus a verdict per month worth arguing about |
No output schema declared.
No examples provided.
update_itinerary Update Itinerary ~78
Update metadata (title, description, dates, public status) on a concierge itinerary. Requires a bearer token.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| is_public | boolean | – | Set false to unpublish the shareable link |
| itinerary_id | string | yes | – |
| start_date | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
write_itinerary_day_detail Write a Day's Detail ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| callouts | array | – | – |
| day_number | integer | yes | – |
| itinerary_id | string | yes | – |
| narrative | string | yes | Two or three short paragraphs, separated by blank lines. Plain text, no markup. |
No output schema declared.
No examples provided.
What is the com.iconic-expeditions/concierge MCP server?
com.iconic-expeditions/concierge is an MCP server listed in the public MCP registry as com.iconic-expeditions/concierge. Search Africa safari destinations, generate day-by-day itineraries, and price expert travel work. This page covers its hosted endpoint (https://concierge.iconic-expeditions.com/mcp).
Is the com.iconic-expeditions/concierge MCP server safe to use?
com.iconic-expeditions/concierge scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.iconic-expeditions/concierge MCP server expose?
com.iconic-expeditions/concierge exposes 23 tools: search_content, search_wp_content, get_content, get_wp_content, list_destinations, and 18 more. Their descriptions and schemas cost roughly 1,957 tokens of context every time the server is loaded.
Does the com.iconic-expeditions/concierge MCP server require authentication?
No. We connected to com.iconic-expeditions/concierge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.iconic-expeditions/concierge MCP server still maintained?
com.iconic-expeditions/concierge is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.