MCP.Market

Estonia Business Register MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/estonia-business-register·v0.2.1

estonia-business-register -- Estonia's e-Business Register, published as open data by RIK…

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Estonia Business Register yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Estonia Business Register tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Estonia Business Register 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
158 ms
faster than 71% of 30,031 servers

Release history: 6 versions in the registry since 2026-10-13, latest 2026-11-01, typically one every 4 days.

Install Estonia Business Register in Claude Code, Cursor or VS Code

claude mcp add --transport http estonia-business-register https://gateway.pipeworx.io/estonia-business-register/mcp
Add to Cursor

What the publisher says

From the Estonia Business Register repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/estonia-business-register

Estonia's e-Business Register, published as open data by RIK (the Estonian Centre of Registers and Information Systems): every registered, liquidating or bankrupt entity's identity, legal form, status and address, its currently reported activity areas (EMTAK/NACE), and selected financial indicators and sales-by-activity breakdowns from filed annual reports. Fleet #2927.

Part of Pipeworx — an MCP gateway connecting AI agents to 1773+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

RIK publishes no live per-record API — only bulk open-data files — so Pipeworx keeps a daily-refreshed copy of the register.

Tools

its exact current registered name: identity (name, legal form, VAT number), registration status, address and currently reported EMTAK/NACE activity areas. A company's former name (before a rename) will not match by name — look it up by registry code instead. For partial names, use eecompanysearch first.

  • eecompany(registrycode?, name?) — one entity by its registry code or

company's current name (prefix match only — "Bolt" finds "Bolt Technology OÜ" but not "EuroBolt OÜ"), diacritic-insensitive, optionally filtered by registration status.

  • eecompanysearch(name, status?, limit?) — search by the start of a

reports: pass registrycode alone to list every year with a filed report (submission date, audited flag, filer-size category); add year for that year's selected financial indicators (revenue, profit/loss, total assets, equity, average FTE employee count) and sales revenue broken down by EMTAK activity area. Not full reports** — only the indicators RIK's own extract tags with a standardized element name. Some filed reports (seen for some large/group filers) carry metadata but no matching figures in RIK's extract; the report row still answers, with null figures, rather than a silent empty result.

  • eeannualreportstats(registrycode, year?) — from filed annual

Every response carries dataasof (the day the mirror was last refreshed), source and (where licence terms apply) licence.

Matching a renamed entity

RIK's basic/general extracts carry only each entity's current name — the register data carries no former-name index. A well-known example: the company now named "Microsoft Development Center Estonia OÜ" (registry code 11056239) traded as "Skype Technologies OÜ" from 2004 until a 2021 rename. eecompany(name: "Skype Technologies") correctly returns notfound with a hint to try the registry code; eecompany(registrycode: "11056239") resolves it.

Status codes

statuscode is one of R (registered/active), L (in liquidation) or N (bankrupt) — the three statuses RIK's basic open-data extract carries. A statuslabel field spells these out in English; status.text_et keeps RIK's own Estonian wording alongside it.

Activity areas

eecompany's activities list and eeannualreportstats' sales breakdown use Estonia's EMTAK classification (with the corresponding EU NACE code alongside), reported as of the mirror's dataasof date — historical/ended activity-area entries are not carried.

Auth

Keyless. The tools answer only through the Pipeworx gateway, which holds the copy of the register; a standalone npm install has no data to read, and every tool throws a clear "not bound in this runtime" error there instead of returning an empty list.

Data sources

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Estonia Business Register: common questions

Is Estonia Business Register MCP server safe?
Mostly: it is graded B (77/100). Read the Estonia Business Register safety report
How do I install Estonia Business Register?
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 Estonia Business Register need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Estonia Business Register maintained?
The last commit was 22 days ago (2026-10-13). The latest release is v0.2.1.
Is Estonia Business Register up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Estonia Business Register 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 158 ms (faster than 71% of 30,031 servers). Full comparison.

More from pipeworx-io →