d8ly-read
Registry code: 285e45b24bdd68ac
Use get_daily_almanac for date-only Chinese almanac questions. Use calculate_bazi_chart only when the user supplied birth date, local time, coordinates, and the historical UTC offset. Use get_daily_bazi_guidance when those birth inputs and a reading date are available. Never infer missing birth data or treat results as medical, legal, financial, or other professional advice.
- endpoint
- https://d8ly.app/mcp?source=mcp_registry
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is d8ly-read live?
- Yes — it answered the hub's last check (checked 38m ago). It answered 100% of checks over the last 30 days.
- Is d8ly-read free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does d8ly-read have?
- 3 tools: calculate_bazi_chart, get_daily_almanac, get_daily_bazi_guidance.
- Is d8ly-read safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 3 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- topic
- lifestyle & home
- used for
- get the chinese almanac for a date
- calculate a bazi birth chart
- get daily bazi guidance
- takes → gives
- data → data, text
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
calculate_bazi_chart reads unknown 5h ago
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 時差時使用;計算會校正真太陽時。請勿用來推測缺少的出生資料、夏令時間規則,或指定日期的個人化指引。僅在獲得當事人同意時使用出生資料。
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "birth_date", "birth_time", "latitude", "longitude", "timezone" ], "properties": { "locale": { "enum": [ "en", "zh" ], "type": "string", "default": "en", "description": "Response display preference; structured technical values include both languages / 回應語言偏好;結構化術語同時包含中英文" }, "latitude": { "type": "number", "maximum": 90, "minimum": -90, "description": "Birth latitude in decimal degrees / 出生地緯度(十進位度數)" }, "timezone": { "type": "number", "maximum": 14, "minimum": -12, "description": "UTC offset in hours at the birth location and date / 出生地與出生日期的 UTC 小時時差" }, "longitude": { "type": "number", "maximum": 180, "minimum": -180, "description": "Birth longitude in decimal degrees; used for True Solar Time / 出生地經度,用於真太陽時校正" }, "birth_date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Birth date in YYYY-MM-DD format / YYYY-MM-DD 格式的出生日期" }, "birth_time": { "type": "string", "pattern": "^(?:[01]\\d|2[0-3]):[0-5]\\d$", "description": "Local birth time in 24-hour HH:mm format / 24 小時制的出生時間 HH:mm" } } }arguments 50 linesget_daily_almanac reads unknown 5h ago
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。
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "date" ], "properties": { "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Calendar date in YYYY-MM-DD format / YYYY-MM-DD 格式的日期" }, "locale": { "enum": [ "en", "zh" ], "type": "string", "default": "en", "description": "Response display preference; structured technical values include both languages / 回應語言偏好;結構化術語同時包含中英文" } } }arguments 23 linesget_daily_bazi_guidance reads unknown 5h ago
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。僅在獲得當事人同意時使用出生資料。
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "birth_date", "birth_time", "latitude", "longitude", "timezone", "reading_date" ], "properties": { "locale": { "enum": [ "en", "zh" ], "type": "string", "default": "en", "description": "Response display preference; structured technical values include both languages / 回應語言偏好;結構化術語同時包含中英文" }, "latitude": { "type": "number", "maximum": 90, "minimum": -90, "description": "Birth latitude in decimal degrees / 出生地緯度(十進位度數)" }, "timezone": { "type": "number", "maximum": 14, "minimum": -12, "description": "UTC offset in hours at the birth location and date / 出生地與出生日期的 UTC 小時時差" }, "longitude": { "type": "number", "maximum": 180, "minimum": -180, "description": "Birth longitude in decimal degrees; used for True Solar Time / 出生地經度,用於真太陽時校正" }, "birth_date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Birth date in YYYY-MM-DD format / YYYY-MM-DD 格式的出生日期" }, "birth_time": { "type": "string", "pattern": "^(?:[01]\\d|2[0-3]):[0-5]\\d$", "description": "Local birth time in 24-hour HH:mm format / 24 小時制的出生時間 HH:mm" }, "reading_date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Date to interpret in YYYY-MM-DD format / YYYY-MM-DD 格式的解讀日期" } } }arguments 56 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id285e45b24bdd68ac.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/285e45b24bdd68ac/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/285e45b24bdd68ac?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.