AI-BELARUS — Belarus business registry
REMOTE · AI-BELARUS.BY · SCANNED SEP 27
Belarusian companies by UNP: state registry answers with source and sha256 for every fact.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 465 tokens (~155/item across 3 items; 3 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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'
{
"mcpServers": {
"by-ai-belarus-registry": {
"url": "https://ai-belarus.by/mcp"
}
}
} {
"servers": {
"by-ai-belarus-registry": {
"type": "http",
"url": "https://ai-belarus.by/mcp"
}
}
} [mcp_servers.by-ai-belarus-registry] url = "https://ai-belarus.by/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"by-ai-belarus-registry": {
"type": "remote",
"url": "https://ai-belarus.by/mcp",
"enabled": true
}
}
} openclaw mcp add by-ai-belarus-registry --url 'https://ai-belarus.by/mcp' --transport streamable-http
mcp_servers:
by-ai-belarus-registry:
url: "https://ai-belarus.by/mcp" {
"McpServers": {
"by-ai-belarus-registry": {
"Transport": "http",
"Url": "https://ai-belarus.by/mcp"
}
}
} assistant mcp add by-ai-belarus-registry -t streamable-http -u 'https://ai-belarus.by/mcp'
{
"mcpServers": {
"by-ai-belarus-registry": {
"type": "http",
"url": "https://ai-belarus.by/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 70
First indexed and scored.
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 27 Sept 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 | 10 Sept 2026 | 9 Dec 2026 | RSA 2048 | SHA256-RSA | 5e9cec17db1a0368eff6f4709421f65390c |
| 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. | present | 495 | 13 | Verified |
| ai-belarus.by. | absent | 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) ~118
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 | – |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_company Company card by UNP (stored) ~80
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 | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_companies Find a legal entity by name or UNP ~80
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 | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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 72 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 3 tools: lookup_company, search_companies, check_counterparty. Their descriptions and schemas cost roughly 278 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 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.