Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Wenjia Home-Fix Diagnosis 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.
98/100
trust score
10
tools declared
local
runs on your machine
—
downloads a day
What it does
Home repair diagnosis for AI agents: ranked causes, repair price ranges, stop-before-DIY flags.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user wenjia-home-fix-diagnosis-mcp '--' uvx wenjia-home-fix-mcp
# 2 — ask your agent for something these tools do
# find_symptom, fix_plan, get_category and 7 more
Wenjia Home-Fix Diagnosis costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GCAll 1 server
gmcho2009-cloud1 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. This one runs on your machine: your client starts Wenjia Home-Fix Diagnosis as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user wenjia-home-fix-diagnosis-mcp '--' uvx wenjia-home-fix-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: 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 your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
【首选入口】把用户的一句人话直接丢进来（「空调不凉」「热水器打不着火」「马桶堵了」），返回最可能的症状 id 与候选。不需要先知道 category_id，也不用猜 id。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | 用户原话或症状描述，中英文均可 |
| limit | integer | no | 候选条数，默认 3，最大 10 |
【解决方案】取某症状的分步方案：按动手难度从低到高排的原因、每步具体动作、需要的配件、安全提示、什么时候必须停手找持牌技师。回答「我该怎么修、先做哪一步」用它。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | no | 品类 id，如 air_conditioner；也可省略 |
| symptom_id | string | no | 症状 id，如 not_cooling；也可省略 |
| query | string | no | 只有口语时用：如「空调不凉」，服务端会自己定位 |
| max_causes | integer | no | 返回几个原因，默认 3 |
| max_steps | integer | no | 每个原因返回几步，默认 4 |
取某品类的全部症状清单（每个症状一句话摘要）。用于从品类入口展开，或确认「这个品类管哪些故障」。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | no | 品类 id，如 washing_machine；也可传品类中文名 |
| category | string | no | 品类中文名，如「洗衣机」，category_id 的替代写法 |
取某症状的原因先验概率分布（合计 100），最省 token 的量化入口。只回答「多大概率是哪个原因」，不含修复步骤。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | no | 品类 id，如 air_conditioner |
| symptom_id | string | no | 症状 id，如 not_cooling |
| query | string | no | 可选：口语描述，省略 id 时用它定位 |
取某症状的上门维修价格区间（人民币元）。只回答问题「修这个大概多少钱」。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | no | — |
| symptom_id | string | no | — |
| query | string | no | 可选：口语描述，省略 id 时用它定位 |
判断该症状是否属于必须停手的涉险场景（燃气/用电/登高），返回风险等级与停手理由。用于安全前置校验。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | no | — |
| symptom_id | string | no | — |
| query | string | no | 可选：口语描述，省略 id 时用它定位 |
列出问家家庭维修诊断知识库的全部品类（含品类名、症状数、更新日期）。共 40 品类 / 224 症状，含空调、洗衣机、燃气热水器、电路、上下水、门窗墙面等。
No parameter schema on file.
按关键词搜索症状（跨品类，带相关度打分），返回匹配的症状 id 与标题。不确定该用哪个 id 时用它，或用 find_symptom 直接给一句口语。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | 关键词或一句话，如「不制冷」「漏水」「异响」 |
| category_id | string | no | 可选，限定品类 |
| limit | integer | no | 返回条数上限，默认 20，最大 50 |
取单个症状的完整诊断树：澄清问题、全部原因与修复步骤、配件、停手边界。内容最全但约占 2,350 字符，只在需要整棵树时用。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | no | 品类 id，如 air_conditioner |
| symptom_id | string | no | 症状 id，如 not_cooling |
| query | string | no | 可选：口语描述，省略 id 时用它定位 |
问→诊主入口：给定品类与症状，返回澄清问题与按先验概率排序的 likely_causes（含修复步骤）。适合 AI 助手直接引用。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category_id | string | no | — |
| symptom_id | string | no | — |
| query | string | no | 可选：口语描述，省略 id 时用它定位 |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Wenjia Home-Fix Diagnosis 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: —
ATrust score 98 / 100
Scanned: 0.2.9 · 11 Nov 2026
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 score98
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationnone
Surface digest71f2a405918d31e2a359c281cc6c52242ebdcf46cb0deb44acfb4fba8de98225
Score vectorthreat 100 → client 98
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
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 digest71f2a405918d31e2
Scanned2026-11-11
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.8. Pin a release below and the command asks for exactly that one.
0.2.8
11 Nov 2026
latestNo release note was published with this version.
0.2.3
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Wenjia Home-Fix Diagnosis 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.