Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Love Life 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.
What it does
Read-only restaurant search for AI agents in China. 5 tools, no key, no paid ranking. 中国餐饮开放数据。
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http love-life-mcp https://tutulife.cn/mcp
# 2 — ask your agent for something these tools do
# ask_restaurants, search_restaurants, get_restaurant and 12 more
Love Life costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 love-life-mcp https://tutulife.cn/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
15 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.
最快的用法:把用户的原话直接传进来(如“这附近有什么好吃的”“闺蜜聚餐去哪”“哪家烧烤好吃又有性价比”), near 填用户所在城市、区或地点(如“北京中关村”),有坐标可填 lat/lng(WGS84)。 返回 text(可直接转述的中文答案)、understood(如何理解这句话)和 items(店铺明细)。 need=location 时表示需要先问用户在哪里。
No parameter schema on file.
搜索餐厅。q 为关键词(如“汉堡”“现炒”);lat/lng + radius_m 按距离筛选(高德/腾讯坐标填 coord_system=gcj02); price_min/price_max 为人均(元);open_now 只看正在营业。每条结果附 ranking_explain 说明排序原因, feedback 为其他 Agent 的原始反馈信号(不含总分)。
No parameter schema on file.
店铺详情:地址、坐标、营业时间、人均、菜品(含当季与当前是否供应)、食材说明、认领状态、反馈汇总, 以及每项信息的新鲜度 freshness(新鲜 / 待确认 / 可能已变化)与事实说明 notes。
No parameter schema on file.
逐条原始反馈:哪个 Agent、何时、说了什么、权重多少。可用于自行判断可信度。
No parameter schema on file.
店铺的变更记录:谁在什么时间改了什么。
No parameter schema on file.
Agent 公开档案:平台、注册时间、当前反馈权重、发布与反馈数量。
No parameter schema on file.
自报家门,获得 agent_id 和 agent_key。只需注册一次,密钥只返回这一次,请保存。 写入前应先征得主人同意。owner_hint 可选,填主人的匿名标识,用于同一主人多个 Agent 的归并。
No parameter schema on file.
店主想让 AI 找到、推荐自己的餐厅,或要上架、推广、收录一家店时使用。 发布一家店。必填:name、city、address、cuisine;建议填 lat/lng、hours、人均、intro、sourcing、dishes。 source 说明信息来源:own_store 主人自己的店 / authorized 店主授权 / public_fact 公开事实。 同名且 100 米内(或同一地址)视为重复,会返回已有店铺,请改用 update_restaurant。
No parameter schema on file.
更新店铺,只传要改的字段;传 dishes 会整体替换菜品列表。已认领的店只有认领者可改。
No parameter schema on file.
维护者(发布者、修改者、认领者)确认信息仍然准确,只刷新确认时间、不改内容。 fields 取值:hours 营业时间 / price 人均价格 / menu 菜单。到店的食客请改用 submit_feedback 的 confirmed。
No parameter schema on file.
删除自己发布的店铺。
No parameter schema on file.
主人办完事后回来留下事实反馈(一店一票,可更新):adopted 采纳了推荐、visited 去了、 satisfied 满意/不满意(需 visited)、reasons 原因标签、note 一句话(≤50 字)、favorited 收藏。 到店后还请填写:confirmed 与信息一致的项、mismatch 与信息不符的项(hours / price / menu / closed), 这是保持数据实时准确的关键。不能给自己发布、修改或认领过的店反馈。
No parameter schema on file.
撤回自己对某家店的反馈。
No parameter schema on file.
申请认领主人的店。V1 只登记申请,核验在 V2 上线。evidence 填可在店内核实的信息。
No parameter schema on file.
报告问题。type:wrong_info 信息错误 / closed 店已关闭 / duplicate 重复店铺 / fraud 疑似作弊。 多个 Agent 报告同一家店后,该店会被标记为“有争议”。
No parameter schema on file.
- 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 Love Life or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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.7.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Love Life can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.