# Why a public MCP daily card can differ from your browser card Check the date, time zone and scope of two Wenbu daily cards. Find the record you want to keep for a journal entry or a later conversation. Updated: 2026-11-13 · Wenbu AI-assisted editorial Wenbu’s get_daily_card tool returns a public daily card for the specified time zone. The website keeps a personal daily card for the browser or account identity and its local date. Compare the date and time zone first, then check the scope. Two cards can differ on the same date in the same zone. To revisit a personal note, use the original website card and the note you saved with it. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) - Start with the date and time zone on each record. - Label the MCP result as public and the website record as browser or account scoped. - Continue with the original record for the exercise you want to discuss. ## Compare the two records in three steps 1. **Match the date** — Read the saved website date and the MCP clock.date and clock.timezone. 2. **Name the scope** — Label the MCP result public. Label the website record browser or account. 3. **Pick the record for the task** — Use the saved website result for a personal review and the public result for an integration exercise. Establish the local day and source of each card before continuing with one of them. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ## Find out which calendar date each result used The website shows a local date above the revealed card. When you look up an older result, copy the date from that record and check the daily time zone in its export if available. Travel or a browser on another device can change the local date used for today’s card. Keep the date you originally saved and make a separate note for the date you see now. When you use MCP, you can pass an IANA time zone such as Asia/Shanghai. The tool defaults to UTC when the parameter is omitted. Read clock.date and clock.timezone in the response. Compare those values with the website record before you compare card names. If you lack the original time zone, keep it unknown until an export or a contemporaneous note establishes it. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ## Check the scope when both dates already match Look at scope in the structured MCP response. Public means the tool returned the public exercise for that date. The call has no need for a personal journal or browser identifier. The website reveals a card in the context of your current browser or account. One identity keeps its website card for that local date, and a saved personal record stays associated with that context. Give date, zone, scope and card name separate fields. Two records with the same date and zone describe the same local day, while scope tells you which kind of record each one is. If the names differ, keep both labels and both sources. If the names match, the scope still tells you where to find the corresponding note later. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ## Decide which card to take into a follow-up If your goal is to revisit what you wrote this morning, open that website journal entry or its original export. On the daily page, Talk about this card carries the selected card and your note to the conversation. You can also use Export card to keep a copy. Check the date and card name before using that result as the basis of a follow-up. If you are checking a tool integration, keep the original public response with its scope. Use its prompt in your integration example or save it in a test note. Decide whether the next task concerns the public prompt or your own observation. Then provide the chosen card and the part of the record needed to answer that task. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ## Recover a follow-up that mixed the two cards Suppose your website note in the morning said you would walk after work. In the afternoon you pasted a public card into an integration note. Later, an assistant quotes the public card when you ask it to review the morning exercise. Open the two original records and see which one contains the walk. Give the assistant that card, date and original note in one follow-up. If the walk is all you have, keep the plan and mark the card name unknown. Fill it in once you find the original export or journal. A traceable reply identifies the record it used and adds what actually happened to that entry. Even if the cards have the same name, the saved location and the original note let you check which one the reply followed. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ## A check for two daily card records | What you see | What to check | What to keep | | --- | --- | --- | | Opened at similar times, different dates | Each time zone and its local calendar date | Both original dates and zones | | Same date and zone, different cards | Public MCP scope and the personal website scope | The card name from each source | | Same date, zone and card name | The scope of each record | Both source labels | | You want to revisit the morning website exercise | Original saved card and note | The existing personal record | [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ## Choose between two fixed practice records These fictional entries use a fixed local setup and Asia/Shanghai on November 13, 2026. Both card names come from the same local test setup and serve only to demonstrate the two scopes. 1. The public example returns scope public, date 2026-11-13 and Two of Wands. Save that row as Public daily card. 2. The website example shows The Hanged Man on the same date and in the same time zone. Record it separately and add one personal observation. 3. Compare the rows. Circle the different scopes and card names even though the dates and time zones match. 4. To revisit the personal observation, use the website row with The Hanged Man. Carry the original card and note from the daily page or its export. You can use both records and still trace each card to its source. The personal follow-up continues with the card and note you originally saved. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ## FAQ ### Does a different card mean a time zone is wrong? Compare the two dates and zones first. If those match, check the scope. Public and personal website cards are selected within separate scopes and can differ on the same day. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ### Can I combine the records if the names happen to match? You can use the same card name in both rows. For a later review, retain each source and its original notes so you can find the record you actually used. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ### Where do I continue the website card from this morning? Open the saved personal card or the original export. On the website, Talk about this card brings the card and note into a conversation. Sending a message starts the turn. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ## Glossary - **Public daily card**: The daily practice returned by MCP using the server calendar in the requested time zone. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) - **Personal website card**: The daily card retained within a browser or account context, with any optional note you save. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) - **Daily card date**: The local calendar date used for the daily card. Keep its time zone with it. [Wenbu · daily card](https://wenbu.app/daily/) · [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) · [Wenbu · agent integrations](https://wenbu.app/agents/) ## Evidence notes - The website retains the same daily card for one identity on one local date. — “同一身份在同一个日期会保留同一张牌” (fact); [Wenbu · daily card](https://wenbu.app/daily/) - The public capabilities document specifies the scope of the MCP daily prompt. — “Public daily prompt” (fact); [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) - Wenbu’s integration guide says the public card can differ from the personal website card. — “可能与个人网页日签不同” (fact); [Wenbu · agent integrations](https://wenbu.app/agents/) ## Sources - [Wenbu · daily card](https://wenbu.app/daily/) — Current first-party product UI; not a personal forecast; fetched 2026-11-13T07:03:04.564Z; complete response - [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) — First-party current tool, convention and privacy contract; not external endorsement or predictive validation; fetched 2026-11-13T07:03:04.563Z; complete response - [Wenbu · agent protocol](https://wenbu.app/agent-protocol.md) — Current first-party tool, citation recovery and completion protocol; fetched 2026-11-13T07:03:04.556Z; complete response - [Wenbu · agent integrations](https://wenbu.app/agents/) — Current first-party product documentation; fetched 2026-11-13T07:03:04.567Z; complete response [Open the website daily card and record the date and name](https://wenbu.app/en/daily/)