{"id":"com.dayze/life-context","slug":"com-dayze-life-context","title":"Dayze — Life Context","description":"Life context for agents: get_context_pack + public notable packs. x402 + OAuth.","version":"1.28.0","publisher":{"kind":"domain","id":"dayze.com","label":"dayze.com","url":"https://dayze.com"},"website":"https://dayze.com","repository":"https://github.com/gohluke/dayze-mcp","remotes":[{"type":"streamable-http","url":"https://dayze.com/api/mcp"},{"type":"streamable-http","url":"https://dayze.com/api/mcp/key"}],"packages":[],"published":"2026-09-11","updated":"2026-09-11","status":"online","auth":"","latency_ms":992,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"search_tools","title":"Search MCP Tools","description":"Discover Dayze MCP tools outside the core default expert listing. Returns matching opt-in tools with their toolset and how to enable them (URL ?toolsets=, tools/list params, or tools.* connection scopes). Call with no query to list available toolsets. Core everyday tools are already listed; this does not replace tools/list. ($0.00)","read_only":true},{"name":"get_context_pack","title":"Life Context Pack","description":"Life Context pack for one Dayze account (`account` names it — with more than one Dayze connection, say which account you are answering from): identity, pulse, people, next actions, memories, quizzes, recent consented place visits, and traced facts. Use include_*=false to omit default sections; current location and money stay opt-in. Spec: https://dayze.com/docs/life-context Records carry inspect_u","read_only":true},{"name":"get_events","title":"Calendar Events","description":"Authenticated user's calendar events. Prefer explicit from/to (YYYY-MM-DD). Shortcuts: today|week|month|year (calendar year)|decade. Browsing noise excluded by default. Records carry inspect_url (their Dayze page): cite with it, never build a link from an id; a record without one has no page (inspect_note says which). ($0.10; API key required)","read_only":true},{"name":"get_people","title":"Dayze Contacts","description":"List or search the authenticated user's Dayze Contacts (private CRM; table people). query matches literal substrings of name, slug, email, occupation or context tags (no fuzzy fallback). context_tags requires all exact tags; occupation requires a substring. These filters combine with query and search the full owned contact set before pagination. Set wealth_category=reviewed for only explicitly own","read_only":true},{"name":"update_person","title":"Update Contact (CRM write)","description":"Edit one owned contact. Omit to keep; lists replace. Read before adding. request_id retries safely; change_id supports undo. ($0.10; API key required)","read_only":false},{"name":"log_food","title":"Log Food (diary write)","description":"MUTATES the authenticated user Food Diary and calendar. Use when they ate or drank — do not store this as a chat memory. Supports dish_items for multiple named dishes with optional price and rating. Example: “I had Mee Pok for late lunch with my parents” → log_food({ what: \"Mee Pok\", kind: \"meal\", meal_period: \"late lunch\", with: [\"my parents\"] }). Optional: calories (user-stated kilocalories), pl","read_only":false},{"name":"update_food","title":"Update Food (diary patch)","description":"MUTATES one owned Food Diary row by food_id. Same fields as log_food; omitted stay. dish_items replaces the full dish list. A dish/notes correction never creates another Finance row. expense_id null unlinks. Unknown/other-user food_id or expense_id errors and changes nothing. Share tokens cannot write. ($0.10; API key required)","read_only":false},{"name":"log_event","title":"Log Event (calendar write)","description":"MUTATES the calendar (non-food events, tasks, sleep). Replies owed ('what to reply to X') go to create_pending_reply. Woke at X: end_time. Requires title+date. No-date task: use create_todo with no date, never log_event with today. Goal steps: create_todo; schedule_todo only when told when. Soft dates keep date_precision. Past story: log_moment (+event_id), not a 2nd event. Wake-only sleep: catego","read_only":false},{"name":"update_event","title":"Update Event (calendar patch)","description":"MUTATES one existing calendar event the authenticated user owns. Required: event_id (UUID). Optional patch (same fields as log_event): title, date / event_date, time / event_time, end_date, end_time, location, description (alias notes), category, external_url, image_url, timezone, visibility, people / with / person_ids, scoreboard (merged; null clears), reminder_enabled (false turns the push remin","read_only":false},{"name":"log_moment","title":"Log Moment (story or memory)","description":"Save a past story or memory as a private moment. Plans go to log_event; a touchpoint with a contact to log_interaction. Requires title, and moment_date (YYYY-MM-DD, YYYY-MM or YYYY; alias date) unless event_id is given. With event_id (an owned event the story is about) it creates a NEW moment linked to that event and takes the event's date and location when you pass none; the event itself is never","read_only":false},{"name":"update_moment","title":"Update Moment (patch a story)","description":"Patch one owned moment by moment_id (from log_moment); fields left out are untouched. It stays private. Requires moment_id. Patchable: title, description, moment_date, moment_date_precision, end_date, moment_type, location_name, people, event_id, images, tags. Unknown or other-user moment_id returns an error and creates nothing. person_ids / people_names, media_urls and tags replace the stored lis","read_only":false},{"name":"create_pending_reply","title":"Create Pending Reply","description":"Pending Replies (Inbox): save a reply the user owes someone, e.g. 'what to reply to X', 'I owe X a reply'. Use this, not log_event or a task. Optional draft (the reply text), summary (one line in your own words; never the email body, subject or sender), channel, category, received_at, and source { kind, thread_id, message_id } (ids only). Links the contact only when resolve_person finds exactly on","read_only":false},{"name":"get_pending_replies","title":"Get Pending Replies","description":"Pending Replies (Inbox): the replies the user owes ('who do I owe a reply?'), newest first, or one by reply_id. status: unsent (default; pending + snoozed), sent, dismissed, all. Filter by person_name or person_id. Each reply has reply_id, person_name, person_id (null when unlinked), draft, summary, channel, category, source ids, status, state (unsent | sent | dismissed) and due (owed now; false w","read_only":true},{"name":"update_pending_reply","title":"Update Pending Reply","description":"Pending Replies: change one reply by reply_id: its draft (replaces; null clears), summary, channel, category, received_at, person (person_id, or person_name linked only on one match), source, or status pending (reopen / unsnooze) or snoozed with snooze_until. Unknown or other-user reply_id returns not_found. To mark it sent or dismissed use resolve_pending_reply. Never sends anything. Requires API","read_only":false},{"name":"resolve_pending_reply","title":"Resolve Pending Reply","description":"Pending Replies: mark a reply done: sent (default; the user replied, logged privately in the contact's history) or dismissed. Dayze sends nothing. By reply_id, or person_name / person_id when that person has exactly one unsent reply (otherwise the candidates come back and nothing changes). Marking sent writes one private interaction for the linked contact (not for an unlinked reply, and not twice)","read_only":false},{"name":"log_interaction","title":"Log Interaction","description":"Contacts: log that the user was in touch with a contact ('I replied to Vadim', 'called Mum'): kind message, call, meeting, note, check_in or thought_of. Private to the owner. person_id (an owned contact) or person_name (linked only on one resolve_person match; otherwise nothing is logged and the candidates come back). With reply_id it also marks that Pending Reply sent: this interaction is the rep","read_only":false},{"name":"get_memories","title":"Agent Memories","description":"Authenticated user memories from Dayze Agent. Pass query for semantic/keyword retrieval. Prefer search for event-first trip and calendar titles. Requires OAuth or a supported scoped credential. ($0.10; API key required)","read_only":true},{"name":"get_expenses","title":"Expense Summary","description":"Cashflow totals at Finance FX. Use period all for all-time requests, never year. Requires OAuth or scoped credentials. ($0.10; API key required)","read_only":true},{"name":"resolve_person","title":"Resolve Contact","description":"Resolve a nickname or surface name to a Dayze Contacts row via person_aliases → exact name → slug → unique substring. Returns avatar_url, photo_count, has_photos, and photos[{url,is_primary}] preview; use get_person_photos for full gallery. With financial_details:read, net_worth_assessment has the same sourced fields as the Contacts card; context-only evidence carries no personal number. Notes omi","read_only":true},{"name":"get_interactions","title":"Life Update Interactions","description":"Bounded graph read over life_updates (PHI-54/61): traverse interaction → person/event/expense/place with source/confidence on every hop. When life_update edges are missing, projects hops from CRM interactions, event_people, and expense person FKs (PHI-100). Prefer for “who was I with at X?”, “when am I meeting Y next?”, “how much at Z?”. 93-day default window. Pass person_name, place_query, or ids","read_only":true},{"name":"get_trackers","title":"Habit Trackers","description":"Authenticated user live trackers only; expired countdowns and inactive streaks are omitted. Sobriety/streak trackers remain visible at day 0 after a reset. Merges event-backed trackers with the trackers table when present. current_value is read from the tracker's events: days for sobriety/streak, days left for a countdown, the total for a counter (value_unit), with last_event_date. Returns up to `","read_only":true},{"name":"reset_tracker","title":"Reset Streak Tracker","description":"Preview first, 30-day undo. Resets a sobriety/streak tracker for the authenticated user (sets current value to 0 and restarts the clock). Prefer tracker_id from get_trackers, or tracker_title fuzzy match; optional reset_at (ISO) and note go in the preview arguments. Rebuilds life_state. Reviewed and reversible: first call preview_destructive_change({ tool: \"reset_tracker\", arguments: { tracker_id ","read_only":false},{"name":"search","title":"Semantic Life Search","description":"Search the authenticated user life graph. Optional from/to (aliases start/end) are inclusive account-local civil dates on every search route; either bound may be used alone. Dated semantic and keyword records use event date, expense date, goal start date, check-in date, or the account-local creation date of contacts and memories. Deterministic routing first: food or relative dates (e.g. \"what did ","read_only":true},{"name":"get_goals","title":"Get Goals","description":"Read your owned life goals and progress. goal_id selects one; status defaults active, all includes completed goals. Each goal carries a computed progress object: kind, percent, this period, change on the previous period, and pace (null without a target date or enough history; never estimate one). Not calendar events or streak trackers. ($0.01; API key required)","read_only":true},{"name":"create_goal","title":"Create Goal","description":"Create a life goal the user explicitly wants to track. Not a calendar event or streak tracker. Numeric goals are totals that build up and need target_value and target_unit; rate goals are a number per calendar month that can go down, such as monthly revenue, and need the same two fields; habit goals need habit_frequency and habit_target_count. Ask for missing facts; never invent aspirations. ($0.1","read_only":false},{"name":"update_goal","title":"Update Goal","description":"Patch one owned goal by goal_id from get_goals. Set current_value to absolute progress, not a delta. On a rate goal current_value is this month's number and replaces the last one. Omitted fields remain unchanged. Never select a goal by a guessed ID. request_id required. ($0.10; API key required)","read_only":false},{"name":"create_tracker","title":"Create Tracker","description":"Start a tracker for the user: title, tracker_type streak, sobriety, countdown or counter, start_date (default today), target_date for a countdown, target_days, emoji. Private. To reset one use reset_tracker. ($0.10; API key required)","read_only":false},{"name":"log_sleep","title":"Log Sleep","description":"Sleep: log overnight or nap. Cross-midnight OK (e.g. 14:00→03:00 = 13h / 780m). ($0.10; API key required)","read_only":false},{"name":"get_sleep","title":"Get Sleep","description":"Sleep: list typed sleep/nap records with duration_minutes. ($0.05; API key required)","read_only":true},{"name":"get_sleep_summary","title":"Sleep Summary","description":"Sleep: day/week/month totals and averages. ($0.05; API key required)","read_only":true},{"name":"update_sleep","title":"Update Sleep","description":"Sleep: patch an existing sleep record by sleep_id. ($0.10; API key required)","read_only":false},{"name":"create_person","title":"Create Contact","description":"Add a Dayze Contacts record, birthday included (YYYY-MM-DD, YYYY-MM, YYYY, or MM-DD if year unknown); checks duplicates first. An existing contact comes back unchanged with its person_id, not_applied (the fields you sent) and a hint. request_id is optional: without one, identical calls within 15 minutes return the first result. Advertised name create_person is stable; tools/call also accepts creat","read_only":false},{"name":"get_birthdays","title":"Get Birthdays","description":"Whose birthday is coming up or was just missed: the user's contacts with a birthday in a window (days_back before and days_ahead after today, 30 each, or from/to), in the account timezone. upcoming (days_until) and recent (days_since), soonest first then closest: birthday_on, age_turning (null when the year is unknown), birthday_precision, relationship, tier, is_favorite, last_in_touch, in_touch_s","read_only":true},{"name":"upload_photo","title":"Upload Photo","description":"Upload a photo to a Life Graph entity you have (event, expense, place, person, inventory, …). Accepts image_base64, url, or ChatGPT file object `image` ({download_url, file_id}). Normally re-encodes as WebP; original_preserved and metadata_stripped describe the saved bytes. Partial results include an asset_id for repair: call upload_photo with asset_id and a new request_id, without image bytes. An","read_only":false},{"name":"log_expense","title":"Log Expense","description":"Create an outgoing expense only. For money received (Venmo/Cash App/PayPal/Zelle) use log_transaction with direction=from and type=income. Lending a contact cash: category \"IOU lend\" + person_id (one call creates the IOU they owe and shows the money out once). ($0.10; API key required)","read_only":false},{"name":"log_transaction","title":"Log Transaction","description":"Income/expense/transfer. from+income = received. IOU repayment/lend need category + person_id (direction from/to). Invoice: iou_type invoice. Open-IOU income needs not_iou_repayment=true. Unknown person_id errors; changes nothing. ($0.10; API key required)","read_only":false},{"name":"log_income","title":"Log Income","description":"Record money received (Stripe, refunds, payroll, Venmo). log_transaction with type income and direction from already set (pass neither). Use external_id for Stripe/Gmail idempotency. A contact paying back an IOU: category \"IOU repayment\" + person_id (lowers the IOU, shows the money once). A contact lending the user cash: category \"IOU lend\" + person_id (creates the IOU the user owes, shows the mon","read_only":false},{"name":"get_person_photos","title":"Person Photos","description":"Read a contact avatar and gallery as inline MCP images with per-asset render status. Avatar comes first. Use offset to page through photos (up to six per call); never paste raw image URLs into chat. ($0.10; API key required)","read_only":true},{"name":"get_moments","title":"Get Moments","description":"List owned Moments by date, title, type, tag, person or place. Stable moment_id and inspect_url for each. ($0.05; API key required)","read_only":true},{"name":"search_moments","title":"Search Moments","description":"Search only owned Moment stories and titles within an optional date range. Returns stable moment_ids. ($0.05; API key required)","read_only":true},{"name":"get_timeline","title":"Get Timeline","description":"The user's days in one read: calendar events, Moments (lived stories) and Food Diary entries for a civil date range in the account timezone (max 92 days; default today). A food entry's calendar mirror is listed once, under food. Text the connection may not see is redacted as in get_events. Each record keeps its id and inspect_url where it has a page. ($0.05; API key required)","read_only":true},{"name":"get_today","title":"Get Today","description":"Today in the user's timezone: local date and time, today's events, Moments and Food Diary entries, and today's money totals by category. Use first when an agent needs the user's current day. ($0.05; API key required)","read_only":true}],"server_info":{"name":"dayze","version":"1.77.4","title":"Dayze"},"category":"cloud","tags":["agents","crypto","web-search"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-09-11","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/com-dayze-life-context/"}