mcp-registry/cn.tutulife/aijiayao · v1.30.0
As of 2026-10-26 18:45 UTC, the Tutulife Aijiayao MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 4 minutes.
Read-only restaurant search for AI agents in China. 5 tools, no key, no paid ranking. 中国餐饮开放数据。
Point your MCP client at this streamable-http endpoint: https://tutulife.cn/mcp
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
10 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcn.tutulife%2Faijiayao/fixes
{
"name": "get_feedback",
"description": "想自行判断兔兔生活里某家店的口碑可信度时用,返回逐条原始反馈。Use to judge credibility from raw per-agent feedback.",
"inputSchema": {
"type": "object",
"title": "get_feedbackArguments",
"required": [
"store_id"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 50
},
"offset": {
"type": "integer",
"title": "Offset",
"default": 0
},
"store_id": {
"type": "string",
"title": "Store Id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_restaurant",
"description": "推荐兔兔生活里的某家店前,核对它的营业时间、人均、菜单及新鲜度。Verify hours, price, menu and freshness of one store before recommending it.",
"inputSchema": {
"type": "object",
"title": "get_restaurantArguments",
"required": [
"store_id"
],
"properties": {
"store_id": {
"type": "string",
"title": "Store Id",
"description": "店铺 id / store id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_unmet_demand",
"description": "兔兔生活(爱佳肴)里的需求缺口:帮店主选址、帮运营补数据的 Agent 调用;搜索没结果,或想知道哪里缺店时用。\n Called by agents helping owners pick sites or fill data gaps; use after an empty search or to see what is missing.\n data.items 每项:city、district(可空)、want(菜系或场景)、asks(被问次数)、misses(无结果次数)、last_seen。\n Each data.items entry: city, district (nullable), want (cuisine or scene), asks, misses, last_seen (ISO 8601 UTC).\n 按 misses 从高到低;只含汇总计数,不含用户原话;misses 不足 2 次的不列出,最多 100 条。\n Sorted by misses, highest first. Aggregated counts only, ",
"inputSchema": {
"type": "object",
"title": "get_unmet_demandArguments",
"properties": {
"city": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "City",
"default": null,
"description": "只看某城市,如“成都”,不填为全国 / filter by one city, e.g. “成都”; omit for all of China"
},
"days": {
"type": "integer",
"title": "Days",
"default": 30,
"description": "统计最近几天,1–90,默认 30 / lookback window in days, 1-90, default 30"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/cn.tutulife/aijiayao"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/cn.tutulife/aijiayao"}) over MCP.
search_restaurants ~416 tokenstell_us_your_need ~324 tokensget_unmet_demand ~260 tokensask_restaurants ~241 tokensget_feedback ~108 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcn.tutulife%2Faijiayao?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcn.tutulife%2Faijiayao?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcn.tutulife%2Faijiayao.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcn.tutulife%2Faijiayao.svg :target: https://glimind.com/server/mcp-registry%2Fcn.tutulife%2Faijiayao?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cec722f586753e70…, first seen 2026-10-17, included at leaf 13621 of 74,829. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable retrieval servers · most reliable search servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:45 UTC, the Tutulife Aijiayao MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 4 minutes.
Tutulife Aijiayao MCP server advertises 6 tools, including ask_restaurants, get_feedback, get_restaurant, get_unmet_demand, search_restaurants.
Point your MCP client at this streamable-http endpoint: https://tutulife.cn/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.