mcp-registry/io.github.shaozhengkun123/yarrow · v0.1.0
Also listed as glama/shaozhengkun123/yarrow
As of 2026-10-26 09:12 UTC, the Shaozhengkun123 Yarrow MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
I-Ching (周易) oracle: cast a hexagram, read classical commentary, get a reflection. Bilingual.
Claude Code
claude mcp add --transport http shaozhengkun123-yarrow-mcp-server https://yarrow-oracle.shaozhengkun.workers.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"shaozhengkun123-yarrow-mcp-server": {
"type": "http",
"url": "https://yarrow-oracle.shaozhengkun.workers.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
7 of 7 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 →
6 parameter(s) across 4 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 →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. 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. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.shaozhengkun123%2Fyarrow/fixes
{
"name": "lookup_hexagram",
"description": "Return the full classical sources for a hexagram by its number (1–64): judgment (卦辞), image (大象), Tuan commentary, Zhu Xi 周易本义, Yang Tian Cai modern explanation, Yarrow's separately labelled Chinese reading aid, and historical anecdote — with available Chinese and English source material.",
"inputSchema": {
"type": "object",
"required": [
"number"
],
"properties": {
"locale": {
"enum": [
"en",
"zh",
"both"
],
"type": "string",
"default": "both"
},
"number": {
"type": "integer",
"maximum": 64,
"minimum": 1,
"description": "Hexagram number 1-64 in King Wen sequence."
},
"compact": {
"type": "boolean",
"default": false,
"description": "If true, omit authorities (long classical commentary). Returns only structural fields."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "lookup_yilin",
"description": "Look up the 焦氏易林 verse for a primary hexagram changing into another hexagram. This is a local classical-source lookup, not an AI reading.",
"inputSchema": {
"type": "object",
"required": [
"primary_number",
"changing_number"
],
"properties": {
"primary_number": {
"type": "integer",
"maximum": 64,
"minimum": 1,
"description": "Primary hexagram number 1-64."
},
"changing_number": {
"type": "integer",
"maximum": 64,
"minimum": 1,
"description": "Changing hexagram number 1-64."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "tarot_reading",
"description": "Ask one real question through a single upright Waite-Smith Major Arcana card. Returns a direct calibrated answer first, the named card and bound Arthur Edward Waite 1910 source excerpt, a practical reality check, and one observable next step. No reversals, astrology, redraw loop, or guaranteed prediction. Daily quota is shared with completed divine and Two Lenses readings.",
"inputSchema": {
"type": "object",
"required": [
"question"
],
"properties": {
"seed": {
"type": [
"string",
"number"
],
"description": "Deterministic Tarot draw seed."
},
"locale": {
"enum": [
"en",
"zh",
"zh-Hant",
"ja",
"ko",
"es",
"fr",
"de",
"pt",
"it",
"ru",
"ar",
"hi",
"id",
"bilingual"
],
"type": "string",
"default": "en"
},
"question": {
"type": "string",
"description": "The real question to reflect on."
},
"device_id": {
"type": "string",
"description": "Optional opaque identifier for quota tracking. If omitted, IP-derived."
}
}
},
"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/io.github.shaozhengkun123/yarrow"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.shaozhengkun123/yarrow"}) over MCP.
two_lenses ~315 tokensdivine ~303 tokenstarot_reading ~251 tokenscast_hexagram ~249 tokenslookup_hexagram ~204 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%2Fio.github.shaozhengkun123%2Fyarrow?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.shaozhengkun123%2Fyarrow?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.shaozhengkun123%2Fyarrow.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.shaozhengkun123%2Fyarrow.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.shaozhengkun123%2Fyarrow?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:a745a0f6f5f4d520…, first seen 2026-10-17, included at leaf 5617 of 71,862. Version history · verify what your client received.
Compare: most reliable other servers · most reliable knowledge 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 09:12 UTC, the Shaozhengkun123 Yarrow MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Shaozhengkun123 Yarrow MCP server advertises 7 tools, including cast_hexagram, cast_tarot, divine, lookup_hexagram, lookup_yilin.
Point your MCP client at this streamable-http endpoint: https://yarrow-oracle.shaozhengkun.workers.dev/mcp
Glimind scanned all 7 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.