# Meridian Dispatch (remote · www.meridiandispatch.com)

Plan trips by chat in the Meridian Dispatch iPhone app, from cited guides to places and events.

- Trust score: 71/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

> **Recent critical change**: Authorization (2026-10-25). See the changelog below before you install this server.

## Components

- remote · `www.meridiandispatch.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-meridiandispatch-travel-guides/api-mcp.md), [page](https://verifymcp.io/servers/com-meridiandispatch-travel-guides/api-mcp)

## Channel facts

- Endpoint: `https://www.meridiandispatch.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.8.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (edit_plan).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 6614 tokens (~330/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 52/100
  - Stability check failed: schema churn in the 29 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 15 additions.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
  - Structured output schemas are declared (60% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Meridian Dispatch MCP server?

Meridian Dispatch is a hosted endpoint at https://www.meridiandispatch.com/api/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.

### Claude

```bash
claude mcp add --transport http com-meridiandispatch-travel-guides 'https://www.meridiandispatch.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-meridiandispatch-travel-guides": {
      "url": "https://www.meridiandispatch.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-meridiandispatch-travel-guides": {
      "type": "http",
      "url": "https://www.meridiandispatch.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-meridiandispatch-travel-guides]
url = "https://www.meridiandispatch.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-meridiandispatch-travel-guides": {
      "type": "remote",
      "url": "https://www.meridiandispatch.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-meridiandispatch-travel-guides --url 'https://www.meridiandispatch.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-meridiandispatch-travel-guides:
    url: "https://www.meridiandispatch.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-meridiandispatch-travel-guides": {
      "Transport": "http",
      "Url": "https://www.meridiandispatch.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-meridiandispatch-travel-guides -t streamable-http -u 'https://www.meridiandispatch.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-meridiandispatch-travel-guides": {
      "type": "http",
      "url": "https://www.meridiandispatch.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 71, −1)

No change was recorded against any check on this day. Stability & Change Management went from 56 to 52.

### 2026-11-02 (score 72, 0)

- [functional] Server version: 2.7.0 → 2.8.0
- [functional] Server version: 2.6.0 → 2.7.0
- [cosmetic] “create_itinerary_link” added an optional parameter “car”

### 2026-11-01 (score 72, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_plan” rewrote its description, which is the text the model reads
- [functional] Server version: 2.5.0 → 2.6.0
- [functional] New tool “suggest_for_my_day”

### 2026-10-31 (score 71, 0)

- [security] Tool “edit_plan” rewrote its description, which is the text the model reads

### 2026-10-30 (score 71, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “create_itinerary_link” rewrote its description, which is the text the model reads
- [security] Tool “create_plan” rewrote its description, which is the text the model reads
- [security] Tool “get_plan” rewrote its description, which is the text the model reads
- [security] Tool “get_travel_preferences” rewrote its description, which is the text the model reads
- [cosmetic] “create_itinerary_link” added an optional parameter “airport”
- [cosmetic] “create_itinerary_link” added an optional parameter “airport_home”

### 2026-10-28 (score 70, +1)

- [security] Tool “get_place” rewrote its description, which is the text the model reads

### 2026-10-26 (score 69, 0)

- [security] Tool “create_itinerary_link” rewrote its description, which is the text the model reads
- [security] Tool “get_travel_preferences” rewrote its description, which is the text the model reads
- [functional] Server version: 2.4.0 → 2.5.0
- [cosmetic] “create_itinerary_link” added an optional parameter “fixed_dates”

### 2026-10-25 (score 69, −6)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “delete_plan”, which the server declares destructive
- [security] New tool “edit_plan”, which the server declares destructive
- [security] Tool “create_itinerary_link” rewrote its description, which is the text the model reads
- [security] Tool “get_destination” rewrote its description, which is the text the model reads
- [security] Tool “suggest_place” rewrote its description, which is the text the model reads
- [functional regression] Tool coverage: 100% → 63%
- [functional regression] Tool coverage: 100% → 93%
- [functional improvement] Schema quality: 364 → 289
- [functional] New tool “create_plan”
- [functional] New tool “get_my_account”
- [functional] New tool “get_plan”
- [functional] New tool “get_travel_preferences”
- [functional] New tool “list_my_plans”
- [cosmetic] “create_itinerary_link” reworded the description of “days”

## MCP tools (20)

### `search_guides` (~408 tokens)

Search the travel guides

Search every Meridian Dispatch travel guide by keyword: long-form dispatches, multi-day itineraries, country and town guides, venues (sights, museums, beaches, parks), trails and scenic drives, events and ski resorts. Use it first when you do not know the exact page. Once you know the place, read it in full with get_destination (a country or town), get_place (one sight, trail, event or ski resort) or get_dispatch (a dispatch or itinerary); for ranked top-ten lists use list_best_places, for a month use get_best_time. Returns up to `limit` pages ranked by relevance, each with its type, title, country, town, a one-line summary, a citable URL and when it was last updated. Ranking is keyword-based with travel synonyms; a country or month named in the query is honoured. Read-only. When nothing matches it returns an error message; retry with a broader query or a place name.

Input parameters:

- `country` (string): Return only pages in this country, by English name, e.g. "Iceland". Omit to search worldwide.
- `limit` (integer): Most results to return, 1 to 20. Defaults to 8.
- `query` (string, required): What the traveller wants, in plain words: a place name ("Kotor"), an activity and a place ("glacier hike Iceland") or a theme ("festivals in Japan").
- `region` (string): Only this part of the world. Use it for asks like "festivals in Europe"; country is more precise when the traveller names one.
- `type` (string): Return only one kind of page: dispatch (a reported long-form piece), itinerary (a multi-day country route), country or town (destination guides), venue (one sight), trail (a hike or scenic drive), ev…

Output parameters:

- `attribution` (string): The terms for quoting these pages.
- `results` (array): Matching pages, best first.

### `get_destination` (~439 tokens)

Get a country or town guide

Read the Meridian Dispatch guide to one country or one town, for planning a stay there. Returns: why go, how long to stay, the best months, getting there and around, practical FAQ answers, a structured fact sheet where one exists (nights, months, travel times in minutes, areas to stay, ranked top things, day trips, watch-outs), up to 15 ranked places worth your time with their own guide links, recommended hotels, the town guides of a country, related dispatches and a citation. Use it for "what to do in X", "how many days in X" or "where to stay in X". For a single sight, trail, event or ski resort use get_place; for a long-form dispatch use get_dispatch; to find a destination by theme use search_guides; for towns within reach use list_nearby. Two sizes: detail "summary" (the default) returns a short overview, nights, months, airports, areas to stay and the top 8 places, each with an id to pass to get_place as url; detail "full" returns everything above. Ask for "full" only when the summary lacks what the traveller needs. Matching tries a country first, then a town. A country with town guides but no country guide returns its town guides and dispatches instead. Read-only. An unknown name returns an error message.

Input parameters:

- `country` (string): The country of the town, by English name, to tell apart towns that share a name (Granada, Valencia, Mérida). Omit when name is a country or a unique town.
- `detail` (string): "summary" (default): a compact answer of a few thousand characters with place ids to drill into. "full": the whole guide (FAQ answers, full fact sheet, every ranked place, hotels), often over 15,000…
- `name` (string, required): One country or town, by English name, e.g. "Slovenia" or "Bled". Case and accents are ignored. Not a sight or region: use get_place or search_guides for those.

Output parameters:

- `best_months` (array)
- `coords_note` (string)
- `country` (string)
- `country_guide` (string): meridiandispatch.com URL.
- `detail` (string)
- `dispatches` (array): Related long-form dispatches.
- `fact_sheet` (object): Structured planning data: nights, months, getting_there, where_to_stay, top_things, day_trips, watch-outs.
- `lat` (number|null)
- `lng` (number|null)
- `name` (string)
- `note` (string)
- `overview` (array): Opening paragraphs of the guide.
- `photo` (object|null): Lead photograph: url, alt text and credit.
- `places` (array): The places worth your time, ranked.
- `places_note` (string)
- `places_total` (integer)
- `planning` (object): Short answers: days needed, best time, getting there, getting around, language, money.
- `practical` (array): Practical questions and answers not already covered by planning.
- `source` (object): How to credit this answer: show cite_as, or link url.
- `stays` (array): Hotels the guide recommends.
- `summary` (string)
- `town_guides` (array): For a country: its town guides.
- `type` (string)
- `verdict` (string)

### `get_place` (~349 tokens)

Get a venue, trail, event or ski resort

Read the Meridian Dispatch field record for one place: a sight, museum, beach or park, a trail or scenic drive, an event, or a ski resort. Returns the best time to go, how long it takes, effort, season, access, how to get there and what goes wrong, plus the best months, practical answers, a photo, the town guide link, reviews by travellers who went when there are any (traveller_reviews) and a citation; an event adds its dates and schedule, a trail its route facts. Use it once you know the place. For a whole country or town use get_destination; for a dispatch use get_dispatch; to find a place you cannot name exactly use search_guides; for what else is close use list_nearby. Give url, or name (at least one). A place mentioned on a town guide with no page of its own returns its short write-up and that guide. A URL of a town, country or dispatch page returns that guide instead. Read-only. No match returns an error message.

Input parameters:

- `country` (string): The place's country, by English name, to narrow a name shared by several places.
- `name` (string): The place's name, e.g. "Kotor Old Town" or "Grunas Waterfall". Exact names match first, then names that contain it.
- `town` (string): The town the place is in or visited from, e.g. "Kotor", to narrow a name shared by several places.
- `url` (string): The place's meridiandispatch.com page URL, from a search_guides or get_destination result. Takes priority over name.

Output parameters:

- `at_a_glance` (object): Best time, time needed, effort, season, access.
- `best_months` (array)
- `country` (string)
- `event` (object): For an event: dates, best day, when to book, where to stay, schedule.
- `lat` (number|null)
- `lng` (number|null)
- `name` (string)
- `official_tickets` (string): The place's own online ticket shop, when it has one. Never a reseller.
- `overview` (array)
- `photo` (object|null): Lead photograph: url, alt text and credit.
- `practical` (array): Questions travellers ask about the place, each {q, a}, as the page answers them. Where the page can open at its FAQ, each also has a url: cite that link when the answer came from it.
- `source` (object): How to credit this answer: show cite_as, or link url.
- `summary` (string)
- `town` (string)
- `town_guide` (string): meridiandispatch.com URL.
- `traveller_reviews` (object): Reviews by travellers who went, when there are any: verdict (Worth it to Skip it), rating out of 5, count, and up to five reviews, each {verdict, text, by, visited, countries_visited, published}. Opi…
- `type` (string)
- `why` (string)

### `get_dispatch` (~240 tokens)

Get a dispatch or itinerary

Read one Meridian Dispatch long-form dispatch or multi-day itinerary. A dispatch is a reported piece on one place: returns its headline, standfirst, opening excerpt, themes, publish date, photo and links to its town and country guides (the full text stays on the page). An itinerary is a country route over several days: returns the bases in order, nights in each, where to stay and every day's activities by part of the day, each linked to its guide. Use it only for these two kinds of page. For a country or town guide use get_destination; for one sight, trail, event or ski resort use get_place; to list dispatches on a theme use search_guides with type "dispatch" or "itinerary". Lookup order: an exact URL, then an exact slug, then the single best keyword match, so a place name returns the one most relevant dispatch. Read-only. No match returns an error message.

Input parameters:

- `query` (string, required): A dispatch or itinerary URL, its slug (e.g. "hallstatt", "montenegro-beach-six-days"), or the place it covers (e.g. "Hallstatt").

Output parameters:

- `country_guide` (string): meridiandispatch.com URL.
- `excerpt` (array)
- `headline` (string)
- `lat` (number|null)
- `lng` (number|null)
- `note` (string)
- `photo` (object|null): Lead photograph: url, alt text and credit.
- `place` (string)
- `published` (string)
- `route` (object): For an itinerary: bases, nights and day_by_day activities.
- `source` (object): How to credit this answer: show cite_as, or link url.
- `standfirst` (string)
- `themes` (array)
- `town_guide` (string): meridiandispatch.com URL.
- `type` (string)

### `list_events` (~278 tokens)

List festivals and events

List the festivals and events worth planning a trip around, from the Meridian Dispatch events guide. Returns each event's name, kind, where it is, the current edition's dates (a label plus ISO start and end), the best day to go, when to book, the next edition where announced, a citable URL and a citation line, sorted by start date. With no filter it returns every event; month keeps events with any day in that month; country keeps one country. Use get_place with an event's URL for its full record (schedule, where to stay, tips). For every kind of destination in a month, not just events, use get_best_time. Read-only. Dates are for one edition, so check the page before booking. An invalid month or no match returns an error message.

Input parameters:

- `country` (string): Keep events in this country, by English name, e.g. "Mexico". Omit for every country.
- `month` (string): An English month name ("October", or "oct") or its number, 1 to 12 ("10"). Keeps events with any day in that month. Omit for the whole year.
- `region` (string): Only this part of the world. Use it for asks like "festivals in Europe"; country is more precise when the traveller names one.

Output parameters:

- `events` (array): Events, soonest first.
- `note` (string)

### `list_best_places` (~237 tokens)

List the World's Best places

List Meridian Dispatch's ranked World's Best places: the 20 best in the world or the 10 best in one country, overall or within one category. Use it for "top things to do in X" or "best beaches in X". For one town's highlights use get_destination; for places near a point use list_nearby; for any other search use search_guides. Returns the list's title, the places in rank order (rank, name, where, a one-line summary, the place's own guide URL where one exists, and a coordinate), the other categories available for that scope, and a citation. Read-only. A country or category with no list returns an error that names the ones that exist.

Input parameters:

- `category` (string): One kind of place: landmarks, museums, towns, wilderness, hiking trails, scenic drives, parks, viewpoints, beaches, shopping, wildlife, wellness or ski resorts. Singular and plural both work. Omit fo…
- `country` (string): The country to rank, by English name, e.g. "Italy". Omit for the world list.

Output parameters:

- `list` (string)
- `other_categories` (array)
- `ranked` (array): Best first.
- `source` (object): How to credit this answer: show cite_as, or link url.

### `get_best_time` (~250 tokens)

Get the best time to go

Get the best time to visit from the Meridian Dispatch guides, in one of two modes. Give destination (a country, town, trail or ski resort) for its best months, good and avoid months, closures and crowds where known, the guide's own best-time line, and the events held there. Or give month for "where to go in March": up to 40 countries, towns, trails, ski resorts and festivals the guides recommend that month, each with its reason, events first. If both are given, destination wins. For festival dates alone use list_events; for a full planning guide use get_destination. Read-only. An unknown destination, an invalid month or neither parameter returns an error message.

Input parameters:

- `destination` (string): A country, town, trail or ski resort, by name, e.g. "Kotor" or "Niseko". Use this or month.
- `month` (string): An English month name ("October", or "oct") or its number, 1 to 12 ("10"). Use this or destination.
- `region` (string): With month: only this part of the world ("where in Asia in February"). Ignored with destination.

Output parameters:

- `avoid_months` (array)
- `best_months` (array)
- `closures`
- `crowds` (object)
- `destination` (string)
- `events_there` (array)
- `good_months` (array)
- `in_their_words` (string)
- `month` (string)
- `note` (string)
- `recommended` (array): For a month: destinations recommended then.
- `source` (object): How to credit this answer: show cite_as, or link url.

### `list_nearby` (~374 tokens)

List places nearby

List the places Meridian Dispatch covers near a place or a coordinate, nearest first, for day trips from a base or what else to see near a sight. From a town with a researched guide, it leads with day_trips: the guide's own picks, with travel mode and how long. Without type it answers a day-trip question: up to 15 towns, each once at its nearest point, with its distance, summary, guide link, best few places and dispatches; a town's own sights are left out (get_destination has them). With type it returns a flat list of up to 20 places of that kind with distances. Distances are straight-line kilometres, not by road. Give place, or lat and lng together. For the sights inside one town use get_destination; to search by theme use search_guides. Read-only. An unknown place or nothing within the radius returns an error message.

Input parameters:

- `lat` (number): Latitude of the starting point in decimal degrees, e.g. 42.42. Give with lng, instead of place.
- `lng` (number): Longitude of the starting point in decimal degrees, e.g. 18.77. Give with lat, instead of place.
- `place` (string): The starting point: a place name or meridiandispatch.com URL, e.g. "Kotor". Use this, or lat and lng.
- `radius_km` (number): How far to look, in straight-line kilometres, 1 to 200. Defaults to 40; use 60 to 100 for a day trip by car.
- `type` (string): Return a flat list of only this kind of place, e.g. "trail" or "event". Omit for the day-trip view grouped by town.

Output parameters:

- `from`: The starting place's name, or the coordinate given.
- `note` (string)
- `places` (array): With type: places, nearest first.
- `radius_km` (number)
- `same_town` (string)
- `towns` (array): Without type: towns, nearest first.

### `create_itinerary_link` (~858 tokens)

Create an itinerary link for the Meridian Dispatch app

Generate an itinerary import link: turn a day-by-day travel itinerary into a shareable "Add Itinerary to Meridian Dispatch" link. Use it only when the traveller wants a link to share or open elsewhere. To save a trip to the traveller's own account, privately, use create_plan (or edit_plan for one they have): that needs no link and can be deleted. To draft the plan itself, use get_destination, get_dispatch and get_place first and link places with their meridiandispatch.com URLs; for a trip the traveller will take themselves, read get_travel_preferences first (it needs sign-in) and fit the hotels, pace and routing to it. Opening the link on an iPhone with the Meridian Dispatch app shows the trip and adds it to the Plan tab as a new plan, after the traveller picks the first day; anywhere else it opens a web preview of the days. Days are numbered (day 1, 2, 3) or dated, and every day needs a hotel stay or its own city. A dated link opens on its dates, which the traveller can still move. When the dates are not negotiable (a trip built around a festival, a match, a concert or any event on fixed days), date every day and set fixed_dates: the app then adds the trip on exactly those dates with no date picker, and the link's page tells the traveller so. A place given with its meridiandispatch.com page URL arrives with that page's field record. Each call creates a new, public, permanent link that cannot be deleted (not idempotent). Anyone with it sees the trip's dates, towns, stops and hotel names; booking references, emails and phone numbers are removed. Tell the traveller this before making one. Returns the link, ready-made markdown, counts of days and items, and the places matched and not matched to the guides. An invalid itinerary returns an error listing every problem; too many links in an hour returns a rate-limit error.

Input parameters:

- `airport` (string): IATA code of the airport to fly into, e.g. "GDN". The app books the flight in to it on day 1 instead of guessing (a country's busiest airport is often the wrong one: Warsaw for Gdańsk).
- `airport_home` (string): IATA code of the airport to fly home from, when it differs from airport.
- `car` (object): A rental car the trip needs (a road trip, or days in the countryside). The app adds it as a car rental still to book and draws those days' travel as driving. from_day and to_day are day numbers on bo…
- `country_code` (string, required): ISO 3166 alpha-2 code of the main country, e.g. "ME".
- `days` (array, required): The days in order, each with what to do. Number every day or date every day, not a mix. Every day needs its own city or a stay (in stays) whose check-in to check-out, inclusive, covers it; the error…
- `fixed_dates` (boolean): true when the trip only works on its dates, e.g. it is built around an event. Needs a date on every day (not day numbers). The app imports it on those dates and the traveller cannot move them. Leave…
- `stays` (array): Where the traveller sleeps, by hotel name. Optional: a day not between a stay's check-in and check-out (inclusive) must give its own city, which places it in the app until a hotel is added. check_in_…
- `summary` (string): One short paragraph shown under the title: what the trip is and why it works.
- `title` (string, required): The trip, e.g. "Six days on the Montenegro coast".

Output parameters:

- `dated`
- `days`
- `fixed_dates`
- `items`
- `link_text` (string)
- `markdown` (string)
- `opens` (string)
- `places_matched_to_guides`
- `title` (string)
- `unmatched_places` (array): Places that matched nothing in the guides; resend with the proper name to attach a location.
- `url` (string): The link to give the traveller.

### `suggest_edit` (~392 tokens)

Suggest a correction to a Meridian Dispatch page

Send the Meridian Dispatch desk a correction to one of its pages. Use it when the traveller tells you something on a meridiandispatch.com page is wrong or out of date (a place has closed, moved, been renamed, changed its hours or now needs booking). Pass a source_url when the traveller gives one or one supports what they said. Do not use it for opinions, reviews or style. To read a page first, use get_place, get_destination or get_dispatch. Quote current_text exactly as it appears on the page (or in this server's answer about it); a quote that is not found is refused. Nothing changes immediately: the desk verifies every suggestion against its own sources before editing. Returns whether the suggestion was received and its id; the same suggestion sent twice is recorded once. A page that is not on meridiandispatch.com, a quote not on the page, or too many suggestions in an hour (per conversation, per address or per page) returns an error saying which.

Input parameters:

- `current_text` (string, required): The wrong text, quoted exactly from the page or from this server's answer about it.
- `field` (string): What kind of fact is wrong: status (closed, reopened), hours, location, access (booking, tickets, transport), dates (an event), name, description, or other.
- `proposed_text` (string, required): What it should say instead, as plain text. Facts only, no prices.
- `reason` (string, required): Why it is wrong, e.g. "The traveller says it closed in spring 2026" or "The official site lists new hours".
- `source_url` (string): Optional: a page that supports the correction, ideally the place's own website. It speeds review.
- `url` (string, required): The meridiandispatch.com page to correct, as returned in source.url or canonical_url.

Output parameters:

- `duplicate` (boolean)
- `id` (string)
- `next` (string): What happens to the suggestion now.
- `page` (string)
- `received` (boolean)

### `confirm_fact` (~258 tokens)

Confirm a fact on a Meridian Dispatch page is still right

Tell the Meridian Dispatch desk that a fact on one of its pages still holds, with the current, independent source that shows it (the place's official website, an operator or government page). Use it when the traveller confirms a fact on a page (they were just there, or asked you to check it and the source agrees). If the fact is wrong instead, use suggest_edit. Quote checked_text exactly as the page (or this server's answer) gives it and pass the source; a quote not on the page, or a source on meridiandispatch.com, is refused. A confirmation is recorded as a signal for the desk to review and counted per page; it does not mark the page verified, change its date or reorder any list, and the page itself does not change. The same confirmation sent twice is recorded once. Returns whether it was recorded.

Input parameters:

- `checked_text` (string, required): The fact you checked, quoted from the page, e.g. a facts_to_check text.
- `source_url` (string, required): Where you checked it: a current, authoritative page that is not on meridiandispatch.com.
- `url` (string, required): The meridiandispatch.com page, as returned in source.url.

Output parameters:

- `duplicate` (boolean)
- `next` (string)
- `page` (string)
- `received` (boolean)

### `suggest_place` (~335 tokens)

Suggest a place Meridian Dispatch does not cover yet

Suggest a town, sight, walk, museum, event, ski resort, food area or hotel that Meridian Dispatch has no page for, so the desk can research and add it to this free, shared travel reference. Use it only when the traveller asks you to, or agrees when you offer, for somewhere the guides do not cover (search_guides or get_destination found nothing) that is real and open. Do not call it on your own for places you recommend or put in a plan. Single restaurants, bars and shops are not listed; a food street, market or bar district is. source_url is required: the place's official website or another current page showing it exists. A place already covered returns its page instead of a suggestion. Nothing is published straight away: the desk researches every suggestion first. The same place suggested twice is recorded once. Returns whether it was received.

Input parameters:

- `country` (string, required): English country name, e.g. "Slovenia".
- `kind` (string): What it is. stay is a hotel worth the trip in itself.
- `lat` (number): Latitude, if known.
- `lng` (number): Longitude, if known.
- `name` (string, required): The place's proper name, e.g. "Lake Bohinj".
- `source_url` (string, required): The place's official website, or another current page showing it exists and is open.
- `town` (string): The nearest town, when the place is not a town itself.
- `why` (string, required): One or two sentences: what it is and why a traveller would go. Facts only, no prices.

Output parameters:

- `already_covered` (string)
- `duplicate` (boolean)
- `id` (string)
- `next` (string)
- `received` (boolean)

### `list_my_plans` (~111 tokens)

List my Meridian Dispatch plans

The signed-in traveller's trip plans in the Meridian Dispatch app: id, title, dates, countries, number of days planned (the app makes days as the traveller fills them, so it can be fewer than the dates span), seq (the plan's version), whether the app has taken in the latest version, and when it last changed. Needs the traveller to sign in to Meridian Dispatch the first time (the client is asked to authorise). Use get_plan for one plan's days and places.

### `get_plan` (~200 tokens)

Get one of my plans

One of the signed-in traveller's plans, day by day: each day's date, town and stops (with each stop's id, time, minutes, category, visitNote (what the traveller does there that day), note (the place's advisory), ticketsURL (its booking page) and, for a table, tour or ticket, booked (true held, false still to book; a place with neither is JUST TURN UP, nothing to reserve)); a titleless freeform stop is marked role transfer, note or alternative), its bookings (with booked or still to book, and their details: a flight's airline, number, airports, terminals, seat and times; a hotel's address and check-in/out times; a train's operator and stations; a car rental's desks), and seq, the version to send back with edit_plan as base_seq. Needs sign-in.

Input parameters:

- `plan_id` (string, required): The plan id from list_my_plans.

### `suggest_for_my_day` (~325 tokens)

Suggest places for a day of my plan

What to do on one day of the signed-in traveller's plan: places near that day's hotel (or its town, when the hotel cannot be placed), ranked for THIS traveller the way the app's For You list ranks them: their travel preferences, how full the day already is for their pace, what the rest of the trip already holds (no fourth museum in a row), what they have planned on past trips, and how famous and how well travellers rate each place. Each place comes with why (the reason it is on the list for them, in the app's words), must_see, distance_miles from the anchor, its description, and its Meridian Dispatch page when it has one. Places already on the plan are left out. The ranking draws only on the Meridian Dispatch guides, so a thin town gives a short list; notes says what the ranking could not know (it cannot see the traveller's photo journal, so a place they have been can still appear). Pass day as the day number from the plan's first date (1 is the first day), or date. Use get_plan first if you need the plan id or the day. Needs sign-in.

Input parameters:

- `date` (string): Or the day's date, YYYY-MM-DD, instead of day.
- `day` (integer): Which day, counted from the plan's first date: 1 is the first day. Default 1.
- `limit` (integer): How many places, 10 by default.
- `plan_id` (string, required): The plan id from list_my_plans.

### `create_plan` (~172 tokens)

Make a new plan

Make a new plan in the traveller's Meridian Dispatch app: a title, a first day and a number of days, optionally with ops to fill it (the same ops as edit_plan). It appears on the website at once and in the app on its next sync. A free account holds one plan; members have as many as they like. Read get_travel_preferences before filling it, so the hotels, pace and routing fit how this traveller travels. Needs sign-in.

Input parameters:

- `country_codes` (array): ISO alpha-2 codes, the main country first.
- `days` (integer, required): How many days.
- `ops` (array): Optional: the same ops as edit_plan, applied at once.
- `start_date` (string, required): The first day, YYYY-MM-DD.
- `title` (string, required)

### `edit_plan` (~277 tokens)

Change one of my plans

Change a plan with a list of ops (see the ops schema), applied in order, all or nothing; days are named by date (YYYY-MM-DD), set_start_date moves every day and booking, and close_day takes out a day between the first and last and moves every later day one date earlier (bookings keep their dates). base_seq is required: the seq from get_plan, so a plan changed elsewhere since you read it is refused rather than overwritten; on a conflict, read it again and redo the edit. Stop and booking ids come from get_plan. Prefer places from get_destination or get_place (meridian_url), so the map can place them; title each place by its proper name with what the traveller does there in visitNote, give every other real place its lat and lng, and every place a time, in the order of the day, so the app can draw the travel between them (a place without a time is timed after the one before it). Ask the traveller before removing anything. Needs sign-in.

Input parameters:

- `base_seq` (integer, required): The seq from get_plan or list_my_plans. Required.
- `ops` (array, required)
- `plan_id` (string, required)
- `verbose` (boolean): Return the whole plan. By default the reply shows only the days and bookings the edit touched.

### `get_travel_preferences` (~332 tokens)

Get my travel preferences

The signed-in traveller's travel preferences, as set in the Meridian Dispatch app (How you like to travel): how much they like each kind of travel (coast, old towns, ancient sites, nature, scenic drives, big cities, hiking, museums, food, nightlife, snow, wellness: love, like, sometimes or not for me), the stays they like, their hotel level (budget, mid-range, luxury, ultra luxury: a level in words, never a price) and where their hotels sit (old town, beach, countryside...), their pace (one base, a few bases, always moving), how far a trip goes (stay put, a region, cover ground) and how they get around (drive, trains, a mix), the shape of their days (packed or unhurried, early or late starts, evenings), how they fly (direct, connecting, stopovers) and in which cabin, the airport they fly from (with its IATA code, the other nearby airports they use, and the city code such as NYC or LON when any airport in that city will do), whether they choose main cities or go deep into a country, whether they want new places or old favourites, and the countries they have been to (ISO codes). Worked out in the app from what they actually did, or set by them. Use it to pick bases and hotels at their level, size a day to their pace, route a trip the way they travel, start and end the flights at their home airport, and tell new countries from ones they know. Needs sign-in.

### `get_my_account` (~84 tokens)

Which account am I signed in as

The Meridian Dispatch account this connection is signed in to: the name (and email, unless the traveller hid it from Apple), when it was made, whether the app on a phone is signed in to it, its plan titles, and whether travel preferences are saved. Use it to confirm the account before editing, since a traveller can hold two Apple accounts. Needs sign-in.

### `delete_plan` (~47 tokens)

Delete one of my plans

Delete a plan from the traveller's account; the app removes it on its next sync. Only when the traveller has asked for it. Needs sign-in.

Input parameters:

- `plan_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-meridiandispatch-travel-guides/api-mcp#diagnostics

## Score history

- 2026-11-04: 71
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 69
- 2026-10-24: 75
- 2026-10-23: 75
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 72
- 2026-10-10: 72
- 2026-10-07: 72
- 2026-10-04: 72
- 2026-10-03: 72
- 2026-10-02: 71

## Common questions

### What is the Meridian Dispatch MCP server?

Meridian Dispatch is an MCP server listed in the public MCP registry as com.meridiandispatch/travel-guides. Plan trips by chat in the Meridian Dispatch iPhone app, from cited guides to places and events. This page covers its hosted endpoint (https://www.meridiandispatch.com/api/mcp).

### Is the Meridian Dispatch MCP server safe to use?

Meridian Dispatch scores 71 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 Meridian Dispatch MCP server expose?

Meridian Dispatch exposes 20 tools: search_guides, get_destination, get_place, get_dispatch, list_events, and 15 more. Their descriptions and schemas cost roughly 5,966 tokens of context every time the server is loaded.

### Does the Meridian Dispatch MCP server require authentication?

No. We connected to Meridian Dispatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Meridian Dispatch MCP server still maintained?

Meridian Dispatch is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.meridiandispatch.com/api/mcp
- Website: https://www.meridiandispatch.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-meridiandispatch-travel-guides/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-meridiandispatch-travel-guides/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-meridiandispatch-travel-guides/api-mcp