Meridian Dispatch MCP server
com.meridiandispatch/travel-guidesmeridiandispatch.comstreamable-httpv2.10.0Scanned
Plan trips by chat in the Meridian Dispatch iPhone app, from cited guides to places and events.
20 tools: 2 can delete or cancel things, 1 do something that can't be undone, 5 change things and 12 only read.
- Reads private data · 5
- Reads text others write · 4
- Can send data out · 3
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Meridian Dispatch MCP server can do
The Meridian Dispatch MCP server is published by meridiandispatch.com, a domain the MCP Registry verified. It has 20 tools. It can delete or cancel things (2 tools: edit_plan and delete_plan), do things that cannot be undone, such as sending, paying or publishing (suggest_edit) and create or change data (5 tools: create_itinerary_link, confirm_fact, suggest_place, suggest_for_my_day and 1 more). 12 tools only read.
5 tools read private data (search_guides, get_place, get_plan and 2 more); 4 tools bring in text other people can write (get_place, create_itinerary_link, get_plan and 1 more); 3 tools can send data out of your system (get_place, suggest_edit and confirm_fact). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 2.10.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
20 tools
Deletes or cancels 2Claude Code: deny
delete_planDelete a plan from the traveller's account; the app removes it on its next sync.No findings
Why it is in this group
- The name "delete_plan" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Delete a plan
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
edit_planChange 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_…No findings
Why it is in this group
- The name "edit_plan" says "edit": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Change a plan
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Can't be undone 1Claude Code: ask
suggest_editSend the Meridian Dispatch desk a correction to one of its pages.Can send data outNo findings
Why it is in this group
- The name "suggest_edit" says "edit": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- title: Suggest a correction to a Meridian Dispatch page
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 5Claude Code: ask
confirm_factTell 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 govern…Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- title: Confirm a fact on a Meridian Dispatch page is still right
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create_itinerary_linkGenerate an itinerary import link: turn a day-by-day travel itinerary into a shareable "Add Itinerary to Meridian Dispatch" link.Reads text others writeNo findings
Why it is in this group
- The name "create_itinerary_link" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create an itinerary link for the Meridian Dispatch app
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
create_planMake 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).No findings
Why it is in this group
- The name "create_plan" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Make a plan
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
suggest_for_my_dayWhat 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 Fo…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Suggest for my day
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
suggest_placeSuggest 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 r…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Suggest a place Meridian Dispatch does not cover yet
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 12Show 12 read-only tools
get_best_timeGet the best time to visit from the Meridian Dispatch guides, in one of two modes.No findings
Why it is in this group
- The name "get_best_time" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get the best time to go
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_destinationRead the Meridian Dispatch guide to one country or one town, for planning a stay there.No findings
Why it is in this group
- The name "get_destination" says "get": a word for reading.
Description, as the server wrote it 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, which town meets which need where the country has a town-by-town comparison (where_to_stay_by_need, and compare on each town), related dispatches and a citation. Use it for "what to do in X", "how many days in X", "where to stay in X" or "which town in X for beaches". 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.
Annotations the server declares
- title: Get a country or town guide
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_dispatchRead one Meridian Dispatch long-form dispatch or multi-day itinerary.No findings
Why it is in this group
- The name "get_dispatch" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a dispatch or itinerary
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_my_accountThe 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 …Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_my_account" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get my account
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_placeRead the Meridian Dispatch field record for one place: a sight, museum, beach or park, a trail or scenic drive, an event, a ski resort, or an airport.Reads private dataReads text others writeCan send data outNo findings
Why it is in this group
- The name "get_place" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "drive": it reads files.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it Read the Meridian Dispatch field record for one place: a sight, museum, beach or park, a trail or scenic drive, an event, a ski resort, or an airport. 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, an airport (airport) how to get from the terminal to each town by bus, taxi or ride-hailing app with the road distance, the arrival steps, security rules, food before and after security, airlines and the airports they fly to, what to do on a layover by time available, and what is not yet confirmed. 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, name or (for an airport) iata, 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.
Annotations the server declares
- title: Get a venue, trail, event, ski resort or airport
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_planOne 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…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_plan" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
- untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a plan
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_travel_preferencesThe 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,…Reads private dataNo findings
Why it is in this group
- The name "get_travel_preferences" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "drive": it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get my travel preferences
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_best_placesList Meridian Dispatch's ranked World's Best places: the 10 best in the world or in one country, overall or within one category.No findings
Why it is in this group
- The name "list_best_places" says "list": a word for reading.
Description, as the server wrote it List Meridian Dispatch's ranked World's Best places: the 10 best in the world or 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), and, where the list is written as an article, its standfirst, a why_go paragraph per place and its close, 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.
Annotations the server declares
- title: List the World's Best places
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_eventsList the festivals and events worth planning a trip around, from the Meridian Dispatch events guide.No findings
Why it is in this group
- The name "list_events" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List festivals and events
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_my_plansThe 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…No findings
Why it is in this group
- The name "list_my_plans" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List my plans
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_nearbyList 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.No findings
Why it is in this group
- The name "list_nearby" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List places nearby
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_guidesSearch every Meridian Dispatch travel guide by keyword: long-form dispatches, multi-day itineraries, country and town guides, venues (sights, museums, beaches, parks), trails and s…Reads private dataNo findings
Why it is in this group
- The name "search_guides" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "drive": it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search the travel guides
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
60 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 3 outbound tools breaks every one.
- Reads private data5
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__travel-guides__confirm_fact",
"mcp__travel-guides__get_place",
"mcp__travel-guides__suggest_edit"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:42 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.meridiandispatch.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://www.meridiandispatch.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (2 destructive, 1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.meridiandispatch.com/api/mcp: tools/list returned 20 tools to an anonymous client, including edit_plan (destructive), delete_plan (destructive), suggest_edit (irreversible), create_itinerary_link (write), confirm_fact (write) and 3 more
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 7 to 8
- Oct 29, 2026
- Tools that change things, listed without credentials: 4 to 7
- RFC 9728 protected resource metadata: none to https://www.meridiandispatch.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers: none to https://www.meridiandispatch.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:get_destinationOnly readsdescription
- Changed:get_placeOnly readstitledescriptioninputSchemaannotations
- Changed:list_best_placesOnly readsdescriptioninputSchema
- Changed:list_nearbyOnly readsinputSchema
- Changed:search_guidesOnly readsinputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 8.View diff
- Tools that change things, listed without credentials: 7 to 8
Tools1 changed.~1 changedView diff
- Changed:create_itinerary_linkChanges thingsinputSchema
Tools8 added, 4 changed.+8 added~4 changedView diff
- Added:create_planChanges things
- Added:delete_planDeletes or cancels
- Added:edit_planDeletes or cancels
- Added:get_my_accountOnly reads
- Added:get_planOnly reads
- Added:get_travel_preferencesOnly reads
- Added:list_my_plansOnly reads
- Added:suggest_for_my_dayChanges things
- Changed:create_itinerary_linkChanges thingsdescriptioninputSchema
- Changed:get_destinationOnly readsdescription
- Changed:get_placeOnly readsdescription
- Changed:suggest_placeChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 7; RFC 9728 protected resource metadata: none -> https://www.meridiandispatch.com/.well-known/oauth-protected-resource/api/mcp; Authorization servers: none -…View diff
- Tools that change things, listed without credentials: 4 to 7
- RFC 9728 protected resource metadata: none to https://www.meridiandispatch.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers: none to https://www.meridiandispatch.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Install
Pinned to version 2.10.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http travel-guides https://www.meridiandispatch.com/api/mcpclaude mcp add --transport http travel-guides https://www.meridiandispatch.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__travel-guides__search_guides",
"mcp__travel-guides__get_destination",
"mcp__travel-guides__get_dispatch",
"mcp__travel-guides__list_events",
"mcp__travel-guides__list_best_places",
"mcp__travel-guides__get_best_time",
"mcp__travel-guides__list_nearby",
"mcp__travel-guides__list_my_plans",
"mcp__travel-guides__get_plan",
"mcp__travel-guides__get_travel_preferences",
"mcp__travel-guides__get_my_account"
],
"ask": [
"mcp__travel-guides__get_place",
"mcp__travel-guides__create_itinerary_link",
"mcp__travel-guides__suggest_edit",
"mcp__travel-guides__confirm_fact",
"mcp__travel-guides__suggest_place",
"mcp__travel-guides__suggest_for_my_day",
"mcp__travel-guides__create_plan"
],
"deny": [
"mcp__travel-guides__edit_plan",
"mcp__travel-guides__delete_plan"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as travel-guides. Review it before you use it.
Capability tags behind 8 rules
- mcp__travel-guides__search_guides private-data
- mcp__travel-guides__get_place private-data, untrusted-input, outbound
- mcp__travel-guides__create_itinerary_link untrusted-input
- mcp__travel-guides__suggest_edit outbound
- mcp__travel-guides__confirm_fact outbound
- mcp__travel-guides__get_plan private-data, untrusted-input
- mcp__travel-guides__get_travel_preferences private-data
- mcp__travel-guides__get_my_account private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.meridiandispatch/travel-guides/verify?hash=3c08c2c9d7f77b3ffefb60262427529f518cd4aff53b7e5dbc85c8a2e887f186" | jq -e '.changed == false'Pinned hash 3c08c2c9d7f7, from Nov 15, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.meridiandispatch/travel-guides/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.meridiandispatch/travel-guides)Source: MCP Registry. Synced Nov 15, 2026, 18:17 UTC.
Meridian Dispatch MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Meridian Dispatch MCP server safe?
- No scan can promise that. What its definitions show: 20 tools, 8 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Meridian Dispatch MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: edit_plan and delete_plan.
Can the Meridian Dispatch MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: suggest_edit.
What tools does the Meridian Dispatch MCP server have?
- 20 tools: 2 destructive, 1 irreversible, 5 write, 12 read. edit_plan, delete_plan, suggest_edit, create_itinerary_link, confirm_fact, suggest_place, suggest_for_my_day, create_plan and 12 more.
Does the Meridian Dispatch MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Meridian Dispatch MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_place, suggest_edit and confirm_fact.
Has the Meridian Dispatch MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.