Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Lab4U is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Lab4U (Russia): pick lab tests for a goal or a doctor's list and build a cart on lab4u.ru
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http lab4u-mcp https://mcp.lab4u.ru/mcp
# 2 — ask your agent for something these tools do
# lab4u_cities, lab4u_tests_search, lab4u_test_details and 2 more
Lab4U costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LAAll 1 server
lab4u1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http lab4u-mcp https://mcp.lab4u.ru/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Список городов, где можно сдать анализы Lab4U. Вызывай первым, чтобы получить location_id города пользователя. Если города нет в списке, скажи, что Lab4U там не работает.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | no | Часть названия города, например «Казань». Не указывай, чтобы получить весь список |
Поиск анализов и комплексов Lab4U по ключевым словам: название, сокращение, показатель или тема (например, «ОАК», «витамин D», «TSH», «щитовидная железа»). Принимает список запросов — передавай все нужные сразу, а не всю фразу пользователя. location_id обязателен: без него не видно доступность и сроки. Комплексы в ответе идут первыми. У каждой позиции есть метка «нашлось» и состав комплекса — испо
| Parameter | Type | Required | Notes |
|---|---|---|---|
| queries | array | yes | Ключевые слова, от 1 до 10: названия анализов, сокращения, показатели или темы. Например: ["ТТГ", "Т4 свободный", "щитовидная железа"] |
| location_id | integer | yes | ID города из lab4u_cities. Обязателен: без него не видно доступность и сроки |
Подробности об одном анализе в городе: доступен ли, срок готовности, работает ли в выходные, ограничения по полу, какие показатели входят, ссылка на страницу с правилами подготовки. Вызывай, когда пользователь спрашивает про конкретный анализ или нужно сравнить похожие.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_id | integer | yes | ID анализа или комплекса из lab4u_tests_search |
| location_id | integer | yes | ID города из lab4u_cities |
Проверяет список анализов, который назвал или выбрал пользователь, перед сборкой корзины. Находит самый подходящий готовый комплекс: включает хотя бы 2 анализа из списка и добавляет не больше 10. Показывает, что недоступно в городе и что нельзя заказать отдельно. Вызывай, когда у пользователя есть конкретный список анализов, в том числе от врача.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_ids | array | yes | ID анализов, которые назвал или выбрал пользователь, от 1 до 20 |
| location_id | integer | yes | ID города из lab4u_cities |
Собирает корзину на lab4u.ru из списка ID анализов (до 20) для города и возвращает ссылку. Вызывай, когда пользователь согласился со списком. Если у пользователя был конкретный список анализов, сначала проверь его через lab4u_basket_check. Сообщи о недоступных в городе и несовместимых анализах из ответа.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| test_ids | array | yes | ID анализов и комплексов из lab4u_tests_search, от 1 до 20 |
| location_id | integer | yes | ID города из lab4u_cities |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Lab4U or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest04252901059973801fd86a9edd0811553408fe08f28aa0a2699cb53ee15f34ba
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| lab4u_cities | no tags | |
| lab4u_tests_search | no tags | |
| lab4u_test_details | no tags | |
| lab4u_basket_check | no tags | |
| lab4u_cart_link_create | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest0425290105997380
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Lab4U can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.