Resolve documentation ownership, edit roots, checks, and human handoffs before an agent edits code.
Chengyu Coach 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
Idiom learning server: Randomly selects idioms, checks their meanings and origins, and records the level of mastery based on dialogue performance.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user chengyu-coach-mcp '--' uvx chengyu-coach-mcp
# 2 — ask your agent for something these tools do
# draw_idiom, idiom_detail, search_idiom and 4 more
Chengyu Coach 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. This one runs on your machine: your client starts Chengyu Coach 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.
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 chengyu-coach-mcp '--' uvx chengyu-coach-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
7 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.
随机抽成语学习。优先抽没抽过的;都抽过一轮后,抽得最少且最久没抽的优先。默认跳过最近 20 条和已掌握的。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| count | integer | no | 抽几个(1~10) |
| include_mastered | boolean | no | 是否把已掌握的也放回抽奖池 |
查一个成语的释义、出处、古文例句,以及学习进度(抽中次数、状态、备注)。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| word | string | yes | 成语原文,如 守株待兔 |
按关键词搜成语(匹配成语、拼音或释义),并附各自的抽中次数。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | 关键词,中文或拼音缩写(如 szdt) |
| limit | integer | no | 最多返回几条(1~20) |
根据对话中用户的实际表现,更新成语的掌握状态。由 AI 自行判断调用,服务端不做判分。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| word | string | yes | 成语原文 |
| status | string | yes | learning=还不熟/答错/卡壳;reviewing=大致理解但不够稳;mastered=能准确解释并举一反三 |
给某个成语写备注(自由文本,如易错点、使用场景),会覆盖原备注。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| word | string | yes | 成语原文 |
| note | string | yes | 备注内容;传空字符串则清除备注 |
查看整体学习进度:接触了几个、各状态数量、有备注的、最近抽的 10 个。
Takes no parameters.
清空某个成语的学习记录(抽中次数、状态、备注),词库本身不受影响。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| word | string | yes | 成语原文 |
- 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 Chengyu Coach 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, 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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| draw_idiom | state-write | state-write: declares readOnlyHint: false, handler runs a INSERT statement at src/chengyu_coach_mcp/server.py:171, handler runs a UPDATE statement at src/chengyu_coach_mcp/server.py:177 |
| idiom_detail | no tags | |
| search_idiom | no tags | |
| update_status | state-write | state-write: declares readOnlyHint: false, handler runs a INSERT statement at src/chengyu_coach_mcp/server.py:245, handler runs a UPDATE statement at src/chengyu_coach_mcp/server.py:251 |
| add_note | state-write | state-write: declares readOnlyHint: false, handler runs a INSERT statement at src/chengyu_coach_mcp/server.py:271, handler runs a UPDATE statement at src/chengyu_coach_mcp/server.py:277 |
| progress | no tags | |
| reset_word | state-write | state-write: handler runs a DELETE statement at src/chengyu_coach_mcp/server.py:317 |
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
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 1.0.0. Pin a release below and the command asks for exactly that one.
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 Chengyu Coach 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.