Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI-TENDER — open procurements of Belarus

REMOTE · AI-TENDER.BY · SCANNED SEP 26

Open public procurements of Belarus: search by words or customer UNP, source link for each.

Available components

73 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 278 tokens (~92/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the AI-TENDER — open procurements of Belarus MCP server?

AI-TENDER — open procurements of Belarus is a hosted endpoint at https://ai-tender.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-tender.by

# add to Claude Code
claude mcp add --transport http by-ai-tender-tenders 'https://ai-tender.by/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "by-ai-tender-tenders": {
      "url": "https://ai-tender.by/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "by-ai-tender-tenders": {
      "type": "http",
      "url": "https://ai-tender.by/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.by-ai-tender-tenders]
url = "https://ai-tender.by/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "by-ai-tender-tenders": {
      "type": "remote",
      "url": "https://ai-tender.by/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add by-ai-tender-tenders --url 'https://ai-tender.by/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  by-ai-tender-tenders:
    url: "https://ai-tender.by/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "by-ai-tender-tenders": {
      "Transport": "http",
      "Url": "https://ai-tender.by/mcp"
    }
  }
}
# add to Vellum
assistant mcp add by-ai-tender-tenders -t streamable-http -u 'https://ai-tender.by/mcp'
// mcp.json
{
  "mcpServers": {
    "by-ai-tender-tenders": {
      "type": "http",
      "url": "https://ai-tender.by/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 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 72

    First indexed and scored.

Diagnostics

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 26 Sept 2026 · Probed https://ai-tender.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-tender.by CN=YR2,O=Let's Encrypt,C=US 10 Sept 2026 9 Dec 2026 RSA 2048 SHA256-RSA 52708714e4e19008aec3ab6c77f7fd4a3e3
SANs: ai-tender.by, www.ai-tender.by
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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-tender.by. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
by. present 495 13 Verified
ai-tender.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'; img-src 'self' data:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; script-src 'self' https://mc.yandex.ru; connect-src 'self' https://mc.yandex.ru; frame-ancestors 'self'; object-src 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ai-tender.by/mcp Verified 200
http (plaintext) http://ai-tender.by/mcp HTTPS enforced 301 https://ai-tender.by/mcp
MCP tools · 3 exposed · ~224 tokens

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 →

Tool Tokens
get_tender ~74

One open procurement by its id ("<source>:<number>", e.g. "goszakupki:3653566"): customer, deadline, price, delivery place, procedure, link to the source platform. A closed or unknown id returns found=false. Карточка закупки.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

list_regions ~31

Regions of Belarus with the number of open procurements in each. Области и число открытых закупок.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_tenders ~119

Search OPEN public procurements of Belarus (submission deadline not passed) by words in the title or customer name, or by the customer UNP (9 digits); optional region. Each item: title, customer, deadline, price, procedure, source platform link and the AI-TENDER card. Ordered by deadline. Поиск открытых закупок Беларуси.

NameTypeReqDescription
limitinteger––
querystring–Words from the title or customer, or customer UNP
regionstring–Region name as returned by list_regions

No output schema declared.

No examples provided.

Common questions

What is the AI-TENDER — open procurements of Belarus MCP server?

AI-TENDER — open procurements of Belarus is an MCP server listed in the public MCP registry as by.ai-tender/tenders. Open public procurements of Belarus: search by words or customer UNP, source link for each. This page covers its hosted endpoint (https://ai-tender.by/mcp).

Is the AI-TENDER — open procurements of Belarus MCP server safe to use?

AI-TENDER — open procurements of Belarus scores 73 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-TENDER — open procurements of Belarus MCP server expose?

AI-TENDER — open procurements of Belarus exposes 3 tools: search_tenders, get_tender, list_regions. Their descriptions and schemas cost roughly 224 tokens of context every time the server is loaded.

Does the AI-TENDER — open procurements of Belarus MCP server require authentication?

No. We connected to AI-TENDER — open procurements of Belarus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AI-TENDER — open procurements of Belarus MCP server still maintained?

AI-TENDER — open procurements of Belarus is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.