io.github.shaozhengkun123/yarrow
REMOTE · YARROW-ORACLE.SHAOZHENGKUN.WORKERS.DEV · SCANNED SEP 28
I-Ching (周易) oracle: cast a hexagram, read classical commentary, get a reflection. Bilingual.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 964 tokens (~137/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 76% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.shaozhengkun123/yarrow MCP server?
io.github.shaozhengkun123/yarrow is a hosted endpoint at https://yarrow-oracle.shaozhengkun.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · yarrow-oracle.shaozhengkun.workers.dev
claude mcp add --transport http shaozhengkun123-yarrow 'https://yarrow-oracle.shaozhengkun.workers.dev/mcp'
{
"mcpServers": {
"shaozhengkun123-yarrow": {
"url": "https://yarrow-oracle.shaozhengkun.workers.dev/mcp"
}
}
} {
"servers": {
"shaozhengkun123-yarrow": {
"type": "http",
"url": "https://yarrow-oracle.shaozhengkun.workers.dev/mcp"
}
}
} [mcp_servers.shaozhengkun123-yarrow] url = "https://yarrow-oracle.shaozhengkun.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shaozhengkun123-yarrow": {
"type": "remote",
"url": "https://yarrow-oracle.shaozhengkun.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add shaozhengkun123-yarrow --url 'https://yarrow-oracle.shaozhengkun.workers.dev/mcp' --transport streamable-http
mcp_servers:
shaozhengkun123-yarrow:
url: "https://yarrow-oracle.shaozhengkun.workers.dev/mcp" {
"McpServers": {
"shaozhengkun123-yarrow": {
"Transport": "http",
"Url": "https://yarrow-oracle.shaozhengkun.workers.dev/mcp"
}
}
} assistant mcp add shaozhengkun123-yarrow -t streamable-http -u 'https://yarrow-oracle.shaozhengkun.workers.dev/mcp'
{
"mcpServers": {
"shaozhengkun123-yarrow": {
"type": "http",
"url": "https://yarrow-oracle.shaozhengkun.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Aug 26 0
- Schema quality: 824 → 964 ▼ functional
- New tool “tarot_reading” functional
- 3 Aug 26 0
- Schema quality: 557 → 824 ▼ functional
- New tool “cast_tarot” functional
- New tool “two_lenses” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://yarrow-oracle.shaozhengkun.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shaozhengkun.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 637a8f3297b89ef1ac3aa3661008d33997a |
| SANs: *.shaozhengkun.workers.dev, shaozhengkun.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of yarrow-oracle.shaozhengkun.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yarrow-oracle.shaozhengkun.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://yarrow-oracle.shaozhengkun.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cast_hexagram ~171
Cast a hexagram for an I-Ching consultation. Returns the primary hexagram, the six lines (6=old yin, 7=young yang, 8=young yin, 9=old yang from bottom to top), any moving lines, and the changing hexagram if there are moving lines. Pass `seed` to make the cast deterministic (useful for testing or for reproducing a reading).
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | coins = three-coin toss (most common); yarrow = traditional 50-stalk probabilities; random = uniformly pick one of the 64 hexagrams with no moving lines. |
| question | string | – | The question being asked (not used for casting, returned in result for context). |
| seed | string|number | – | Optional seed for deterministic casting. |
No output schema declared.
No examples provided.
cast_tarot ~96
Draw one upright Major Arcana card for reflection. Uses a deterministic one-card Waite-Smith Major Arcana method and returns a selected source excerpt from Arthur Edward Waite's public-domain 1910/1922 text. Pass `seed` to reproduce the same draw.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | – | The question being reflected on (not used to influence the draw). |
| seed | string|number | – | Optional deterministic draw seed. |
No output schema declared.
No examples provided.
divine ~190
Ask the I Ching. See your next step. Cast a hexagram, show the classical sources first, then offer a thoughtful reflection grounded in those sources. Sources first. Reflection, not prediction. The divine name remains stable for oracle/divination client compatibility. Supports English, Chinese, Japanese, Korean, Spanish, French, German, Portuguese, Italian, Russian, Arabic, Hindi, Indonesian, and English+Chinese bilingual output. Daily quota: 30 completed readings per device_id (or per anonymous IP if no device_id is supplied); timeout, provider failure, incomplete response, and cancellation do not consume it.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Optional opaque identifier for quota tracking. If omitted, IP-derived. |
| locale | string | – | – |
| method | string | – | – |
| question | string | yes | The question to consult on. |
| seed | string|number | – | Deterministic cast seed. |
No output schema declared.
No examples provided.
lookup_hexagram ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | If true, omit authorities (long classical commentary). Returns only structural fields. |
| locale | string | – | – |
| number | integer | yes | Hexagram number 1-64 in King Wen sequence. |
No output schema declared.
No examples provided.
lookup_yilin ~74
Look up the 焦氏易林 verse for a primary hexagram changing into another hexagram. This is a local classical-source lookup, not an AI reading.
| Name | Type | Req | Description |
|---|---|---|---|
| changing_number | integer | yes | Changing hexagram number 1-64. |
| primary_number | integer | yes | Primary hexagram number 1-64. |
No output schema declared.
No examples provided.
tarot_reading ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Optional opaque identifier for quota tracking. If omitted, IP-derived. |
| locale | string | – | – |
| question | string | yes | The real question to reflect on. |
| seed | string|number | – | Deterministic Tarot draw seed. |
No output schema declared.
No examples provided.
two_lenses ~171
Bring one real question to two independent symbolic traditions: a source-first I-Ching cast and one upright Waite-Smith Major Arcana card. Returns a clear calibrated answer first, then five grounded sections covering the I Ching lens, Tarot lens, shared themes, different emphasis, and next step. Direction without guaranteed prediction or mutual-confirmation claims. Daily quota is shared with completed divine readings.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Optional opaque identifier for quota tracking. If omitted, IP-derived. |
| iching_seed | string|number | – | Deterministic I-Ching cast seed. |
| locale | string | – | – |
| method | string | – | – |
| question | string | yes | The same real question for both lenses. |
| tarot_seed | string|number | – | Deterministic Tarot draw seed. |
No output schema declared.
No examples provided.
What is the io.github.shaozhengkun123/yarrow MCP server?
io.github.shaozhengkun123/yarrow is an MCP server listed in the public MCP registry as io.github.shaozhengkun123/yarrow. I-Ching (周易) oracle: cast a hexagram, read classical commentary, get a reflection. Bilingual. This page covers its hosted endpoint (https://yarrow-oracle.shaozhengkun.workers.dev/mcp).
Is the io.github.shaozhengkun123/yarrow MCP server safe to use?
io.github.shaozhengkun123/yarrow scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.shaozhengkun123/yarrow MCP server expose?
io.github.shaozhengkun123/yarrow exposes 7 tools: cast_hexagram, lookup_hexagram, lookup_yilin, cast_tarot, divine, and 2 more. Their descriptions and schemas cost roughly 964 tokens of context every time the server is loaded.
Does the io.github.shaozhengkun123/yarrow MCP server require authentication?
No. We connected to io.github.shaozhengkun123/yarrow without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.shaozhengkun123/yarrow MCP server still maintained?
io.github.shaozhengkun123/yarrow is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.