Estonia Company Check

io.github.JusticeUAPublished by GitHub account JusticeUAv0.1.0Updated Nov 7, 2026

Estonia company checks: status, insolvency, LEI and sanctions from official registers.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant run Estonian company checks — status, insolvency, LEI and sanctions — from official registers.

What you can do
  • Look up Estonian companies and retrieve their registration status
  • Check insolvency and sanctions information drawn from official registers
  • Retrieve LEI (legal entity identifier) details for a company
  • No individual tools are documented; capabilities are described only at the level of company checks
When to use it
Useful when you need quick due diligence on an Estonian business partner, supplier or customer — verifying that a company is active, solvent and not sanctioned — without visiting each register by hand.
Requirements
A remote streamable HTTP endpoint; no local install. Requires an Apify API token sent as a bearer token in the Authorization header. An Apify account with billing enabled is needed because checks are charged per company.
Before you install
The Authorization header carries an Apify API token, so treat it as a secret. Each company check is billed to your Apify account, so repeated lookups cost money. Results come from third-party register data and should be verified before relying on them for decisions.

Installation

In SourceWeft

  1. Open Estonia Company Check in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.JusticeUA%2Festonia-company-check/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "estonia-company-check": {
      "type": "http",
      "url": "https://kyb-data--estonia-company-check.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestNov 7, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Check integrations