Remote MCP · Endpoint

Latvia Beneficial Owners MCP server

No. Latvia Beneficial Owners answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://gateway.pipeworx.io/latvia-beneficial-owners/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/latvia-beneficial-owners
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
47 ms
Tools exposed
45 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
latvia-beneficial-owners -- Latvia's beneficial-owners register, published as open data by LR…
Listing
From the official MCP registry (active).
Recent checks of Latvia Beneficial Owners
CheckedResultHandshake
5 hours agoHandshake completed47 ms
9 days agoHandshake completed128 ms
10 days agoHandshake completed962 ms
11 days agoHandshake completed1.04 s
12 days agoHandshake completed962 ms
14 days agoHandshake completed695 ms
14 days agoHandshake completed950 ms
15 days agoHandshake completed214 ms
17 days agoHandshake completed451 ms
19 days agoHandshake completed1.04 s
22 days agoFailed - the request timed out—
24 days agoHandshake completed2.00 s
26 days agoHandshake completed121 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 Latvia Beneficial Owners and makes no claim about it beyond what these checks measured.