Estonia Business Register
NPM · @PIPEWORX/MCP-ESTONIA-BUSINESS-REGISTER · 2 COMPONENTS
estonia-business-register -- Estonia's e-Business Register, published as open data by RIK…
Available components
Last scanned (10 hours ago)
Scores higher than 72% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-estonia-business-register). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 998 tokens (~249/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-estonia-business-register@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-estonia-business-register |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-estonia-business-register/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635928389 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cfcfea342bb299707c0b809302dd0522ad17b68eac7ceaafd75c712bbce9c7892d6d27234d5f55561257282f195daa73e992ff9982d89ae57fdbb7972 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ee_annual_report_stats ~200
Selected financial indicators and sales-by-activity breakdowns from an Estonian entity's filed annual reports (RIK's monthly open-data extracts of e-Business Register annual reports) -- NOT full reports. Pass registry_code alone to list every year with a filed report (submission date, audited flag, filer-size category); add year for that year's figures: revenue, profit/loss, total assets, equity, average full-time-equivalent employee count, and sales revenue broken down by EMTAK activity area. Some filed reports carry metadata but no matching figures in RIK's extract (seen for some large/group filers) -- the report row still answers, with null figures.
| Name | Type | Req | Description |
|---|---|---|---|
| registry_code | string | yes | Estonian registry code (ariregistri kood), e.g. "11056239". |
| year | string | – | Report year, e.g. "2024". Omit to list every year with a filed report. |
No output schema declared.
No examples provided.
ee_beneficial_owners ~239
An Estonian entity's beneficial owners (Estonia's e-Business Register, published by RIK, the Estonian Centre of Registers and Information Systems) by registry code or exact current name: each owner's name, date of birth and nationality EXACTLY as the register itself shows them, the manner in which control is exercised (direct/indirect ownership etc.), and the start date of that holding. RIK marks this data as informative rather than authoritative, and the register carries no live per-record API for it -- this tool reads the register's own public company page, live, per request, so data_as_of reflects RIK's own last-updated date for the beneficial-owners section specifically. Anyone named here can request removal at support@pipeworx.io; a removal already on file is silently withheld and counted in withheld_by_removal_request.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Exact current registered name. Use ee_company_search first for a partial match, or pass registry_code directly if known. |
| registry_code | string | – | Estonian registry code (ariregistri kood), e.g. "11056239". |
No output schema declared.
No examples provided.
ee_company ~232
One Estonian company or other registered entity by its registry code or exact current name, from Estonia's e-Business Register (published as open data by RIK, the Estonian Centre of Registers and Information Systems). Returns identity (name, legal form, VAT number), registration status (registered/in liquidation/bankrupt), address, and currently reported EMTAK/NACE activity areas. Use for "what is the status of registry code 12417834" or "look up Bolt Technology OÜ". A company's CURRENT registered name is matched exactly -- a FORMER name (e.g. a company later renamed) will not match by name; look it up by registry code instead if known. For partial name matches use ee_company_search first.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Exact current registered name, e.g. "Bolt Technology OÜ". Case/diacritic-insensitive (works with or without õ/ä/ö/ü). Use ee_company_search for partial names. |
| registry_code | string | – | Estonian registry code (ariregistri kood), e.g. "12417834". |
No output schema declared.
No examples provided.
ee_company_search ~271
Search Estonia's e-Business Register (RIK open data) by the start of a company's current name, optionally filtered by registration status (registered, liquidation or bankrupt; any other value is refused, not ignored). Prefix match first ("Bolt" finds "Bolt Technology OÜ" but not "EuroBolt OÜ"); only when nothing starts with the text does it fall back to a weaker contains-the-text pass and report match_mode:'substring'; diacritic-insensitive, so plain-ASCII and Estonian spellings both work; the legal form is optional and can sit either side ("Tallinna Sadam", "Tallinna Sadam AS" and "AS Tallinna Sadam" all find "aktsiaselts TALLINNA SADAM"), and the company whose name matches exactly apart from its legal form is listed first. Use for "find Estonian companies named Bolt..." or to get a registry code to pass to ee_company.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results (1-100, default 20). |
| name | string | yes | Start of the company's current registered name, e.g. "Bolt". |
| status | string | – | Filter by registration status. "active" is a synonym for "registered". Case-insensitive; any other value is refused with the valid list. |
No output schema declared.
No examples provided.
How do I install the Estonia Business Register MCP server?
Estonia Business Register runs locally as an npm package, launched with npx -y @pipeworx/mcp-estonia-business-register. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-estonia-business-register
claude mcp add pipeworx-io-estonia-business-register -- npx -y @pipeworx/mcp-estonia-business-register
What is the Estonia Business Register MCP server?
Estonia Business Register is an MCP server listed in the public MCP registry as io.github.pipeworx-io/estonia-business-register. estonia-business-register -- Estonia's e-Business Register, published as open data by RIK… This page covers its npm package (@pipeworx/mcp-estonia-business-register).
Is the Estonia Business Register MCP server safe to use?
Estonia Business Register scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Estonia Business Register MCP server expose?
Estonia Business Register exposes 4 tools: ee_company, ee_company_search, ee_annual_report_stats, ee_beneficial_owners. Their descriptions and schemas cost roughly 942 tokens of context every time the server is loaded.
Is the Estonia Business Register MCP server still maintained?
Estonia Business Register is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Estonia Business Register MCP server under?
Estonia Business Register declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Estonia Business Register MCP server?
VerifyMCP ran 15 checks on Estonia Business Register, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Estonia Business Register: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.