
Latvia Beneficial Owners MCP server
online · 100% uptimelatvia-beneficial-owners -- Latvia's beneficial-owners register, published as open data by LR…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Latvia Beneficial Owners yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Latvia Beneficial Owners tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Latvia Beneficial Owners compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 293 ms
- faster than 49% of 30,031 servers
Release history: 3 versions in the registry since 2026-10-19, latest 2026-11-02, typically one every 10 days.
Install Latvia Beneficial Owners in Claude Code, Cursor or VS Code
claude mcp add --transport http latvia-beneficial-owners https://gateway.pipeworx.io/latvia-beneficial-owners/mcp
What the publisher says
From the Latvia Beneficial Owners repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/latvia-beneficial-owners
A Latvian legal entity's beneficial owners -- forename, surname, date of birth, nationality, country of residence and registration date -- from Latvia's beneficial-owners open data, published by LR Uznemumu registrs (Latvia Enterprise Register).
Part of Pipeworx — an MCP gateway connecting AI agents to 1847+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Fleet #3332, Bruce's build-names ruling (#3329, CLAUDE.md "What we will source" -> personal data). Loaded live 2026-10-19 (Bruce, direct): 199,964 lvbeneficialowners rows across 164,174 entities, verified table-count-matched against the ingest manifest.
Tools
file for one Latvian legal entity, by its unique registration number (e.g. "40008018725"). Returns each owner's forename+surname, date of birth, the register's own partially-masked personal code, nationality and country of residence (ISO-2 codes -- never a street address), and the date the holding was registered. A registration number with no rows answers found: false, reason: "not_held", not a bare [] -- a company can genuinely have no beneficial-owner entry on file.
- lvbeneficialowners(registration_number) -- every beneficial owner on
Auth
Keyless. The tool answers only through the Pipeworx gateway, which holds the D1 mirror; a standalone npm install has no data to read, and the tool throws a clear "not bound in this runtime" error there instead of returning an empty list.
Personal data
Beneficial owners' names, dates of birth, and nationality/residence (country-level only) are served under Bruce's build-names ruling (fleet #3329/#3332). A shared removal mechanism (@pipeworx/shared's applyRemovals, the same one sos-entities uses under the 2026-10-08 names-and-roles ruling) withholds any name on request to support@pipeworx.io -- withheldbyremoval_request on every response says how many were suppressed for that lookup. No address of any kind (the residence field is a country code, confirmed against a live sample of the open-data file -- never a street address) is collected or served.
Data sources
data. Licence: CC0-1.0 (public domain dedication), published on Latvia's national open-data portal. Refreshed by the publisher on its own schedule (observed daily); this pack refreshes on the same cadence once the daily workflow is applied (currently a proposal -- proposals/agent-config/.github/workflows/latvia-beneficial-owners-refresh.yml -- CLAUDE.md's agent-config-paths push ruleset blocks a direct .github/workflows/ edit, so a human applies it). The exact download route lives only in scripts/latvia-beneficial-owners/refresh.sh (CLAUDE.md step 9b).
- LR Uznemumu registrs (Latvia Enterprise Register), beneficial owners open
Refreshing the mirror
bash scripts/latvia-beneficial-owners/refresh.sh build # download + build local SQLite; no remote writes
bash scripts/latvia-beneficial-owners/refresh.sh load # the above, then replace the D1 tables and verifyAutomated daily once the proposed workflow above is applied; until then, run by hand or via gh workflow run after it lands.
Schema
scripts/latvia-beneficial-owners/schema.sql: lvbeneficialowners (one row per owner-entity pair) + lvmeta (key/value: dataas_of, source, licence). Must stay in sync with src/store.ts's BeneficialOwnerRow.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"latvia-beneficial-owners": {
"url": "https://gateway.pipeworx.io/latvia-beneficial-owners/mcp"
}
}
}What this endpoint actually serves
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Latvia Beneficial Owners: common questions
- Is Latvia Beneficial Owners MCP server safe?
- Mostly: it is graded B (77/100). Read the Latvia Beneficial Owners safety report
- How do I install Latvia Beneficial Owners?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Latvia Beneficial Owners need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Latvia Beneficial Owners maintained?
- The last commit was 15 days ago (2026-10-19). The latest release is v0.2.1.
- Is Latvia Beneficial Owners up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Latvia Beneficial Owners compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 293 ms (faster than 49% of 30,031 servers). Full comparison.