AI-BELARUS — Belarus business registry

by.ai-belarus/registry · v1.19.0 · finance-and-payments

AI-BELARUS — Belarus business registry is healthy: it completed an MCP handshake in 3420 ms and exposes 5 tools.

Belarusian companies by UNP: state registry answers with source and sha256 for every fact.

Endpoint: https://ai-belarus.by/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count5
Latency3420 ms
Last checked (UTC)2026-10-15T18:05:14.930Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T18:05:14.930ZHealthy3420
2026-10-14T17:15:44.383ZHealthy5610

Tools (5)

lookup_companyCollected 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. Instant, no registry call. Карточка субъекта по УНП из собранного.
search_companiesSearch collected Belarusian legal entities by name fragment or UNP. Only legal entities are found by name (sole proprietors never are). Absence here is not absence in the state registry. Поиск юрлица по названию или УНП среди собранного.
check_counterpartyLive 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. Pass `name` from your do
sources_and_coverageMachine-readable trust card of the registry itself: every source with provenance (organ, tier, URL) and its DECLARED access/rights (machine_api_authorization, terms_status) AS DECLARED in config — not asserted by this tool; plus coverage (claims and evidence per source, which sources give canon) and
entity_timelineChange timeline of a Belarusian entity by UNP from collected data: an ordered log of canon changes per predicate (created / reaffirmed / superseded / conflict_detected), each event carrying old and new value, source registry and time (effective_at, observed_at). Lets an agent read anomalies over tim