Skip to main content
Glama
ariregister-mcp

ariregister-mcp

by aanndryyyy

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ARIREGISTER_API_KEYNoREST API key (Keychain fallback: service arireister-api-key).
ARIREGISTER_XML_URLNoOverride the XML service URL, e.g. https://demo-ariregxmlv6.rik.ee/ for RIK's test environment.https://ariregister.rik.ee
ARIREGISTER_PASSWORDNoXML service password (used together with ARIREGISTER_USERNAME).
ARIREGISTER_REST_URLNoOverride the REST API base URL.https://api.ariregister.rik.ee
ARIREGISTER_USERNAMENoXML 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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 service_provider), MR = registry code not found in the e-invoice register.

get_companyA

Full register data for one company (REST, needs an API key). Choose blocks with include: general (names, addresses, legal form, share capital, financial year, contacts, EMTAK activities, VAT number), related_persons (board and council members, shareholders, representation rights), commercial_pledges, rulings (court registry rulings), registry_cards (entries on the registry card). Default: general. Company status codes: R = registered, L = in liquidation, N = bankrupt, K = deleted.

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 total). Company status codes: R = registered, L = in liquidation, N = bankrupt, K = deleted.

get_representation_rightsA

Who may represent companies, and how (REST, needs an API key): persons with their role and whether they can act alone (exclusiveRightOfRepresentation), plus special conditions and joint-representation groups. Search by the REPRESENTATIVE: a person's identification code, or a company's registry code with person_type J when the representative is itself a company, or by name. For who can represent a given company, use get_company with include ['related_persons'] instead.

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 year it lists the available reports (year, report code, name). With year and no report_code it returns every report for that year (one query each); pass report_code (from the list) for just one.

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. body holds the fields of keha as JSON: arrays repeat an element, objects nest. Field names and required fields are in the per-query docs at https://avaandmed.ariregister.rik.ee/en/open-data-api/introduction-api-services; send them in the order the docs list them. The service rejects a request that leaves out a field it requires, even one with a documented default. The response is the keha element as JSON with all values as text.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 12 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues