MyTender
Registry code: 3d663c560de39df7
MyTender — открытые тендеры и госзакупки Казахстана (goszakup.gov.kz, Самрук-Қазына, Mitwork). search_tenders — найти открытые лоты по словам, региону, сумме; get_tender — карточка лота с характеристиками, документами, числом заявок и ИИ-разбором, если он есть; get_customer — как заказчик платит, кто у него выигрывает, обычная скидка победителей и рейтинг 0–100; price_history — цены прошлых закупок товара по коду КТРУ. Суммы — в тенге без НДС. Ссылки ведут на mytender.kz.
- endpoint
- https://mytender.kz/api/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 MyTender live?
- Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
- Is MyTender free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does MyTender have?
- 4 tools: get_tender, price_history, get_customer, search_tenders.
- Is MyTender 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
through this hub
successful
what callers paid
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 open 15h ago
Открытые лоты (идёт приём заявок) по словам из названия, региону, сумме, типу и площадке. Возвращает до 20 лотов: id, название, заказчик, сумма, регион, способ, срок, ссылка. Закупки из одного источника и среди организаций инвалидов скрыты.
{ "type": "object", "properties": { "sort": { "enum": [ "newest", "ending_soon", "largest" ], "type": "string", "description": "Порядок: новые, скоро конец приёма, крупные" }, "limit": { "type": "number", "description": "Сколько лотов вернуть, 1–20 (по умолчанию 10)" }, "query": { "type": "string", "description": "Слова из названия лота, номер лота или объявления, например «ноутбук» или «услуги охраны»" }, "region": { "type": "string", "description": "Регион: Астана, Алматы, Шымкент или область, например «Карагандинская обл.»" }, "category": { "enum": [ "goods", "works", "services" ], "type": "string", "description": "Товары, работы или услуги" }, "platform": { "enum": [ "goszakup", "samruk", "mitwork", "all" ], "type": "string", "description": "Площадка; по умолчанию goszakup" }, "amount_to": { "type": "number", "description": "Сумма лота до, ₸" }, "amount_from": { "type": "number", "description": "Сумма лота от, ₸" }, "price_requests_only": { "type": "boolean", "description": "Только запросы ценовых предложений (ЗЦП)" } }, "additionalProperties": false }arguments 58 linesget_tender unknown 15h ago
Всё о лоте по его id (из search_tenders или ссылки mytender.kz/tenders/<id>): характеристики, предоплата, срок поставки, документы, число поданных заявок, рейтинг заказчика и ИИ-разбор ТЗ (если его уже запускали на MyTender).
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "number", "description": "id лота MyTender (число из ссылки mytender.kz/tenders/<id>)" } }, "additionalProperties": false }arguments 13 linesprice_history unknown never probed
Закрытые закупки того же товара по коду КТРУ (ЕНС ТРУ): сумма, цена договора, скидка, победитель; медиана скидки. Можно сузить до заказчика.
{ "type": "object", "required": [ "ktru" ], "properties": { "ktru": { "type": "string", "description": "Код КТРУ, например 262013.000.000018" }, "customer_bin": { "type": "string", "description": "БИН заказчика — показать ещё, кто у него выигрывал" } }, "additionalProperties": false }arguments 17 linesget_customer unknown 15h ago
Заказчик по БИН за 12 месяцев: сколько лотов и сколько не состоялось, заявок на лот, обычная скидка победителей, как платит по актам, главные поставщики, «свой» поставщик, рейтинг 0–100.
{ "type": "object", "required": [ "bin" ], "properties": { "bin": { "type": "string", "description": "БИН заказчика, 12 цифр" } }, "additionalProperties": false }arguments 13 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3d663c560de39df7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3d663c560de39df7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3d663c560de39df7?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.