ariregister-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARIREGISTER_API_KEY | No | REST API key (Keychain fallback: service arireister-api-key). | |
| ARIREGISTER_XML_URL | No | Override the XML service URL, e.g. https://demo-ariregxmlv6.rik.ee/ for RIK's test environment. | https://ariregister.rik.ee |
| ARIREGISTER_PASSWORD | No | XML service password (used together with ARIREGISTER_USERNAME). | |
| ARIREGISTER_REST_URL | No | Override the REST API base URL. | https://api.ariregister.rik.ee |
| ARIREGISTER_USERNAME | No | XML service login username (Keychain fallback: service arireister-xml, account = username). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for the Estonian e-Business Register (Äriregister, RIK). Start with search_companies to turn a name into an 8-digit registry code; it and check_einvoice_recipients are public. get_company, find_companies, get_representation_rights, list_annual_reports, get_beneficial_owners and search_trusts use the REST API and need an API key; get_annual_report_figures, list_company_documents, get_classifier and xml_service_request use the XML service and need the contract username and password. A tool returns CREDENTIALS_MISSING when its credentials aren't set. Beneficial-owner data is restricted and every lookup is logged with the requester's identity: only call get_beneficial_owners with details the user gave for themselves. Limits: 50 000 queries per day, and one XML query at a time. Link a company's register page: https://ariregister.rik.ee/eng/company/{registry_code}.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_companiesA | Find Estonian companies and other legal persons by name, part of a name, or registry code. Public, no account needed. Returns up to 10 matches with registry code, status, legal address and the register page URL; historical names match too. Company status codes: R = registered, L = in liquidation, N = bankrupt, K = deleted. |
| check_einvoice_recipientsA | Check whether companies are in the e-invoice recipient register, i.e. whether you can send them a machine-readable e-invoice through an operator. Public, no account needed. Status OK = has a valid link in the e-invoice register (operator in |
| get_companyA | Full register data for one company (REST, needs an API key). Choose blocks with |
| find_companiesA | Search companies with filters (REST, needs an API key): name, registry code, EMTAK activity code, location, status, or a related person or company (e.g. every company where a person is a board member). Returns contacts, VAT number, address, activities and the matching related persons. Paginated (see |
| get_representation_rightsA | Who may represent companies, and how (REST, needs an API key): persons with their role and whether they can act alone ( |
| list_annual_reportsA | Annual reports filed by a company (REST, needs an API key): year, submission date, revenue, balance-sheet total, employee count, audit status, and links to the report files (PDF, BDOC/DDOC, XBRL). For the actual balance-sheet and income-statement lines use get_annual_report_figures. |
| get_beneficial_ownersA | A company's beneficial owners (REST, needs an API key and a contract that grants beneficial-owner access). This data is restricted: access needs a legal basis (e.g. a competent authority, an obliged entity under the AML act, or a legitimate interest), and RIK logs every lookup together with the requester's identity. The requester fields describe the PERSON MAKING THE QUERY and must be the real user's own details; ask the user for them and never guess or fill them in from other context. |
| search_trustsA | Search the register of trusts and similar arrangements (REST, needs an API key): trust name, status, country and the people involved (trustee UH.HALDUR, settlor UH.LOOJA, beneficiary UH.SOODUST, …). Beneficial-owner details of a trust are not requested by this tool. |
| get_annual_report_figuresA | Line items of a company's annual report: balance sheet, income statement, cash flow and so on, with this year's and the previous year's values (XML service, needs contract username and password). Without |
| list_company_documentsA | Documents in a company's public file (XML service, needs contract username and password): annual reports as PDF, BDOC/DDOC and XBRL, and articles of association, with their e-Business Register URLs (opening one needs a login there; this tool never requests the paid access token that would buy the document). Document types: A = annual report PDF, D = BDOC/DDOC, X = XBRL, P = articles of association. Report types: A = annual, V = interim, L = liquidation, P = final. |
| get_classifierA | Code lists used by the register (XML service, needs contract username and password), e.g. OIGVORMID (legal forms), EVSTAATUSED (company statuses), ISIKROLLID (person roles), RIIGID (countries), SIDEVAH (contact types), VALUUTAD (currencies). Use it to decode codes returned by the other tools. |
| xml_service_requestA | Call any e-Business Register XML (SOAP) query that has no dedicated tool, e.g. ettevotjaMuudatusedTasuline_v1 (companies changed on a date), kandedMaarused_v1 (entries and rulings for a day), aruandeMyygituluEMTAKjargi_v1 (revenue by activity), detailandmed_v2. Your contract username and password are added automatically. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target distinct resources or access modes, but search_companies vs find_companies and list_annual_reports vs list_company_documents vs get_annual_report_figures overlap enough that the agent must read descriptions carefully. The generic xml_service_request is explicitly framed as a fallback, which reduces confusion with the dedicated XML tools. Overall mostly distinct with a few avoidable boundary ambiguities.
All names use snake_case and nearly all follow a verb_noun pattern: search_companies, get_company, find_companies, list_annual_reports, check_einvoice_recipients, etc. The only clear deviation is xml_service_request, which is a noun phrase rather than an action-oriented name. The search/find distinction is intentional but still readable.
Twelve tools is well within the appropriate range for a read-only registry API and each dedicated tool maps to a meaningful capability. The generic XML tool provides an escape hatch without bloating the dedicated surface. The count is well scoped for the server's purpose.
The surface covers the core read-only lifecycle: company search, company details, representation rights, annual reports, documents, beneficial owners, trusts, e-invoice checks and classifiers. However, less common XML operations are only available through the generic xml_service_request, which requires external documentation and exact field ordering, so the dedicated surface is not fully self-contained. Minor gaps remain but can be worked around.