Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

D8ly Read

REMOTE · D8LY.APP · SCANNED SEP 22

Read-only Bazi, True Solar Time, and Chinese almanac tools in English and Traditional Chinese.

Available components

remote · d8ly.app 81
+4 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 987 tokens (~329/item across 3 items; 3 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 Management63
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the D8ly Read MCP server?

D8ly Read is a hosted endpoint at https://d8ly.app/mcp?source=mcp_registry, 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 · d8ly.app

# add to Claude Code
claude mcp add --transport http dhsiao510-d8ly-read 'https://d8ly.app/mcp?source=mcp_registry'
// .cursor/mcp.json
{
  "mcpServers": {
    "dhsiao510-d8ly-read": {
      "url": "https://d8ly.app/mcp?source=mcp_registry"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dhsiao510-d8ly-read": {
      "type": "http",
      "url": "https://d8ly.app/mcp?source=mcp_registry"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dhsiao510-d8ly-read]
url = "https://d8ly.app/mcp?source=mcp_registry"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dhsiao510-d8ly-read": {
      "type": "remote",
      "url": "https://d8ly.app/mcp?source=mcp_registry",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dhsiao510-d8ly-read --url 'https://d8ly.app/mcp?source=mcp_registry' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dhsiao510-d8ly-read:
    url: "https://d8ly.app/mcp?source=mcp_registry"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dhsiao510-d8ly-read": {
      "Transport": "http",
      "Url": "https://d8ly.app/mcp?source=mcp_registry"
    }
  }
}
# add to Vellum
assistant mcp add dhsiao510-d8ly-read -t streamable-http -u 'https://d8ly.app/mcp?source=mcp_registry'
// mcp.json
{
  "mcpServers": {
    "dhsiao510-d8ly-read": {
      "type": "http",
      "url": "https://d8ly.app/mcp?source=mcp_registry"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 59 to 63.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 56.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 46 to 49.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 39 to 43.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 32 to 36.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 22 to 26.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 16 to 19.

  • 8 Sept 26 −5
    • Stability: 0.50 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • “calculate_bazi_chart” made “birth_time” required, so existing callers break ▼ functional
    • “get_daily_bazi_guidance” made “birth_time” required, so existing callers break ▼ functional
Diagnostics

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 22 Sept 2026 · Probed https://d8ly.app/mcp?source=mcp_registry

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.d8ly.app CN=YR1,O=Let's Encrypt,C=US 21 Sept 2026 20 Dec 2026 RSA 2048 SHA256-RSA 53bf91319a8bc905e0b3a51af933ee9b80a
SANs: *.d8ly.app, d8ly.app
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of d8ly.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
d8ly.app. 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
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://d8ly.app/mcp?source=mcp_registry Verified 200
http (plaintext) http://d8ly.app/mcp?source=mcp_registry HTTPS enforced 308 https://d8ly.app/mcp?source=mcp_registry
MCP tools · 3 exposed · ~907 tokens

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 →

Tool Tokens
calculate_bazi_chart ~348

Use this when the user wants a Four Pillars birth chart and has explicitly supplied the birth date, local time, latitude, longitude, and historical UTC offset. Applies True Solar Time correction. Do not use this to infer missing birth details, daylight-saving rules, or personalized guidance for a reading date. Use only with the subject’s permission. / 當使用者要建立四柱八字命盤，並已明確提供出生日期、當地時間、緯度、經度與當時 UTC 時差時使用；計算會校正真太陽時。請勿用來推測缺少的出生資料、夏令時間規則，或指定日期的個人化指引。僅在獲得當事人同意時使用出生資料。

NameTypeReqDescription
birth_datestringyesBirth date in YYYY-MM-DD format / YYYY-MM-DD 格式的出生日期
birth_timestringyesLocal birth time in 24-hour HH:mm format / 24 小時制的出生時間 HH:mm
latitudenumberyesBirth latitude in decimal degrees / 出生地緯度（十進位度數）
localestring–Response display preference; structured technical values include both languages / 回應語言偏好；結構化術語同時包含中英文
longitudenumberyesBirth longitude in decimal degrees; used for True Solar Time / 出生地經度，用於真太陽時校正
timezonenumberyesUTC offset in hours at the birth location and date / 出生地與出生日期的 UTC 小時時差
NameTypeReqDescription
canonical_urlstringyes–
dataobjectyes–
deterministicbooleanyes–
disclaimerobjectyes–
generated_atstringyes–
localestringyes–
schema_versionstringyes–
toolstringyes–

No examples provided.

get_daily_almanac ~202

Use this when the user asks for Chinese almanac information for a specific calendar date without personal birth data. Returns the day pillar, lunar date, activities, directions, and zodiac clash. Do not use this for a personalized Bazi chart or daily Bazi guidance. No generative AI is used. / 當使用者詢問特定日期的黃曆資料、且不涉及個人出生資料時使用。回傳日柱、農曆、宜忌、吉神方位與生肖相沖。個人八字命盤或八字每日指引請勿使用此工具。本工具不使用生成式 AI。

NameTypeReqDescription
datestringyesCalendar date in YYYY-MM-DD format / YYYY-MM-DD 格式的日期
localestring–Response display preference; structured technical values include both languages / 回應語言偏好；結構化術語同時包含中英文
NameTypeReqDescription
canonical_urlstringyes–
dataobjectyes–
deterministicbooleanyes–
disclaimerobjectyes–
generated_atstringyes–
localestringyes–
schema_versionstringyes–
toolstringyes–

No examples provided.

get_daily_bazi_guidance ~357

Use this when the user wants personalized daily Bazi interactions for a specific reading date and has supplied the complete birth inputs. Returns the chart and daily guidance. Do not use this for a date-only almanac request or when any birth input is missing. No generative AI is used. Use only with the subject’s permission. / 當使用者要查看指定日期的個人化八字互動，且已提供完整出生資料時使用；回傳命盤與每日指引。僅詢問日期黃曆或缺少任何出生資料時請勿使用。本工具不使用生成式 AI。僅在獲得當事人同意時使用出生資料。

NameTypeReqDescription
birth_datestringyesBirth date in YYYY-MM-DD format / YYYY-MM-DD 格式的出生日期
birth_timestringyesLocal birth time in 24-hour HH:mm format / 24 小時制的出生時間 HH:mm
latitudenumberyesBirth latitude in decimal degrees / 出生地緯度（十進位度數）
localestring–Response display preference; structured technical values include both languages / 回應語言偏好；結構化術語同時包含中英文
longitudenumberyesBirth longitude in decimal degrees; used for True Solar Time / 出生地經度，用於真太陽時校正
reading_datestringyesDate to interpret in YYYY-MM-DD format / YYYY-MM-DD 格式的解讀日期
timezonenumberyesUTC offset in hours at the birth location and date / 出生地與出生日期的 UTC 小時時差
NameTypeReqDescription
canonical_urlstringyes–
dataobjectyes–
deterministicbooleanyes–
disclaimerobjectyes–
generated_atstringyes–
localestringyes–
schema_versionstringyes–
toolstringyes–

No examples provided.

Common questions

What is the D8ly Read MCP server?

D8ly Read is an MCP server listed in the public MCP registry as io.github.dhsiao510/d8ly-read. Read-only Bazi, True Solar Time, and Chinese almanac tools in English and Traditional Chinese. This page covers its hosted endpoint (https://d8ly.app/mcp?source=mcp_registry).

Is the D8ly Read MCP server safe to use?

D8ly Read scores 81 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 D8ly Read MCP server expose?

D8ly Read exposes 3 tools: get_daily_almanac, calculate_bazi_chart, get_daily_bazi_guidance. Their descriptions and schemas cost roughly 907 tokens of context every time the server is loaded.

Does the D8ly Read MCP server require authentication?

No. We connected to D8ly Read without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the D8ly Read MCP server still maintained?

D8ly Read is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.