Remote MCP · Endpoint

Tu Lugar MCP server

No. Tu Lugar answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tulugar.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.tulugar/tulugar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
88 ms
Tools exposed
39 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and manage Paraguay & LatAm real estate from any AI assistant.
Listing
From the official MCP registry (active).
Recent checks of Tu Lugar
CheckedResultHandshake
1 hour agoHandshake completed88 ms
2 days agoHandshake completed98 ms
4 days agoHandshake completed49 ms
5 days agoHandshake completed66 ms
7 days agoHandshake completed39 ms
8 days agoHandshake completed367 ms
9 days agoHandshake completed75 ms
12 days agoHandshake completed39 ms
13 days agoHandshake completed57 ms
15 days agoHandshake completed41 ms
16 days agoHandshake completed74 ms
18 days agoHandshake completed44 ms
19 days agoHandshake completed62 ms
20 days agoHandshake completed76 ms
20 days agoHandshake completed44 ms
21 days agoHandshake completed110 ms
22 days agoHandshake completed96 ms

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

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