Lab4U
REMOTE · MCP.LAB4U.RU
Lab4U (Russia): pick lab tests for a goal or a doctor's list and build a cart on lab4u.ru
Available components
Last scanned (22 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Health and Science
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1382 tokens (~276/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 72
First indexed and scored.
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 4 Nov 2026 · Probed https://mcp.lab4u.ru/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.lab4u.ru | CN=YE2,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5accfe2b2788e502a80af4e35df6aed0188 |
| SANs: mcp.lab4u.ru | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.lab4u.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | present | 26734 | 8 | Verified |
| lab4u.ru. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.lab4u.ru/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.lab4u.ru/mcp | HTTPS enforced | 301 | https://mcp.lab4u.ru/mcp |
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 →
lab4u_basket_check Проверка списка анализов ~135
Проверяет список анализов, который назвал или выбрал пользователь, перед сборкой корзины. Находит самый подходящий готовый комплекс: включает хотя бы 2 анализа из списка и добавляет не больше 10. Показывает, что недоступно в городе и что нельзя заказать отдельно. Вызывай, когда у пользователя есть конкретный список анализов, в том числе от врача.
| Name | Type | Req | Description |
|---|---|---|---|
| location_id | integer | yes | ID города из lab4u_cities |
| test_ids | array | yes | ID анализов, которые назвал или выбрал пользователь, от 1 до 20 |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
lab4u_cart_link_create Корзина на lab4u.ru ~135
Собирает корзину на lab4u.ru из списка ID анализов (до 20) для города и возвращает ссылку. Вызывай, когда пользователь согласился со списком. Если у пользователя был конкретный список анализов, сначала проверь его через lab4u_basket_check. Сообщи о недоступных в городе и несовместимых анализах из ответа.
| Name | Type | Req | Description |
|---|---|---|---|
| location_id | integer | yes | ID города из lab4u_cities |
| test_ids | array | yes | ID анализов и комплексов из lab4u_tests_search, от 1 до 20 |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
lab4u_cities Города Lab4U ~82
Список городов, где можно сдать анализы Lab4U. Вызывай первым, чтобы получить location_id города пользователя. Если города нет в списке, скажи, что Lab4U там не работает.
| Name | Type | Req | Description |
|---|---|---|---|
| name | – | – | Часть названия города, например «Казань». Не указывай, чтобы получить весь список |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
lab4u_test_details Подробности об анализе ~104
Подробности об одном анализе в городе: доступен ли, срок готовности, работает ли в выходные, ограничения по полу, какие показатели входят, ссылка на страницу с правилами подготовки. Вызывай, когда пользователь спрашивает про конкретный анализ или нужно сравнить похожие.
| Name | Type | Req | Description |
|---|---|---|---|
| location_id | integer | yes | ID города из lab4u_cities |
| test_id | integer | yes | ID анализа или комплекса из lab4u_tests_search |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
lab4u_tests_search Поиск анализов ~219
Поиск анализов и комплексов Lab4U по ключевым словам: название, сокращение, показатель или тема (например, «ОАК», «витамин D», «TSH», «щитовидная железа»). Принимает список запросов — передавай все нужные сразу, а не всю фразу пользователя. location_id обязателен: без него не видно доступность и сроки. Комплексы в ответе идут первыми. У каждой позиции есть метка «нашлось» и состав комплекса — используй их, чтобы выбрать подходящее и не предлагать лишнее.
| Name | Type | Req | Description |
|---|---|---|---|
| location_id | integer | yes | ID города из lab4u_cities. Обязателен: без него не видно доступность и сроки |
| queries | array | yes | Ключевые слова, от 1 до 10: названия анализов, сокращения, показатели или темы. Например: ["ТТГ", "Т4 свободный", "щитовидная железа"] |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Lab4U MCP server?
Lab4U is a hosted endpoint at https://mcp.lab4u.ru/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 · mcp.lab4u.ru
claude mcp add --transport http ru-lab4u-mcp-lab4u 'https://mcp.lab4u.ru/mcp'
What is the Lab4U MCP server?
Lab4U is an MCP server listed in the public MCP registry as ru.lab4u.mcp/lab4u. Lab4U (Russia): pick lab tests for a goal or a doctor's list and build a cart on lab4u.ru. This page covers its hosted endpoint (https://mcp.lab4u.ru/mcp).
Is the Lab4U MCP server safe to use?
Lab4U scores 78 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 Lab4U MCP server expose?
Lab4U exposes 5 tools: lab4u_cities, lab4u_tests_search, lab4u_test_details, lab4u_basket_check, lab4u_cart_link_create. Their descriptions and schemas cost roughly 675 tokens of context every time the server is loaded.
Does the Lab4U MCP server require authentication?
No. We connected to Lab4U without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lab4U MCP server still maintained?
Lab4U is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.