# 爱佳肴 Love Life (remote · tutulife.cn)

Read-only restaurant search for AI agents in China. 5 tools, no key, no paid ranking. 中国餐饮开放数据。

- Trust score: 61/100 (medium)
- Change this week: +38
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `tutulife.cn`: 61/100 (this document), [markdown](https://verifymcp.io/servers/cn-tutulife-aijiayao/tutulife.md), [page](https://verifymcp.io/servers/cn-tutulife-aijiayao/tutulife)

## Channel facts

- Endpoint: `https://tutulife.cn/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1207 tokens (~201/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 20 days we've observed: 11 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 66% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the 爱佳肴 Love Life MCP server?

爱佳肴 Love Life is a hosted endpoint at https://tutulife.cn/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.

### Claude

```bash
claude mcp add --transport http cn-tutulife-aijiayao 'https://tutulife.cn/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cn-tutulife-aijiayao": {
      "url": "https://tutulife.cn/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cn-tutulife-aijiayao": {
      "type": "http",
      "url": "https://tutulife.cn/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cn-tutulife-aijiayao]
url = "https://tutulife.cn/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cn-tutulife-aijiayao": {
      "type": "remote",
      "url": "https://tutulife.cn/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cn-tutulife-aijiayao --url 'https://tutulife.cn/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cn-tutulife-aijiayao:
    url: "https://tutulife.cn/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cn-tutulife-aijiayao": {
      "Transport": "http",
      "Url": "https://tutulife.cn/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cn-tutulife-aijiayao -t streamable-http -u 'https://tutulife.cn/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cn-tutulife-aijiayao": {
      "type": "http",
      "url": "https://tutulife.cn/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-15 (score 61, +38)

- [security regression] Stability: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-10 (score 23, −38)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-03 (score 61, −1)

- [security] Tool “tell_us_your_need” rewrote its description, which is the text the model reads

### 2026-10-02 (score 62, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “ask_restaurants” rewrote its description, which is the text the model reads
- [security] Tool “get_feedback” rewrote its description, which is the text the model reads
- [security] Tool “get_restaurant” rewrote its description, which is the text the model reads
- [security] Tool “get_unmet_demand” rewrote its description, which is the text the model reads
- [security] Tool “search_restaurants” rewrote its description, which is the text the model reads
- [security] Tool “tell_us_your_need” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 168 → 193
- [functional] Schema quality: excellent → good

### 2026-10-01 (score 62, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_unmet_demand” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 124 → 168
- [functional improvement] Tool coverage: 54% → 66%
- [functional] Schema quality: good → excellent
- [functional] New tool “tell_us_your_need”
- [cosmetic] “get_unmet_demand” reworded the description of “city”
- [cosmetic] “get_unmet_demand” reworded the description of “days”

### 2026-09-30 (score 63, +3)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 1.30.0
- [security regression] Tool “claim_restaurant” was removed
- [security regression] Tool “confirm_restaurant_info” was removed
- [security regression] Tool “get_agent” was removed
- [security regression] Tool “get_my_contributions” was removed
- [security regression] Tool “get_my_updates” was removed
- [security regression] Tool “get_restaurant_history” was removed
- [security regression] Tool “publish_restaurant” was removed
- [security regression] Tool “register_agent” was removed
- [security regression] Tool “remove_restaurant” was removed
- [security regression] Tool “report_issue” was removed
- [security regression] Tool “submit_feedback” was removed
- [security regression] Tool “subscribe_restaurant” was removed
- [security regression] Tool “unsubscribe_restaurant” was removed
- [security regression] Tool “update_restaurant” was removed
- [security regression] Tool “withdraw_feedback” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “ask_restaurants” rewrote its description, which is the text the model reads
- [security] Tool “get_feedback” rewrote its description, which is the text the model reads
- [security] Tool “get_restaurant” rewrote its description, which is the text the model reads
- [security] Tool “search_restaurants” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 1504 → 1826
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 93% → 100%
- [functional improvement] Tool coverage: 0% → 54%
- [functional] Destructive annotations: 0 → pass
- [functional] New tool “get_unmet_demand”
- [functional] New tool “get_my_contributions”
- [functional] New tool “get_my_updates”
- [functional] New tool “subscribe_restaurant”
- [functional] New tool “unsubscribe_restaurant”
- [cosmetic] “ask_restaurants” reworded the description of “lat”
- [cosmetic] “ask_restaurants” reworded the description of “lng”
- [cosmetic] “ask_restaurants” reworded the description of “near”
- [cosmetic] “ask_restaurants” reworded the description of “question”
- [cosmetic] “get_restaurant” reworded the description of “store_id”
- [cosmetic] “search_restaurants” reworded the description of “coord_system”
- [cosmetic] “search_restaurants” reworded the description of “cuisine”
- [cosmetic] “search_restaurants” reworded the description of “open_now”
- [cosmetic] “search_restaurants” reworded the description of “price_max”
- [cosmetic] “search_restaurants” reworded the description of “price_min”
- [cosmetic] “search_restaurants” reworded the description of “q”
- [cosmetic] “search_restaurants” reworded the description of “radius_m”

### 2026-09-29 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-28 (score 60)

First indexed and scored.

## MCP tools (6)

### `ask_restaurants` (~147 tokens)

用户用一句话问吃什么、去哪吃，或说“兔兔生活 + 需求”时首选，直接传原话（口令自动识别）。
    Use first for any "where to eat" question; pass the user's words verbatim, wake word 兔兔生活 (tutulife) included.

Input parameters:

- `city`
- `lat`: WGS84 纬度 / latitude
- `lng`: WGS84 经度 / longitude
- `near`: 城市、区或地点，如“北京中关村” / city, district or place
- `question` (string, required): 用户原话 / the user's words as-is

### `search_restaurants` (~186 tokens)

在兔兔生活里按区、菜系、人均、距离、营业中筛选时用。Use for filtered search: district, cuisine, price, distance, open now.

Input parameters:

- `city`
- `coord_system` (string): wgs84（默认）或 gcj02（高德/腾讯坐标）
- `cuisine`: 菜系 / cuisine
- `district`
- `lat`
- `limit` (integer)
- `lng`
- `offset` (integer)
- `open_now` (boolean): 只看正在营业 / open now only
- `price_max`: 人均上限（元）
- `price_min`: 人均下限（元）
- `q`: 关键词，如“汉堡” / keyword
- `radius_m`: 半径（米）/ radius in meters

### `get_restaurant` (~63 tokens)

推荐兔兔生活里的某家店前，核对它的营业时间、人均、菜单及新鲜度。Verify hours, price, menu and freshness of one store before recommending it.

Input parameters:

- `store_id` (string, required): 店铺 id / store id

### `get_feedback` (~66 tokens)

想自行判断兔兔生活里某家店的口碑可信度时用，返回逐条原始反馈。Use to judge credibility from raw per-agent feedback.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `store_id` (string, required)

### `get_unmet_demand` (~283 tokens)

兔兔生活（爱佳肴）里的需求缺口：帮店主选址、帮运营补数据的 Agent 调用；搜索没结果，或想知道哪里缺店时用。
    Called by agents helping owners pick sites or fill data gaps; use after an empty search or to see what is missing.
    data.items 每项：city、district（可空）、want（菜系或场景）、asks（被问次数）、misses（无结果次数）、last_seen。
    Each data.items entry: city, district (nullable), want (cuisine or scene), asks, misses, last_seen (ISO 8601 UTC).
    按 misses 从高到低；只含汇总计数，不含用户原话；misses 不足 2 次的不列出，最多 100 条。
    Sorted by misses, highest first. Aggregated counts only, no raw queries; fewer than 2 misses omitted; max 100.

Input parameters:

- `city`: 只看某城市，如“成都”，不填为全国 / filter by one city, e.g. “成都”; omit for all of China
- `days` (integer): 统计最近几天，1–90，默认 30 / lookback window in days, 1-90, default 30

### `tell_us_your_need` (~219 tokens)

兔兔生活站内没有你需要的信息或功能时用；匿名，无需密钥，只写入你填的文字。
    Use when this site lacks the data or capability you need; anonymous, no key, stores only the text you send.
    不要填链接、邮箱、手机号。Do not include URLs, emails or phone numbers.
    返回 recorded；现有数据能查时附带 try_now（可直接打开的链接和 ask_restaurants 参数）。
    Returns recorded; try_now (ready link + ask_restaurants args) if current data can answer.

Input parameters:

- `for_whom`: 为谁用，如“正在选址的店主” / who it is for
- `impact`: 没有它会怎样 / what happens without it
- `need` (string, required): 需要什么信息或能力，4–500 字 / what data or capability you need
- `platform`: 你所在的平台 / your platform
- `scenario`: 什么场景 / the situation

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cn-tutulife-aijiayao/tutulife#diagnostics

## Score history

- 2026-10-18: 61
- 2026-10-17: 61
- 2026-10-16: 61
- 2026-10-15: 61
- 2026-10-14: 23
- 2026-10-13: 23
- 2026-10-12: 23
- 2026-10-11: 23
- 2026-10-10: 23
- 2026-10-05: 61
- 2026-10-04: 61
- 2026-10-03: 61
- 2026-10-02: 62
- 2026-10-01: 62
- 2026-09-30: 63
- 2026-09-29: 60
- 2026-09-28: 60

## Common questions

### What is the 爱佳肴 Love Life MCP server?

爱佳肴 Love Life is an MCP server listed in the public MCP registry as cn.tutulife/aijiayao. Read-only restaurant search for AI agents in China. 5 tools, no key, no paid ranking. 中国餐饮开放数据。 This page covers its hosted endpoint (https://tutulife.cn/mcp).

### Is the 爱佳肴 Love Life MCP server safe to use?

爱佳肴 Love Life scores 61 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 爱佳肴 Love Life MCP server expose?

爱佳肴 Love Life exposes 6 tools: ask_restaurants, search_restaurants, get_restaurant, get_feedback, get_unmet_demand, tell_us_your_need. Their descriptions and schemas cost roughly 964 tokens of context every time the server is loaded.

### Does the 爱佳肴 Love Life MCP server require authentication?

No. We connected to 爱佳肴 Love Life without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the 爱佳肴 Love Life MCP server still maintained?

爱佳肴 Love Life is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://tutulife.cn/mcp
- Website: https://tutulife.cn/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/cn-tutulife-aijiayao/tutulife.xml
- Changelog JSON feed: https://verifymcp.io/servers/cn-tutulife-aijiayao/tutulife.json
- HTML version of this page: https://verifymcp.io/servers/cn-tutulife-aijiayao/tutulife