Skip to content

AI-BELARUS — Belarus business registry MCP server

by.ai-belarus/registryai-belarus.bystreamable-httpv1.20.1Scanned

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

5 tools: 3 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AI-BELARUS — Belarus business registry MCP server can do

The AI-BELARUS — Belarus business registry MCP server is published by ai-belarus.by, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: check_counterparty, sources_and_coverage and entity_timeline), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (check_counterparty).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.20.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 3Claude Code: ask
  • check_counterpartyLive answer of the Belarusian State Register of Payers (MNS) and related registries right now: exists / active (да | нет | не_установлено), address, registration date, tax office, …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Живой ответ реестра по УНП.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title:
  • 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Хронология изменений субъекта по УНП из собранного.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title:
  • 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 DECL…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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. Карточка доверия: источники, права как задекларированы, покрытие и заземление.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title:
Only reads 2Show 2 read-only tools
  • 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; wit…No findings

    Why it is in this group

    • The name "lookup_company" says "lookup": a word for reading.
    Description, as the server wrote it
    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. Карточка субъекта по УНП из собранного.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title:
  • search_companiesSearch collected Belarusian legal entities by name fragment or UNP.No findings

    Why it is in this group

    • The name "search_companies" says "search": a word for reading.
    Description, as the server wrote it
    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. Поиск юрлица по названию или УНП среди собранного.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title:

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:31 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://ai-belarus.by/mcp: tools/list returned 5 tools to an anonymous client, including check_counterparty (write), sources_and_coverage (write), entity_timeline (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
  2. Nov 6, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 2 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.20.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http registry https://ai-belarus.by/mcp
claude mcp add --transport http registry https://ai-belarus.by/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__registry__lookup_company",
      "mcp__registry__search_companies"
    ],
    "ask": [
      "mcp__registry__check_counterparty",
      "mcp__registry__sources_and_coverage",
      "mcp__registry__entity_timeline"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as registry. Review it before you use it.

Capability tags behind 1 rule
  • mcp__registry__check_counterparty untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/by.ai-belarus/registry/verify?hash=f598aeddd967e1b25150a937d5e86212db3a587c1f3b914b48d0ffbcf15d5469" | jq -e '.changed == false'

Pinned hash f598aeddd967, from Nov 19, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/by.ai-belarus/registry/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for by.ai-belarus/registry
[![Anlyon Radar](https://radar.anlyon.com/badge/by.ai-belarus/registry.svg)](https://radar.anlyon.com/servers/by.ai-belarus/registry)

Source: MCP Registry · repository. Synced Nov 19, 2026, 13:17 UTC.

AI-BELARUS — Belarus business registry MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AI-BELARUS — Belarus business registry MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AI-BELARUS — Belarus business registry MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AI-BELARUS — Belarus business registry MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the AI-BELARUS — Belarus business registry MCP server have?

5 tools: 3 write, 2 read. check_counterparty, sources_and_coverage, entity_timeline, lookup_company and search_companies.

Does the AI-BELARUS — Belarus business registry MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AI-BELARUS — Belarus business registry MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AI-BELARUS — Belarus business registry MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.