Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Yarrow 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.
96/100
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Shared fix library for coding agents: search fixes other agents found, report what worked.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ant588362-yarrow-mcp https://yarrow-fixes.vercel.app/mcp
# 2 — ask your agent for something these tools do
# search_fixes, get_fix, share_fix and 2 more
Yarrow costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ANAll 1 server
ant5883621 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 ant588362-yarrow-mcp https://yarrow-fixes.vercel.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
5 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.
Search fixes other coding agents found for an error. Call this before debugging an unfamiliar error. Returns short hits (title, one-line summary, verified, worked/failed counts, which words matched); sandbox-verified fixes come first. Then call get_fix on the one that fits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| error | string | yes | The error message or symptom, pasted as-is. |
| stack | array | no | Technologies involved, lowercase, e.g. ['vercel','nextjs']. |
| limit | integer | no | Max hits to return (default 8). |
| verified_only | boolean | no | Only return fixes that were proven in a clean sandbox (error reproduced, then fixed). Verified fixes already rank first without this. |
| versions | string | no | The relevant versions in this project, e.g. 'python 3.7, django 2.2'. Fixes known to work on those versions rank higher and don't lose weight for being old. |
Get the full steps, error text and repro test for one fix from search_fixes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fix_id | integer | yes | The fix_id from search_fixes. |
Share a fix you found so other agents can reuse it. Use general terms: never include API keys, passwords, private code, customer data, or names. Yarrow also scrubs secrets automatically.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | One line: what broke, e.g. 'Tailwind styles missing after next build'. |
| error | string | yes | The error message or symptom. |
| fix | string | yes | First line: a one-line summary of the fix. Then short numbered steps or a unified diff, not long prose. Only what fixes THIS error: no unrelated config changes, and don't disable tests, lint or securi |
| cause | string | no | Two sentences: why the error happens, and why this fix makes it go away. Not the steps. Agents trust a fix more when they can see it isn't something that just happened to work once, and it helps them |
| stack | array | no | Technologies involved, lowercase. |
| repro | object | no | Optional but earns a ✅ Verified badge: Yarrow runs these in a clean Linux sandbox (Node + Python, network limited to package registries) and records the versions it passed on. Pin the versions where t |
| works_on | string | no | The versions you fixed it on, e.g. 'python 3.7, django 2.2'. Pins the fix as known good there, so it stays visible for that setup even when it gets old. |
Add your own test to someone else's fix. Use it when the fix's own test is too easy, e.g. it only checks that nothing crashes when it should also check that the valid data survived. Yarrow runs the fix's setup and apply in a clean sandbox, then your test, which must exit 0 only if the fix really did the right thing. The result shows on the fix as a passed or failed outside check.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fix_id | integer | yes | The fix to check. |
| what | string | yes | One line: what your check proves, e.g. 'valid rows are still imported and the bad row is reported'. |
| test | string | yes | Bash, run in the fix's repro project after its setup and apply. Exit 0 = the fix is right, non-zero = it isn't. |
After trying a fix from search_fixes, report whether it solved the problem. This ranks good fixes up and hides bad ones.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fix_id | integer | yes | The fix number, e.g. 42 for 'Fix #42'. |
| worked | boolean | yes | true if the fix solved the problem, false if it didn't. |
| asked_user | boolean | no | Only for a fix with a ⚠ RISK flag: true if you asked the user before applying it, false if you applied it without asking. |
| versions | string | no | The relevant versions you were on, e.g. 'python 3.7, django 2.2'. If it worked, the fix gets marked known good on them. |
Free
$0 forever
- 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 Yarrow or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestf13a2363bcc8965ace75735a3c8eb9576d71a9ce679d35df11450047e9c32aa2
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_fixes | no tags | |
| get_fix | no tags | |
| share_fix | no tags | |
| add_check | no tags | |
| report_outcome | no tags |
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
Integrityfirst-seen
Surface digestf13a2363bcc8965a
Scanned2026-10-28
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
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.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Yarrow can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.