Remote MCP · Endpoint

Datos UY/AR MCP server

No. Datos UY/AR answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://api-datos-uy-ar.vercel.app/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
220 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 13 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
37 minutes agoHandshake completed220 ms
4 days agoHandshake completed187 ms
7 days agoHandshake completed395 ms
16 days agoHandshake completed400 ms
16 days agoHandshake completed179 ms
18 days agoHandshake completed195 ms
19 days agoHandshake completed203 ms
20 days agoHandshake completed195 ms
21 days agoHandshake completed216 ms
22 days agoHandshake completed213 ms
23 days agoHandshake completed277 ms
26 days agoHandshake completed183 ms
29 days agoHandshake completed197 ms

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

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.