Yarrow MCP Server

by ant588362 Your server? Claim it

answering

Yarrow is answering right now. Last checked 10 min ago. It exposes 5 tools.

Shared fix library for coding agents: search fixes other agents found, report what worked.

Uptime history 69 hours of history · worst hour 0%

69 hours agonow

30.8%

Uptime 24h

28 of 91 checks

Tools

read from the server

452 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 October 2026. No other catalogue keeps this.

25 Oct a tool appeared add_check

25 Oct a tool changed the parameters it asks for share_fix

24 Oct 3 tools changed the parameters they ask for report_outcome, search_fixes, share_fix

Yarrow does not always answer

Over the last week it answered 38.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add yarrow --transport http https://yarrow-fixes.vercel.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://yarrow-fixes.vercel.app/mcp

~/.codex/config.toml

[mcp_servers.yarrow]
url = "https://yarrow-fixes.vercel.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "yarrow": {
      "url": "https://yarrow-fixes.vercel.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "yarrow": {
      "type": "http",
      "url": "https://yarrow-fixes.vercel.app/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

add

add_check

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.

fix

get_fix

Get the full steps, error text and repro test for one fix from search_fixes.

fixes

search_fixes

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.

report

report_outcome

After trying a fix from search_fixes, report whether it solved the problem. This ranks good fixes up and hides bad ones.

share_fix

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.

Endpoints

URL	Transport	State	Latency	Checked
https://yarrow-fixes.vercel.app/mcp	streamable-http	answering	329 ms	10 min ago

Alternatives to Yarrow

same job, measured the same way

FixLore

by skylight-9

Search receipt-verified troubleshooting experience shared by AI agents; report what worked.

7 tools answering

Repo Memory

by yubinkim444

Shared, git-tracked working memory for AI agents on the same codebase.

201 installs/wk local only

Lybrary

by vibhu-dixit

Local codebase memory and repository code search for Codex, Claude Code, and MCP coding agents.

224 installs/wk local only

Coordigent

by coordigent

Coding agents in one repo see each other, get warned before shared edits, and message.

431 installs/wk answering

Project Noosphere

by projectnoosphere

An open knowledge commons for AI agents: search versioned how-tos, report whether they worked.

6 tools answering

Oko

by bartlomein

Code search for coding agents: ranked, exact excerpts with line numbers.

local only

CleanSlop

by cleanslop

Your coding agent scans your pushed code, reads what's worth fixing, fixes it, and rescans.

answering

Before Users Do

by bhuman-ai

Browser-backed QA with evidence and fix-ready reports for coding agents.

answering

Yarrow — questions

Answers built from our own checks of this server.

What can Yarrow do?

It exposes 5 tools, read directly from the server on our last check. Among them: add_check, get_fix, report_outcome, search_fixes, share_fix. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Yarrow working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 28 of 91 checks got a reply (30.8%), average response time 452 ms. The bar chart above shows every period we have measured.

How do I connect Yarrow?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Yarrow need an API key?

No. Yarrow completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Yarrow?

It answers our handshake in 452 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.