Remote MCP · Endpoint

Messe Atlas MCP server

No. Messe Atlas answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://messeatlas.com/mcp

The last check completed an MCP handshake.

Registry name
com.messeatlas/atlas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.80 s
Tools exposed
27 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
MICE data for AI agents: trade shows, exhibitors, organizers, venues, halls, subsidies. Asia-first.
Listing
From the official MCP registry (active).
Recent checks of Messe Atlas
CheckedResultHandshake
1 hour agoHandshake completed1.80 s
6 hours agoHandshake completed1.25 s
2 days agoHandshake completed1.31 s
4 days agoHandshake completed734 ms
7 days agoHandshake completed1.19 s
9 days agoHandshake completed2.00 s
11 days agoHandshake completed1.05 s
13 days agoHandshake completed937 ms
15 days agoHandshake completed509 ms
17 days agoHandshake completed656 ms
19 days agoHandshake completed1.09 s
21 days agoHandshake completed319 ms
23 days agoHandshake completed173 ms
24 days agoHandshake completed1.41 s
25 days agoHandshake completed66 ms

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

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 Messe Atlas and makes no claim about it beyond what these checks measured.