mcp-registry/com.iconic-expeditions/concierge · v2.0.0
As of 2026-10-17 16:58 UTC, the Iconic Expeditions Concierge MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Search Africa safari destinations, generate day-by-day itineraries, and price expert travel work.
Claude Code
claude mcp add --transport http iconic-expeditions-concierge-mcp-server https://concierge.iconic-expeditions.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"iconic-expeditions-concierge-mcp-server": {
"type": "http",
"url": "https://concierge.iconic-expeditions.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool definition(s) exceed ~1,200 tokens each (largest: set_itinerary_dossier, ~1,685).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,085 tokens every session.
23 of 23 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
30 parameter(s) across 17 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
7 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
Handshake + tools/list takes ~1,895 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 17 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.iconic-expeditions%2Fconcierge/fixes
{
"name": "add_activity",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"itinerary_id",
"day_id",
"slot",
"title"
],
"properties": {
"slot": {
"enum": [
"morning",
"afternoon",
"evening"
],
"type": "string"
},
"title": {
"type": "string",
"minLength": 1,
"description": "Short title for the activity"
},
"day_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The day UUID to add the activity to"
},
"description": {
"type": "string"
},
"itinerary_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "Parent itinerary UUID"
},
"wp_content_id": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Source content id"
},
"wp_content_type": {
"enum": [
"itinerary",
"activity",
"destination",
"post"
],
"type": "string",
"description": "Content type to link"
},
"duration_minutes": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 5
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Add Activity to Day"
}{
"name": "add_day",
"description": "Append an extra day to a concierge itinerary and increment num_days. Requires a bearer token.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"itinerary_id"
],
"properties": {
"notes": {
"type": "string"
},
"title": {
"type": "string",
"description": "Optional day label, e.g. 'Drive to Hwange'"
},
"itinerary_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Add Day to Itinerary"
}{
"name": "create_itinerary",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"title",
"num_days"
],
"properties": {
"title": {
"type": "string",
"minLength": 1,
"description": "Itinerary title, e.g. '7-Day Hwange Safari'"
},
"num_days": {
"type": "integer",
"maximum": 30,
"minimum": 1,
"description": "Number of days"
},
"start_date": {
"type": "string",
"description": "Optional ISO date string for day 1, e.g. '2025-06-01'"
},
"description": {
"type": "string",
"description": "Optional short description"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create Itinerary"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.iconic-expeditions/concierge"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.iconic-expeditions/concierge"}) over MCP.
set_itinerary_dossier ~1,685 tokensadd_activity ~390 tokensgenerate_itinerary_from_places ~389 tokensprice_itinerary ~341 tokenswrite_itinerary_day_detail ~332 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.iconic-expeditions%2Fconcierge?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.iconic-expeditions%2Fconcierge?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.iconic-expeditions%2Fconcierge.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.iconic-expeditions%2Fconcierge.svg :target: https://glimind.com/server/mcp-registry%2Fcom.iconic-expeditions%2Fconcierge?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d3dbe5211f650f0e…, first seen 2026-10-17, included at leaf 6110 of 17,931. Version history · verify what your client received.
Compare: most reliable data servers · most reliable other servers · most reliable retrieval servers · most reliable finance servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 16:58 UTC, the Iconic Expeditions Concierge MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Iconic Expeditions Concierge MCP server advertises 23 tools, including add_activity, add_day, create_itinerary, delete_activity, delete_itinerary.
Point your MCP client at this streamable-http endpoint: https://concierge.iconic-expeditions.com/mcp
Glimind scanned all 23 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.