D8ly Read
REMOTE · D8LY.APP
Read-only Bazi, True Solar Time, and Chinese almanac tools in English and Traditional Chinese.
Available components
Last scanned (11 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 7 Nov 2026.
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 10 Oct 26 +5
- Stability: fail → pass ▲ security
- 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
- 8 Sept 26 0
- 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
- 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
- 24 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Aug 26 0
First indexed and scored.
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 7 Nov 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 | 22 Sept 2026 | 21 Dec 2026 | RSA 2048 | SHA256-RSA | 5281b467281f3ca4f9d8e96ad253e5a8416 |
| SANs: 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. | DS published | 23684 | 8 | Verified |
| d8ly.app. | No DS | 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 |
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 →
calculate_bazi_chart 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 時差時使用；計算會校正真太陽時。請勿用來推測缺少的出生資料、夏令時間規則，或指定日期的個人化指引。僅在獲得當事人同意時使用出生資料。
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | yes | Birth date in YYYY-MM-DD format / YYYY-MM-DD 格式的出生日期 |
| birth_time | string | yes | Local birth time in 24-hour HH:mm format / 24 小時制的出生時間 HH:mm |
| latitude | number | yes | Birth latitude in decimal degrees / 出生地緯度（十進位度數） |
| locale | string | – | Response display preference; structured technical values include both languages / 回應語言偏好；結構化術語同時包含中英文 |
| longitude | number | yes | Birth longitude in decimal degrees; used for True Solar Time / 出生地經度，用於真太陽時校正 |
| timezone | number | yes | UTC offset in hours at the birth location and date / 出生地與出生日期的 UTC 小時時差 |
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_url | string | yes | – |
| data | object | yes | – |
| deterministic | boolean | yes | – |
| disclaimer | object | yes | – |
| generated_at | string | yes | – |
| locale | string | yes | – |
| schema_version | string | yes | – |
| tool | string | yes | – |
No examples provided.
get_daily_almanac Daily Chinese 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。
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Calendar date in YYYY-MM-DD format / YYYY-MM-DD 格式的日期 |
| locale | string | – | Response display preference; structured technical values include both languages / 回應語言偏好；結構化術語同時包含中英文 |
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_url | string | yes | – |
| data | object | yes | – |
| deterministic | boolean | yes | – |
| disclaimer | object | yes | – |
| generated_at | string | yes | – |
| locale | string | yes | – |
| schema_version | string | yes | – |
| tool | string | yes | – |
No examples provided.
get_daily_bazi_guidance 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。僅在獲得當事人同意時使用出生資料。
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | yes | Birth date in YYYY-MM-DD format / YYYY-MM-DD 格式的出生日期 |
| birth_time | string | yes | Local birth time in 24-hour HH:mm format / 24 小時制的出生時間 HH:mm |
| latitude | number | yes | Birth latitude in decimal degrees / 出生地緯度（十進位度數） |
| locale | string | – | Response display preference; structured technical values include both languages / 回應語言偏好；結構化術語同時包含中英文 |
| longitude | number | yes | Birth longitude in decimal degrees; used for True Solar Time / 出生地經度，用於真太陽時校正 |
| reading_date | string | yes | Date to interpret in YYYY-MM-DD format / YYYY-MM-DD 格式的解讀日期 |
| timezone | number | yes | UTC offset in hours at the birth location and date / 出生地與出生日期的 UTC 小時時差 |
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_url | string | yes | – |
| data | object | yes | – |
| deterministic | boolean | yes | – |
| disclaimer | object | yes | – |
| generated_at | string | yes | – |
| locale | string | yes | – |
| schema_version | string | yes | – |
| tool | string | yes | – |
No examples provided.
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
claude mcp add --transport http dhsiao510-d8ly-read 'https://d8ly.app/mcp?source=mcp_registry'
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 86 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 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the D8ly Read MCP server?
VerifyMCP ran 13 checks on D8ly Read, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.