Remote MCP · Endpoint

Meridian Dispatch MCP server

No. Meridian Dispatch answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://www.meridiandispatch.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.meridiandispatch/travel-guides
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Plan trips by chat in the Meridian Dispatch iPhone app, from cited guides to places and events.
Listing
From the official MCP registry (active).
Recent checks of Meridian Dispatch
CheckedResultHandshake
43 minutes agoHandshake completed76 ms
3 days agoHandshake completed79 ms
12 days agoHandshake completed76 ms
13 days agoHandshake completed155 ms
14 days agoHandshake completed65 ms
15 days agoHandshake completed66 ms
16 days agoHandshake completed90 ms
17 days agoHandshake completed179 ms
18 days agoHandshake completed107 ms
19 days agoHandshake completed185 ms
22 days agoHandshake completed98 ms
25 days agoHandshake completed84 ms
27 days agoHandshake completed118 ms
29 days agoHandshake completed65 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Meridian Dispatch and makes no claim about it beyond what these checks measured.