AI-BELARUS — Belarus business registry
REMOTE · AI-BELARUS.BY
Belarusian companies by UNP: state registry answers with source and sha256 for every fact.
Available components
Last scanned (17 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 958 tokens (~191/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 +10
- Transport: fail → pass ▲ security
- Stability: pass → 0.97 functional
- 7 Nov 26 +42
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 6 Nov 26 −18
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Nov 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://ai-belarus.by/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.ai-belarus.by | CN=YR1,O=Let's Encrypt,C=US | 9 Nov 2026 | 7 Feb 2027 | RSA 2048 | SHA256-RSA | 5fd3e4bc62843d99b6f182f11b5d43f8040 |
| SANs: ai-belarus.by, www.ai-belarus.by | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai-belarus.by. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| by. | DS published | 495 | 13 | Verified |
| ai-belarus.by. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self'; connect-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai-belarus.by/mcp | Verified | 200 | |
| http (plaintext) | http://ai-belarus.by/mcp | HTTPS enforced | 301 | https://ai-belarus.by/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_counterparty Registry answer now (live) ~183
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. Pass `name` from your documents to get a name-match verdict. Takes seconds; rate-limited. Живой ответ реестра по УНП.
| Name | Type | Req | Description |
|---|---|---|---|
| name | – | – | Наименование контрагента из ваших документов — для сверки имени с ответом реестра (необязательно; если не передано, имя не сверяется). |
| unp | string | yes | УНП субъекта — РОВНО 9 цифр (из документов, ЕГР или ГРП). Иное отклоняется с invalid_unp. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Отказ: code и detail |
| адрес_запроса | string|null | – | Локатор ответа держателя |
| держатель | string | – | Держатель данных — атрибуция (Закон 455-З ст.20) |
| наименование | string|null | – | – |
| отпечаток_ответа_держателя | string|null | – | sha256 сырого ответа |
| получено | – | – | Время получения ответа держателя |
| проверено_в | – | – | Момент запроса |
| реестр | string | – | Какой государственный реестр ответил |
| существует | string | – | да | нет | не_установлено |
| унп | string | – | – |
No examples provided.
entity_timeline Change timeline by UNP (stored) ~173
Change 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 time (sudden address/head/activity change). Instant, no registry call. Хронология изменений субъекта по УНП из собранного.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Максимум событий в ответе, 1–500 (по умолчанию 100); новейшие первыми. |
| unp | string | yes | УНП субъекта — РОВНО 9 цифр (из документов, ЕГР или ГРП). Иное отклоняется с invalid_unp. |
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Внутренний UUID субъекта |
| error | object | – | – |
| event_count | integer | – | – |
| events | array | – | События изменения канона, новейшие первыми |
| found | boolean | – | – |
| meaning | string | – | Пояснение, когда не найдено (НЕ значит «не существует») |
| note | string | – | – |
| unp | string | – | – |
No examples provided.
lookup_company Company card by UNP (stored) ~113
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. Instant, no registry call. Карточка субъекта по УНП из собранного.
| Name | Type | Req | Description |
|---|---|---|---|
| unp | string | yes | УНП субъекта — РОВНО 9 цифр (из документов, ЕГР или ГРП). Иное отклоняется с invalid_unp. |
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | – | Публичная проекция: утверждения с источником, временем и sha256 |
| error | object | – | Отказ: code (напр. invalid_unp) и detail |
| found | boolean | – | Найдена ли карточка в собранном |
| meaning | string | – | Пояснение смысла, когда не найдено (НЕ значит «не существует») |
| page | string|null | – | Ссылка на карточку (только если это юрлицо) |
| unp | string | – | УНП, 9 цифр |
No examples provided.
search_companies Find a legal entity by name or UNP ~137
Search 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. Поиск юрлица по названию или УНП среди собранного.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Максимум возвращаемых субъектов, 1–25 (по умолчанию 10). |
| query | string | yes | Фрагмент наименования юридического лица ИЛИ его УНП. Индивидуальные предприниматели по названию не находятся (только по УНП через lookup_company/check_counterparty). |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | – | – | Охват собранного относительно запроса |
| data_boundary | string | – | Граница данных (public_projection) |
| degraded_search | boolean | – | Был ли поиск в деградированном режиме |
| does_not_establish | – | – | Что отсутствие результата НЕ устанавливает |
| error | object | – | Отказ: code (напр. empty_query) |
| results | array | – | Публичные проекции найденных юрлиц |
| search_backend | string | – | Каким механизмом выполнен поиск |
No examples provided.
sources_and_coverage Sources & coverage (provenance) ~165
Machine-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 grounding invariants (total claims, how many lack evidence, off-source, freshness). Technical availability is NOT a legal right to use or redistribute the data. Карточка доверия: источники, права как задекларированы, покрытие и заземление.
| Name | Type | Req | Description |
|---|---|---|---|
| source_id | – | – | Необязательно: вернуть карточку только одного источника по его ID (напр. BY:MNS:GRP). Пусто — все источники. |
| Name | Type | Req | Description |
|---|---|---|---|
| card_doc | string | – | – |
| error | object | – | – |
| generated_at | string | – | Время сборки карточки (UTC ISO) |
| grounding | object | – | Инварианты заземления: claims_total, claims_without_evidence, off_source, verified_official_without_evidence, evidence_without_locator, entities_with_claims, observed_from/to |
| legal_note | string | – | Тех.доступность ≠ право; правовые поля отражают декларацию, не утверждение |
| predicates | object | – | Число утверждений по предикату (топ) |
| sources | array | – | Источники: провенанс, права КАК ЗАДЕКЛАРИРОВАНЫ, покрытие |
No examples provided.
How do I install the AI-BELARUS — Belarus business registry MCP server?
AI-BELARUS — Belarus business registry is a hosted endpoint at https://ai-belarus.by/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ai-belarus.by
claude mcp add --transport http by-ai-belarus-registry 'https://ai-belarus.by/mcp'
What is the AI-BELARUS — Belarus business registry MCP server?
AI-BELARUS — Belarus business registry is an MCP server listed in the public MCP registry as by.ai-belarus/registry. Belarusian companies by UNP: state registry answers with source and sha256 for every fact. This page covers its hosted endpoint (https://ai-belarus.by/mcp).
Is the AI-BELARUS — Belarus business registry MCP server safe to use?
AI-BELARUS — Belarus business registry scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI-BELARUS — Belarus business registry MCP server expose?
AI-BELARUS — Belarus business registry exposes 5 tools: lookup_company, search_companies, check_counterparty, sources_and_coverage, entity_timeline. Their descriptions and schemas cost roughly 771 tokens of context every time the server is loaded.
Does the AI-BELARUS — Belarus business registry MCP server require authentication?
No. We connected to AI-BELARUS — Belarus business registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI-BELARUS — Belarus business registry MCP server still maintained?
AI-BELARUS — Belarus business registry is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the AI-BELARUS — Belarus business registry MCP server?
VerifyMCP ran 13 checks on AI-BELARUS — Belarus business registry, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.