Remote MCP · Endpoint

Venues Abroad MCP server

No. Venues Abroad answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://venuesabroad.com/mcp

The last check completed an MCP handshake.

Registry name
com.venuesabroad/wedding-venues-portugal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
478 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Wedding venues and planners in Portugal: capacity, rooms, catering, each fact with its source.
Listing
From the official MCP registry (active).
Recent checks of Venues Abroad
CheckedResultHandshake
2 hours agoHandshake completed478 ms
2 days agoHandshake completed519 ms
4 days agoHandshake completed468 ms
6 days agoHandshake completed556 ms
8 days agoHandshake completed652 ms
10 days agoHandshake completed487 ms
12 days agoHandshake completed460 ms
14 days agoHandshake completed455 ms
16 days agoHandshake completed506 ms
17 days agoHandshake completed498 ms
18 days agoHandshake completed490 ms
21 days agoHandshake completed482 ms
22 days agoHandshake completed470 ms
24 days agoHandshake completed549 ms

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

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