Skip to content
AI-TENDER logo

AI-TENDER MCP server

Which MCP servers are AI-TENDER's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-30

← Back to AI-TENDER

Whose server it is
  • Registry nameby.ai-tender/tendersverified in the MCP registry

The registry name sits under ai-tender.by. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-30
  • Stateanswerschecked 2026-10-30
  • Tools3
  • Server calls itselfby.ai-tender/tenders
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 603 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: Receive tender notifications by email; Extract tender documents from PDF, Word and Excel.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 2 of 3 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-30
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it0 of 2 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer888 ms
  • Space in an agent's context≈ 300 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 89 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 3

What an agent can do with it

  • cannot · Receive tender notifications by email
  • cannot · Extract tender documents from PDF, Word and Excel
  • not sure · Monitor goszakupki and icetrade tender listings

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-30
  • search_tenders

    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…

  • get_tender

    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. Карточка закупки.

  • list_regions

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "tenders": {
      "type": "http",
      "url": "https://ai-tender.by/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://ai-tender.by/mcp as a custom connector in the settings.

OpenAPI spec

4 paths, read 2026-10-30. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.