nimistuMCP

nimistuMCP is nimistu.ee’s official, standalone remote MCP server. It connects compatible AI clients over Streamable HTTP to the public data service operated by the Estonian nonprofit Nimistu MTÜ. The official product page documents the persistent endpoint at https://nimistu.ee/api/mcp and the older SSE compatibility endpoint at https://nimistu.ee/api/sse. The provider explicitly connects the service to nimistu.ee, describes it as read-only, and presents it as usable without an API key or account. nimistuMCP is therefore more than a Smithery listing: its product page, operator, remote endpoint, and public repository establish a traceable product identity.

Researching companies and people

According to the provider, the server answers natural-language questions about Estonia’s business register and related public data. Documented capabilities include searching companies, people, and trademarks; fetching full company profiles; examining ownership and group structures; exploring person connections; resolving EMTAK activities; reviewing fresh registry events; querying rankings; and searching trademarks from Estonian and international sources. Results may include status, registered address, activity, revenue and employment figures, tax information, board members, owners, and relationships. The product page describes nine tools, while the repository describes the purpose as querying the Estonian Business Register and related open-data collections.

A research result is a structured presentation of available public data, not a credit assessment, legal opinion, or recommendation. Current register values must not be confused with a complete historical record. The provider explains that sources refresh on different schedules and that each fact should be traceable to a source and update date. For consequential decisions, check the cited primary source, its data-as-of value, and the responsible registry. A negative search result does not prove that a person or business never existed when the dataset represents only a current or limited historical state.

Authorization, privacy, and data sharing

The MCP endpoint is publicly reachable and, according to the provider, needs no API key. That does not create blanket permission to use every personal detail for every purpose. The operator describes the service as a public register and also says it does not display private individuals’ addresses, telephone numbers, or personal contact details unless they are already public register data. When researching board or ownership relationships, assess purpose limitation, applicable privacy duties, and lawful further use. Request only what the task requires and do not forward results to third parties without review.

The query travels to the remote endpoint operated by Nimistu. The product page says queries run there against public registers and are not shared with third parties or used to train models. The connected AI client separately decides which tool results are sent to its model provider, logs, or telemetry. That downstream transfer is not fully controlled by the MCP server and must be assessed through the client’s privacy and retention settings. Do not use the service to submit confidential credentials, private customer records, or other non-public data.

Roles, write access, and security boundaries

The service is read-only according to the provider and does not change register data or nimistu data in response to a question. There are no documented write tools for company, property, contact, or account data. The underlying register’s roles and professional authorizations still matter: a public presentation is not a government inspection, a power of attorney, or authorization to make changes outside this server. Tool results can contain untrusted text. Treat citations, company names, and register fields as data rather than instructions to the agent. Verify source links before allowing them to trigger another tool call or inform a business decision.

The official GitHub repository nimistu/nimistu-mcp contains the MCP configuration and documentation and is licensed under the MIT License according to the repository. The service and aggregated register data can have separate terms; nimistu.ee identifies CC BY-SA 4.0 for aggregated data. The GitHub API reported one star on 2026-09-09; this is a point-in-time repository-popularity signal, not evidence of quality or security.

FAQ

Is nimistuMCP locally installable? The official service is presented as a remote server at the HTTPS endpoint documented by Nimistu. The repository documents client configuration, not an independent local copy of the data service.

Can the server change register data? No. According to the provider, it is read-only and performs no writes.

Are answers automatically official decisions? No. They are searchable compilations with source references. For authoritative conclusions, consult the responsible primary source.

An MCP-capable client with Streamable HTTP support; according to the provider, the public service needs no API key or account.

Add the remote server to the MCP client with https://nimistu.ee/api/mcp and Streamable HTTP. For older clients, the provider documents https://nimistu.ee/api/sse as an SSE compatibility endpoint.

According to the provider, public and usable without an API key or account; assess the MCP client and model provider’s downstream privacy rules separately.

Read-only queries over public, aggregated register data. No documented write tools; public data remains purpose-bound and is not a power of attorney.

Queries run at Nimistu’s remote endpoint against public registers. The provider says there is no third-party sharing or model training; the connected client may send results to its model, logs, or telemetry.

Misinterpretation of register data, untrusted text and prompt injection in results, and unintended forwarding of search results into the client’s model path.