Remote MCP · Endpoint

Landing en 24h MCP server

No. Landing en 24h answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://landingen24h.com/mcp

The last check completed an MCP handshake.

Registry name
com.landingen24h/landing-en-24h
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
575 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Argentina data tools: dolar blue/MEP/CCL, INDEC inflation, feriados, CUIT/CBU, FX; x402 pay-per-call
Listing
From the official MCP registry (active).
Recent checks of Landing en 24h
CheckedResultHandshake
1 hour agoHandshake completed575 ms
3 days agoHandshake completed221 ms
12 days agoHandshake completed265 ms
12 days agoHandshake completed242 ms
14 days agoHandshake completed382 ms
15 days agoHandshake completed135 ms
16 days agoHandshake completed319 ms
17 days agoHandshake completed88 ms
18 days agoHandshake completed113 ms
19 days agoHandshake completed307 ms
22 days agoHandshake completed181 ms
25 days agoHandshake completed96 ms
27 days agoHandshake completed503 ms

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

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 Landing en 24h and makes no claim about it beyond what these checks measured.