Remote MCP · Endpoint

Aventurator MCP server

No. Aventurator answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
com.aventurator/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
216 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Multilingual restaurant menus and local travel discovery in Lanzarote. Read-only, no API key.
Listing
From the official MCP registry (active).
Recent checks of Aventurator
CheckedResultHandshake
18 minutes agoHandshake completed216 ms
10 days agoHandshake completed176 ms
10 days agoHandshake completed186 ms
11 days agoHandshake completed193 ms
12 days agoHandshake completed350 ms
14 days agoHandshake completed249 ms
14 days agoHandshake completed213 ms
15 days agoHandshake completed197 ms
17 days agoHandshake completed209 ms
19 days agoHandshake completed185 ms
21 days agoHandshake completed197 ms
24 days agoHandshake completed333 ms
26 days agoHandshake completed170 ms
28 days agoHandshake completed192 ms

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

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