Is the Yarrow MCP server down?

mcp-registry/io.github.ant588362/yarrow · registry v1.0.0 · server reports v0.1.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 19:48 UTC · handshake 202ms

As of 2026-11-22 19:48 UTC, the Yarrow MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
876
outages (90d)
0
tools
5

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

Point your MCP client at this streamable-http endpoint: https://yarrow-fixes.vercel.app/mcp

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 5 tool(s); ~1,546 tokens of tool definitions.
Scores higher than 37% of 27,666 MCP servers Glimind has audited.
Its tool list costs an agent ~1,546 tokens per session — lighter than 55% of servers.
85 → 85 since 2026-11-16
no tool-poisoning patterns
Descriptions100
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (2)

5 of 5 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 →

Tools: add_check, get_fix, report_outcome, search_fixes, share_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 →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.ant588362%2Fyarrow/fixes

add_check 1 change
{
  "name": "add_check",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "fix_id",
      "what",
      "test"
    ],
    "properties": {
      "test": {
        "type": "string",
        "minLength": 4,
        "description": "Bash, run in the fix's repro project after its setup and apply. Exit 0 = the fix is right, non-zero = it isn't."
      },
      "what": {
        "type": "string",
        "minLength": 8,
        "description": "One line: what your check proves, e.g. 'valid rows are still imported and the bad row is reported'."
      },
      "fix_id": {
        "type": "integer",
        "maximum": 9007199254740991,
        "description": "The fix to check.",
        "exclusiveMinimum": 0
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add an outside check to a Yarrow fix"
}
get_fix 1 change
{
  "name": "get_fix",
  "description": "Get the full steps, error text and repro test for one fix from search_fixes.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "fix_id"
    ],
    "properties": {
      "fix_id": {
        "type": "integer",
        "maximum": 9007199254740991,
        "description": "The fix_id from search_fixes.",
        "exclusiveMinimum": 0
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get a Yarrow fix"
}
search_fixes 1 change
{
  "name": "search_fixes",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "error"
    ],
    "properties": {
      "error": {
        "type": "string",
        "minLength": 3,
        "description": "The error message or symptom, pasted as-is."
      },
      "limit": {
        "type": "integer",
        "maximum": 10,
        "minimum": 1,
        "description": "Max hits to return (default 8)."
      },
      "stack": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Technologies involved, lowercase, e.g. ['vercel','nextjs']."
      },
      "versions": {
        "type": "string",
        "description": "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."
      },
      "verified_only": {
        "type": "boolean",
        "description": "Only return fixes that were proven in a clean sandbox (error reproduced, then fixed). Verified fixes already rank first without this."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Search Yarrow fixes"
}

Get alerted

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/io.github.ant588362/yarrow"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.ant588362/yarrow"}) over MCP.

Passed

Largest tool definitions

Static 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.ant588362%2Fyarrow.svg)](https://glimind.com/server/mcp-registry%2Fio.github.ant588362%2Fyarrow?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.ant588362%2Fyarrow?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.ant588362%2Fyarrow.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:889cee1410f67d85…, first seen 2026-11-16, included at leaf 300574 of 385,048. Version history · verify what your client received.

Tools (5)

Compare: most reliable code servers · most reliable knowledge servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Yarrow MCP server down right now?

As of 2026-11-22 19:48 UTC, the Yarrow MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Yarrow MCP server provide?

Yarrow MCP server advertises 5 tools, including add_check, get_fix, report_outcome, search_fixes, share_fix.

How do I install Yarrow MCP server?

Point your MCP client at this streamable-http endpoint: https://yarrow-fixes.vercel.app/mcp

Is the Yarrow MCP server safe to connect to an AI agent?

Glimind scanned all 5 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.

Operator of Yarrow MCP server?

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.

Feedback
Help us improve