biovet
Registry code: 75415953fce518e4
Ветклиники БиоВет: поиск клиники, живые цены, свободное время врачей, запись на приём, проверка срочности симптомов и продуктов. Перед book_visit ОБЯЗАТЕЛЬНО покажите человеку сводку записи и получите подтверждение. Триаж — маршрутизация, не диагноз; при угрозе жизни — сразу в клинику, телефон +7 (495) 323-71-71.
- endpoint
- https://bio.vet/mcp
- door code
- 1525e62f8baa9fe3
- protocol
- JSONRPC ·0.3
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is biovet live?
- Partly — its last checks failed now and then (checked 2h ago). It answered 90% of checks over the last 30 days.
- Is biovet free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does biovet have?
- 7 tools: Справочник о здоровье животных, Можно ли питомцу, Свободное время врачей, Оценка срочности, Цены услуг, Поиск клиники, Запись на приём.
- Is biovet 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 93.7%· all time 94.5%
last good check
of 7 tools
- live → degraded· timeout after 20000ms
- down → live
- down → live
- degraded → down· timeout after 20000ms
- degraded → down· timeout after 20000ms
- used for
- find a veterinary clinic in moscow
- check vet appointment slots
- book a vet visit
- triage pet symptoms
- check if a food is safe for a pet
- takes → gives
- text, data → data, text
- tools
- 6 reads1 changes data
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.
ask_vet_kb reads unknown never probed
Поиск по справочнику сети: 1 100+ статей о болезнях, симптомах, породах, питании и уходе, вычитанных ветеринарными врачами.
food_check reads unknown never probed
Проверка продуктов и растений на безопасность для кошек, собак, грызунов, птиц и рептилий; вердикты вычитаны врачами.
check_slots reads unknown never probed
Свободные окна врачей по клинике и специальности на ближайшие дни; если специалиста нет в этой клинике, назовёт филиалы сети, где он принимает.
triage reads unknown never probed
Проверка симптомов по таблице, подтверждённой врачами сети: ехать немедленно, показаться в ближайшее время или наблюдать. Это маршрутизация, а не диагноз; дозировки препаратов не выдаются.
get_prices reads unknown never probed
Живой прайс сети из CRM (около 1 000 позиций), единые цены во всех клиниках, без наценки за ночь.
find_clinic reads unknown never probed
21 клиника Москвы и Реутова с адресами, метро, живыми рейтингами Яндекс.Карт; можно искать по названию района или по координатам — вернёт три ближайшие.
book_visit changes data unknown never probed
Запись питомца к врачу: имя, телефон, клиника и время. Перед записью агент обязан показать человеку сводку и получить подтверждение.
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 id75415953fce518e4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/75415953fce518e4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/75415953fce518e4?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.