Remote MCP · Endpoint

Datos UY/AR MCP server

No. Datos UY/AR answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://datosuyar.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.agustinmoscoso/datos-uy-ar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
194 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Datos oficiales de Uruguay y Argentina: UI y cotizaciones del BCU, feriados AR y validación de RUT
Listing
From the official MCP registry (active).
Recent checks of Datos UY/AR
CheckedResultHandshake
2 hours agoHandshake completed194 ms
1 day agoHandshake completed217 ms
3 days agoHandshake completed196 ms
3 days agoHandshake completed183 ms
4 days agoHandshake completed227 ms
5 days agoHandshake completed204 ms
7 days agoHandshake completed223 ms
10 days agoHandshake completed265 ms
12 days agoHandshake completed200 ms
15 days agoHandshake completed196 ms
17 days agoHandshake completed187 ms
19 days agoHandshake completed200 ms
21 days agoHandshake completed226 ms
23 days agoHandshake completed191 ms
25 days agoHandshake completed236 ms

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

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