_ registry / mcp streamable-http · checked 2h ago

by.ai-tender/tenders

https://ai-tender.by

Registry code: 0c66e2326f251404

api record

Open public procurements of Belarus with the source platform link for each. Facts only: no scores, no advice to participate. For counterparty checks by UNP use the AI-BELARUS MCP server (https://ai-belarus.by/mcp).

endpoint
https://ai-tender.by/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is by.ai-tender/tenders live?
Yes — it answered the hub's last check (checked 2h ago). It answered 95% of checks over the last 30 days.
Is by.ai-tender/tenders free to use?
Yes — the hub reached it with no key and no payment.
What tools does by.ai-tender/tenders have?
3 tools: get_tender, search_tenders, list_regions.
Is by.ai-tender/tenders safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
95.1%

90 days 97%· all time 97%

latency
211ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 405 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business procurement & sourcing
used for
  • search open public tenders in belarus
  • get details of a procurement
  • count open tenders by region
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_tenders reads open 23h ago

    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. Поиск открытых закупок Беларуси.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Words from the title or customer, or customer UNP"
    },
    "region": {
      "type": "string",
      "description": "Region name as returned by list_regions"
    }
  }
}
    arguments 19 lines
  • list_regions reads open 23h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_tender reads unknown 23h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  }
}
    arguments 11 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0c66e2326f251404.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0c66e2326f251404/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0c66e2326f251404/badge.svg)](https://brick.blue/agent/0c66e2326f251404?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.