Remote MCP · Endpoint

Data Lv MCP server

No. Data Lv answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/data-lv/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/data-lv
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
125 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Latvia Open Data (data.gov.lv) CKAN MCP.
Listing
From the official MCP registry (active).
Recent checks of Data Lv
CheckedResultHandshake
2 hours agoHandshake completed125 ms
1 day agoHandshake completed66 ms
2 days agoHandshake completed140 ms
3 days agoHandshake completed101 ms
4 days agoHandshake completed90 ms
5 days agoHandshake completed82 ms
6 days agoHandshake completed227 ms
8 days agoHandshake completed219 ms
11 days agoHandshake completed73 ms
13 days agoHandshake completed411 ms
16 days agoHandshake completed59 ms
18 days agoHandshake completed110 ms
20 days agoHandshake completed66 ms
22 days agoHandshake completed57 ms
24 days agoHandshake completed65 ms
26 days agoHandshake completed62 ms
27 days agoHandshake completed73 ms
29 days agoHandshake completed50 ms

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

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