问家家庭维修诊断 MCP Server
中文家庭维修自助诊断引擎的 MCP 服务端。40 品类 / 200 症状 / 800 原因 / 3,687 修复步骤。 纯 Python 标准库，零第三方依赖，只读，无鉴权。数据 CC BY 4.0。
装法与运行
uvx wenjia-home-fix-mcp # stdio 传输，给 MCP 客户端
python -m wenjia_home_fix STDIO # 等价写法（见下）
PORT=8765 wenjia-home-fix-mcp # streamable-http 传输，监听 127.0.0.1:8765/mcp
stdio 模式：wenjia-home-fix-mcp --stdio
工具
原子事实（省 token，给 agent）：
| 工具 | 返回 |
|---|---|
prob_distribution |
原因先验概率分布（合计 100）+ 能否 DIY，约 530 字符 |
price_band |
上门价格区间（元）+ 配件价，约 410 字符 |
stop_check |
风险等级（gas / electric / height）+ 必须停手的理由，约 420 字符 |
全树（丰富，给人）：
| 工具 | 返回 |
|---|---|
list_categories |
40 品类与症状数 |
search_symptoms |
跨品类关键词搜索 |
get_symptom |
单个症状完整诊断树，约 2,350 字符 |
diagnose |
按概率排序的原因 + 追问选项 |
同一症状下，三个原子工具比 get_symptom 省 77–83% 上下文。
我们刻意不卖的东西
分步修复文本——前沿模型自己写得已经很细。它造不出来的是先验概率、地域价格、涉险停手判断，这三个工具只为这三件事存在。
数据口径（诚实说明）
prob_prior是文献与经验先验，不是工单统计，只能当排序信号，不能当精确频率。- 价格是 2026 年中国市场区间（CNY），未建模地域差异。
- 覆盖城市住宅场景，农村自建房不在范围内。
- 每个症状带
see_pro字段（何时停手找持证技师），转发时不要删。
数据来自问家家庭维修诊断树（40 品类 200 症状，持续更新）。引用请保留出处与版本号。
1 maintainer
Metadata
1 maintainer
Release files for wenjia-home-fix-mcp 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wenjia_home_fix_mcp-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for wenjia_home_fix_mcp-0.1.4-py3-none-any.whl |
Release files / wenjia_home_fix_mcp-0.1.4-py3-none-any.whl
| Download URL | wenjia_home_fix_mcp-0.1.4-py3-none-any.whl |
|---|---|
| Size | 446.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3509166bc8faad22a89dd2eb9365c4d06a4fd822de71c509f5ad440345ee71ff
|
|
BLAKE2b-256 checksum How to use checksums |
f646598cc2cfdebed5df2be0837ac8f06215785d993a9842845d235b53359159
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for wenjia-home-fix-mcp 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
