Remote MCP · Endpoint

MyLatinLife Data MCP server

No. MyLatinLife Data answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mylatinlife.com/mcp

The last check completed an MCP handshake.

Registry name
com.mylatinlife/data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
466 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verified residency, citizenship, tax and banking data for Latin America and Latin Europe.
Listing
From the official MCP registry (active).
Recent checks of MyLatinLife Data
CheckedResultHandshake
1 hour agoHandshake completed466 ms
9 days agoHandshake completed458 ms
9 days agoHandshake completed449 ms
11 days agoHandshake completed517 ms
12 days agoHandshake completed505 ms
13 days agoHandshake completed481 ms
14 days agoHandshake completed412 ms
14 days agoHandshake completed1.03 s
16 days agoHandshake completed406 ms
19 days agoHandshake completed443 ms
21 days agoHandshake completed423 ms
24 days agoHandshake completed484 ms
26 days agoHandshake completed443 ms
28 days agoHandshake completed739 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 MyLatinLife Data and makes no claim about it beyond what these checks measured.