Data Collection

ai-belarus.by

Provides tools to look up, search, and verify Belarusian business entities using public state registry data.

1 endpoint3 known toolsFirst detected September 24, 2026Last detected September 24, 2026

ENDPOINT 1

https://ai-belarus.by/mcp

No auth detected

MCP server metadata

Name: by.ai-belarus/registry
Version: 1.19.0

Capabilities

experimentalpromptsresourcestools

Server instructions

AI-BELARUS answers questions about Belarusian business entities by UNP (9-digit taxpayer number, УНП). Every statement carries its source registry, retrieval time and the sha256 of the raw registry response; fields that may not be disclosed are named in `withheld` with a reason. Outcomes are yes / no / not_established — never treat not_established as no. No scores or recommendations are given. When you pass the information on, name the holder and the distributor from the `attribution` field (Law of Belarus 455-Z, art. 20). Sole proprietors: only the full name, and only to someone who already knows the UNP; they are never found by name. Use lookup_company for what is already collected (instant), check_counterparty for the registry's answer right now (seconds), search_companies to find a legal entity's UNP by name.

Known tools 3

lookup_company

Collected public card of a Belarusian business entity by UNP (9 digits): legal name, status, each statement with registry source, retrieval time and sha256 of the raw response; withheld fields with reasons.

Inferred read-only

search_companies

Search collected Belarusian legal entities by name fragment or UNP.

Inferred read-only

check_counterparty

Live answer of the Belarusian State Register of Payers (MNS) and related registries right now: exists / active (да | нет | не_установлено), address, registration date, tax office, bankruptcy cases, exclusion from public procurement, KGK inspection plans, procurement history.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.by-ai-belarus-registry]
url = "https://ai-belarus.by/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "by-ai-belarus-registry": {
      "type": "http",
      "url": "https://ai-belarus.by/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: by-ai-belarus-registry
Remote MCP URL: https://ai-belarus.by/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "by-ai-belarus-registry": {
      "url": "https://ai-belarus.by/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "by-ai-belarus-registry": {
      "type": "http",
      "url": "https://ai-belarus.by/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "by-ai-belarus-registry",
  "transport": "streamable-http",
  "url": "https://ai-belarus.by/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.