Remote MCP · Endpoint

Iberá Experience MCP server

No. Iberá Experience answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.iberaexperience.com/mcp

The last check completed an MCP handshake.

Registry name
com.iberaexperience/ibera-experience
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Iberá Wetlands (Argentina) travel guide: gateways, routes, 500+ local providers, bookable trips.
Listing
From the official MCP registry (active).
Recent checks of Iberá Experience
CheckedResultHandshake
1 hour agoHandshake completed52 ms
22 hours agoHandshake completed105 ms
1 day agoHandshake completed68 ms
3 days agoHandshake completed80 ms
5 days agoHandshake completed54 ms
7 days agoHandshake completed79 ms
10 days agoHandshake completed61 ms
12 days agoHandshake completed46 ms
14 days agoHandshake completed55 ms
16 days agoHandshake completed69 ms
18 days agoHandshake completed42 ms
20 days agoHandshake completed60 ms
22 days agoHandshake completed47 ms
23 days agoHandshake completed91 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 Iberá Experience and makes no claim about it beyond what these checks measured.