mcpbeat Sign in

Dayze — Life Context MCP Server

answering

Dayze — Life Context is answering right now. Last checked 4 min ago. It exposes 130 tools. Last commit 18 Sep 2026.

Life context for agents: get_context_pack + public notable packs. x402 + OAuth.

Uptime history 51 days of history · worst day 99%
51 days agonow
99.5%
Uptime 24h
181 of 182 checks
130
Tools
read from the server
786 ms
Response time
average over 24h
0
Stars
last commit 18 Sep 2026

What changed 369

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 August 2026. No other catalogue keeps this.

21 Sep a tool description was rewritten get_interactions
19 Sep a tool appeared get_interactions
17 Sep 3 tools changed the parameters they ask for cleanup_preview, normalize_people_preview, update_event
17 Sep a tool changed version2 times that day
16 Sep 10 tools changed the parameters they ask for delete_event, get_events, get_people and 7 more
16 Sep 9 tool descriptions were rewritten create_person, delete_event, get_people and 6 more
16 Sep 9 tools appeared archive_event, archive_expense, archive_trip and 6 more
16 Sep a tool changed version4 times that day
14 Sep 18 tools appeared add_person_alias, audit_people, classify_contact and 15 more
14 Sep 2 tools changed the parameters they ask for get_context_pack, update_person
and 314 more, back to 17 August 2026

Dayze — Life Context missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add life-context --transport http https://dayze.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "life-context": {
      "url": "https://dayze.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.life-context]
url = "https://dayze.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "life-context": {
      "url": "https://dayze.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "life-context": {
      "url": "https://dayze.com/api/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 130

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

person
add_person_alias
Add a nickname/payment handle/misspelling alias for one CRM person. ($0.05; API key required)
create_person
Add a Dayze Contacts record; checks duplicates first. Advertised name create_person is stable; tools/call also accepts create_contact. ($0.10; API key required)
get_person_aliases
List canonical aliases (nicknames) for a CRM person. Pass person_id or name (resolved via aliases). Requires OAuth or a supported scoped credential. ($0.05; API key required)
get_person_connections
List graph edges for one CRM person. ($0.05; API key required)
get_person_interactions
Relationship timeline for one CRM person: interactions rows (message/call/meeting/note + extended kinds like visit/gift/stayed_over encoded in summary) plus co-tagged calendar events. Prefer this over dumping people.notes for “when did I last see X?”. Pass person_id or name. ($0.10; API key required)
get_person_neighborhood
Subgraph around one user-owned person_id — profile (avatar_url, photo_count, has_photos) plus declared connections. Use get_person_photos for the full gallery. Notes omitted unless include_notes=true (redacted). Requires OAuth or a supported scoped credential. ($0.15; API key required)
get_person_photos
Gallery image URLs for a CRM contact. Returns photos[{ id, url, is_primary, created_at }] plus inline MCP image attachments for chat render. Accepts person_id. ($0.10; API key required)
get_person_transactions
Me↔contact money ledger from expenses (paid_to_person_id / income_from_person_id). Pass person_id or name. Returns entries + per-currency totals. Reuses existing expenses — no parallel ledger table. ($0.10; API key required)
remove_person_alias
Remove one alias from a CRM person. ($0.05; API key required)
update_person
MUTATES Dayze Contacts. Patch one existing contact the user owns (person_id UUID required). Optional fields: name (renames + refreshes slug), is_favorite, tier (vip|normal|low), relationship, notes (replaces stored notes — read first if you need to append), birthday (YYYY|YYYY-MM|YYYY-MM-DD|MM-DD|--MM-DD or null to clear; MM-DD stores month_day precision). Rejects unknown fields. Does not create or delete contacts. Rebuilds life_state so the next get_context_pack inner_circle is fresh. Advertised name update_person is stable; tools/call also accepts update_contact. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
update_person_alias
Update alias_kind/source/display for an existing alias. ($0.05; API key required)
update_person_identity
Patch identity fields (legal/preferred name, pronouns, social handles, user_relationships[]). Never infer sensitive identity from appearance. Confirmed user_relationships are preserved unless force=true. ($0.10; API key required)
log
log_event
MUTATES the authenticated user calendar. Use for non-food days — funeral, cremation, appointment, dinner, anything that is not a food log. Do not store this as a chat memory. Example (funeral tonight): log_event({ title: "Funeral service — Mr Goh Choo Taw", date: "2026-08-29", time: "8pm", location: "Multi Purpose Hall, Blk 661 Jurong West St 64", category: "funeral" }). Example (Sunday cremation): log_event({ title: "Cremation — Mr Goh Choo Taw", date: "2026-08-30", location: "Mandai Crematorium", category: "funeral" }). Required: title + event_date (YYYY-MM-DD, YYYY-MM, or YYYY; alias date). Soft dates expand to first-of-period and set metadata.date_precision (day|month|year|approx). Optional: event_time (8pm or 20:00; alias time), end_date, end_time, location / city+country, description, category, external_url, visibility (private|friends|public), image_url, timezone, date_precision, share_with (Dayze handles e.g. ["boof"]), people / with / person_ids, idempotency_key (recommended; retries reuse the first write). For trips/residences prefer log_travel({ city, country, start_date, kind }). Unknown people names do not fail the write. Public events return share_url (/e/{id}) for Explore + social. Inserts public.events, optional event_people / shared_events, then rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
log_expense
Create an outgoing expense only. For money received (Venmo/Cash App/PayPal/Zelle) use log_transaction with direction=from and type=income. ($0.10; API key required)
log_favorite_song
MUTATES the authenticated user favorite tracks list at /music. Use when they favorite or save a song — do not store this as a chat memory or in music_preferences. Example: “Henry Mancini - Piano And Strings (1995 Remastered)” → log_favorite_song({ track: "Henry Mancini - Piano And Strings (1995 Remastered)" }) or title + artist. Optional year_note, source_url. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
log_food
MUTATES the authenticated user Food Diary and calendar. Use when they ate or drank — do not store this as a chat memory. 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: place/merchant, amount, consumed_at (ISO). Resolves with/Mum/Dad via person aliases; unknown names do not fail the food write. Tags companions on the mirrored event. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
log_income
Record money received (Stripe, refunds, payroll, Venmo). Alias of log_transaction with type=income and direction=from. Use external_id for Stripe/Gmail idempotency. ($0.10; API key required)
log_place_visit
MUTATES place_visits for map/history digs (Uber dropoff, address evidence). Required: place (or place_id) + arrived_at/date. Optional: departed_at, source (uber|mcp|…), evidence_expense_id (idempotent), city/country/address. Prefer this over stuffing streets only into expenses. ($0.10; API key required)
log_sleep
Sleep: log overnight or nap. Cross-midnight OK (e.g. 14:00→03:00 = 13h / 780m). ($0.10; API key required)
log_transaction
Income/expense/transfer write. direction=from + type=income for Venmo/Stripe/refunds received. Positive amount; external_id dedupes imports. Optional project/tags. Zelle always USD. Optional mirror_event creates a calendar Money · annotation (ledger is still the source of truth for /money). ($0.10; API key required)
log_travel
MUTATES trips (+ optional calendar travel event). Prefer this over free-text log_event for map/history. Required: city + start_date. Optional: country, end_date, kind (trip|residence|soft_pin), confidence (confirmed|likely|possible), evidence, title, mirror_event. Soft pins default to status=possible and stay off cities/map until confidence=confirmed. Zelle/Venmo money belongs in log_transaction — not here. ($0.10; API key required)
inventory
add_inventory_item
Add an owned object to Life Inventory. ($0.10; API key required)
add_inventory_valuation
Append immutable valuation observation. ($0.10; API key required)
get_inventory
Browse owned inventory with filters. ($0.10; API key required)
get_inventory_item
Full item with valuations, people links, assets. ($0.10; API key required)
get_inventory_valuations
Chronological valuation history for an item. ($0.10; API key required)
search_inventory
Search owned inventory by name/brand/model/notes. Returns photo_count, has_photos, cover_url; when empty, photo_hint explains upload_asset linkage. ($0.10; API key required)
update_inventory_item
PATCH semantics — unspecified fields untouched. ($0.10; API key required)
archive
archive_asset
Soft-delete an asset (sets archived_at). Original rows are preserved for versioning. ($0.05; API key required)
archive_event
Reversibly archive one owned event; preserve linked data and return restore_id. Use a new request_id for each intended action. ($0; API key required)
archive_expense
Reversibly archive one owned expense; preserve linked data and return restore_id. Use a new request_id for each intended action. ($0; API key required)
archive_inventory_item
Archive instead of destructive delete. ($0.10; API key required)
archive_trip
Reversibly archive one owned trip; preserve linked data and return restore_id. Use a new request_id for each intended action. ($0; API key required)
notable
notable_pack
DEFAULT for who is X: profile + life_in_days (age/day_number) + similar people + birthday peers. Timeline events include day_number. Prefer this over notable_profile. Example: albert-einstein. ($0.05)
notable_pack_premium
S-tier guaranteed pack (score≥85, timeline≥8, image, embedding). Errors if below bar. Use when you need high-quality, complete notable context. Example slug: elon-musk. ($0.10)
notable_profile
Bio-only profile JSON by slug (no life-in-days, similar, or birthday peers). Prefer notable_pack for “who is X / age in days / peers”. Example: taylor-swift. ($0.02)
notable_search
Search the public Dayze notable-people catalog by name, occupation, or slug. Use when you need to find a person before fetching a pack. Example slug: albert-einstein. ($0.01)
update_notable
MUTATES public notable_people. Superuser only. Patch by slug (bio, about, occupation, birth_place, birth_date, net_worth, residence, before_fame, trivia, family_life, zodiac, flag). Rejects unknown fields. No create/delete. Stamps last_updated_via=mcp. ($0.10; API key required)
gmail
list_gmail_accounts
List connected Gmail mailboxes for the authenticated user (id, email, is_default). Use account on search_gmail / read_gmail_* / import_*_gmail to pick a mailbox. Connect another inbox at /integrations (multi-mailbox after migration). Share tokens cannot call. ($0.05; API key required)
read_gmail_attachment
Download one Gmail attachment by message_id + attachment_id (from read_gmail_message.attachments). Returns utf-8 text for text/csv/vcf/vcard; binary types return filename/mime/size + a note (no base64 dump). Optional account. Read-only. Share tokens cannot call. ($0.10; API key required)
read_gmail_message
Read one Gmail message by id from search_gmail. Returns subject, from, date, snippet, plain-text body (truncated), and attachments[] metadata (attachment_id, filename, mime_type, size). Use read_gmail_attachment for text/csv/vcf contents. Optional account when multiple mailboxes. Read-only. Share tokens cannot call. ($0.10; API key required)
search_gmail
Search one of the authenticated user's connected Gmail inboxes (read-only). Reuses Integrations hub Gmail (service_connections provider=gmail). Optional account/email selects a mailbox when multiple are connected — call list_gmail_accounts first. Prefer Gmail operators: from:, subject:, is:unread, newer_than:7d, has:attachment. Returns id, subject, from, date, snippet only (no body). Follow up with read_gmail_message. Cannot send, archive, or delete. Never invent email contents. If Gmail is not connected, connect at /integrations. Requires API key or OAuth with scope context. Share tokens cannot call this tool. ($0.10; API key required)
people
get_people
List the authenticated user's Dayze Contacts (private CRM; table people). Each contact includes avatar_url, photo_count, and has_photos; use get_person_photos(person_id) for the full gallery. Notes omitted by default (has_notes flag); pass include_notes=true for progressive fetch (credential/secret spans are redacted server-side). Supports limit (default 100, max 500) and offset; returns total and truncated. Distinct from public notable People at /people. Advertised name get_people is stable; tools/call also accepts get_contacts / list_contacts. Requires OAuth or a supported scoped credential. ($0.10; API key required)
get_people_cleanup_result
Fetch start_people_cleanup result by cleanup_id. ($0.05; API key required)
get_people_links
Alias of get_person_connections — list graph edges for one CRM person. ($0.05; API key required)
update_people_link
Patch an existing person↔person graph edge (type/context/source/confidence). ($0.10; API key required)
place
create_place
Save a venue card (business_contacts): address, opening_hours, affordability ($/$$/$$$), notes, tags. Idempotent by name or idempotency_key — does not create calendar notes. ($0.10; API key required)
get_place
Fetch one saved place card (business_contacts) by place_id — address, opening hours, affordability, notes. ($0.05; API key required)
get_place_visits
When was I at a venue — merges place_visits, location_visits, and event locations. ($0.10; API key required)
update_place
Patch a saved place card by place_id / business_contact_id. Unspecified fields stay unchanged (hours, affordability, address, notes, …). ($0.10; API key required)
restore
restore_cleanup
Restore an archive or normalization receipt. Requires restore_id and request_id. Refuses intervening edits; repeats are no-ops. ($0; API key required)
restore_event
Restore an archive or normalization receipt. Requires restore_id and request_id. Refuses intervening edits; repeats are no-ops. ($0; API key required)
restore_expense
Restore an archive or normalization receipt. Requires restore_id and request_id. Refuses intervening edits; repeats are no-ops. ($0; API key required)
restore_trip
Restore an archive or normalization receipt. Requires restore_id and request_id. Refuses intervening edits; repeats are no-ops. ($0; API key required)
link
link_entities
Link Trip→Stay→Place / Event→Person (graph, not prose). ($0.10; API key required)
link_inventory_person
Provenance link e.g. inherited_from, gifted_by. ($0.10; API key required)
link_people
NON-DESTRUCTIVE: create/update a person_connections edge between two distinct people (friends/family/knows/…). Both contacts remain. Do not use for duplicate cleanup — use merge_people. ($0.10; API key required)
photos
get_photos_for_event
Assets linked to an event. ($0.10; API key required)
get_photos_for_place
Assets linked to a canonical place. ($0.10; API key required)
search_photos
Search person photos and entity assets by query/metadata. Returns inline MCP image attachments. ($0.10; API key required)
resolve
resolve_clarification
Link a clarification surface to an existing person. ($0.10; API key required)
resolve_person
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. Notes omitted unless include_notes=true (redacted). Prefer this before money or relationship tools when the agent only has a nickname. Advertised name resolve_person is stable; tools/call also accepts resolve_contact. ($0.05; API key required)
resolve_place
Canonicalize a venue name via place aliases and fuzzy match. ($0.10; API key required)
sleep
get_sleep
Sleep: list typed sleep/nap records with duration_minutes. ($0.05; API key required)
get_sleep_summary
Sleep: day/week/month totals and averages. ($0.05; API key required)
update_sleep
Sleep: patch an existing sleep record by sleep_id. ($0.10; API key required)
asset
get_asset
Fetch one asset by asset_id with signed_url for download/processing. ($0.05; API key required)
update_asset
Patch role, metadata, description, or parent_asset_id (e.g. mark as processed). ($0.08; API key required)
cleanup
cleanup_apply
Atomically archive the exact reviewed preview. Requires preview_id, candidate_hash and request_id. Refuses changed sources. Returns per-row statuses and restore_id; replay performs no additional actions. ($0; API key required)
cleanup_preview
Read-only account audit and durable archive plan for events, expenses or trips. Returns source hashes, linked records, field differences, rollback payloads and a review queue. Review the exact candidate set before cleanup_apply. Preview expires after 30 minutes. ($0; API key required)
current
get_current_states
Permitted assertion states for a person (flagged life-graph; off by default). ($0.10; API key required)
update_current_location
MUTATES where the user is now: profiles.location + polaris current_city/country (same as in-app Dayze chat). Pass location ("The Madeira, Singapore") and/or city+country; optional place/venue + lat/lon records a fresh location_visits check-in so get_location_context returns is_current. set_home defaults true; check_in defaults true when place or coordinates are set. Does not invent GPS when omitted. ($0.10; API key required)
entity
get_entity_assets
List assets linked to an entity (role, signed_url, versions). entity_type inventory_item → inventory. ($0.10; API key required)
get_entity_links
List graph edges for an event, trip, place, or person. ($0.05; API key required)
event
delete_event
Reversibly archives one owned event. Required event_id and request_id. Returns the prior row in deleted for compatibility, changed, restore_id and life_state_rebuilt. All food, people and asset links are preserved. Restore with restore_event. Replays perform no additional action. ($0.10; API key required)
update_event
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, category, external_url, people / with / person_ids. Unknown or other-user event_id returns an error and does not create a row. For food-diary meals, prefer update_food (it syncs the mirrored event). Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
food
delete_food
MUTATES by removing one Food Diary row the authenticated user owns and its mirrored calendar event. Required: food_id (UUID). Prefer this over delete_event for meals logged via log_food. Unknown or other-user food_id returns an error. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
update_food
MUTATES one existing Food Diary row the authenticated user owns. Required: food_id (UUID). Optional patch (same fields as log_food): what, kind, place, merchant, notes, append_notes (concat), consumed_at / meal_period (profile TZ civil wall-clock), amount, currency, paid_by / payment_method, with / people_names / person_ids. Example: add hot tea onto an existing Salmon Bento → update_food({ food_id, what: "Salmon Bento + hot tea" }). Unknown or other-user food_id returns an error and does not create a row. Syncs the mirrored calendar event and rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
import
import_uber_gmail
Search connected Gmail for Uber trip receipts and write log_place_visit rows with sources gmail:uber-{gmail_id} (idempotent). Optional dry_run, max_results, query, account. ($0.15; API key required)
import_venmo_gmail
Search connected Gmail for Venmo receipts and write log_transaction rows with external_id=venmo-gmail-{gmail_id} (idempotent). Optional dry_run, max_results, query, mirror_event, account. Prefer this over calendar-only Money · digs. ($0.15; API key required)
life
get_life_context
Get a snapshot of the authenticated user's current life context (identity, today/upcoming events, pulse, trackers). Relationships and memories are included by default; pass include_*=false to omit. Location is opt-in. Requires an authenticated Dayze account via OAuth; scoped API keys are also supported for direct clients. ($0.15; API key required)
get_life_graph
Explicit private life-graph export: favorites/VIP plus people with edges or recent event tags. Pass full=true for a larger capped list. Optional event–people links. Requires OAuth or a supported scoped credential. ($0.25; API key required)
location
get_location_context
Likely current or at-time place with confidence and provenance. ($0.10; API key required)
get_location_history
Normalized visit history (venue-level by default). Merges GPS location_visits + place_visits (MCP/Uber digs). ($0.10; API key required)
merge
merge_people
Apply a reviewed durable preview atomically; undo_contact_change accepts restore_id for 30 days if unchanged. Fold duplicate CRM contact(s) into primary_person_id (same human, spelling variants). Prefer score_people_duplicates first. Not for “X knows Y” — use link_people for relationships. ($0.10; API key required)
merge_people_preview
Save a durable restore snapshot without modifying contacts before merge_people. Returns resulting name/aliases, preserved counts, field conflicts, safe_to_merge. ($0.05; API key required)
normalize
normalize_people_apply
Apply a normalize_people_preview by preview_id. ($0.10; API key required)
normalize_people_preview
Preview whitespace/phone/handle normalization changes (no title-case of stylized names). ($0.05; API key required)
record
record_purchase
Atomic expense + optional inventory item creation. ($0.10; API key required)
record_sale
Mark inventory sold + record sale proceeds with gain/loss. ($0.10; API key required)
transactions
get_transactions
List expense/income/transfer rows (includes tags, payment_method). Filter with tag=project:… or project=… ($0.10; API key required)
search_transactions
Keyword search over merchant/description/category, or exact tag query (project:/ext:/rail:). ($0.10; API key required)
upload
upload_asset
Upload image bytes to Dayze storage (WebP re-encode strips EXIF/AI metadata). Returns asset_id. For inventory item photos: pass entity_type=inventory, entity_id=inventory_id, role=photo, image_base64 from chat images. Or upload then attach_asset. ($0.15; API key required)
upload_photo
Upload a photo to a Life Graph entity. Accepts image_base64 or url (one required). Re-encodes via WebP (strips EXIF/AI metadata). Person uploads also write the CRM gallery (person_photos) and avatar when set_as_avatar=true. ($0.15; API key required)
attach
attach_asset
Link an existing asset_id to another entity by creating a linked copy (does not move the original row). Roles: original | processed | thumbnail | cover | document | receipt | certificate | other. Legacy: pass url instead of asset_id. ($0.10; API key required)
audit
audit_people
CONTEXT LAYER: server-side contact hygiene. Returns compact candidate clusters only (duplicates, entity-type hints, normalization, payment-handle collisions). Do NOT use get_people bulk dumps for cleanup. ($0.10; API key required)
bulk
bulk_dismiss_clarifications
Dismiss non-person / typed junk from the clarification queue. ($0.05; API key required)
cities
get_cities_visited
Canonical cities from confirmed/completed trips only (excludes soft pins / status=possible). Inference requires category=travel + structured location — not todo titles. ($0.10; API key required)
clarifications
list_clarifications
Ranked clarification queue: only person-typed mentions + duplicate CRM people. Non-person junk (places, orgs, media, command fragments) is auto-dismissed. Existing contacts auto-link. ($0.05; API key required)
classify
classify_contact
Set entity_type (person/company/merchant/…) on a CRM row without losing transactions or links. ($0.10; API key required)
commit
commit_life_update
Owner approve+commit via payload_hash + owner_session_id (flagged; off by default). ($0.10; API key required)
compare
compare_lives
Side-by-side notable packs for two slugs (life_in_days + day_number timelines). One call instead of two notable_pack. Example: elon-musk vs steve-jobs. ($0.08)
context
get_context_pack
Life Context Protocol (LCP) pack for the authenticated user: identity, pulse, who_matters, whats_next, memories, quiz_results. Pass include_relationships/include_memories/include_quiz_results false to omit those sections; location and money stay opt-in. Spec: https://dayze.com/docs/life-context ($0.20; API key required)
convert
convert_contact_entity
Convert a contact’s entity_type (same as classify_contact). Preserves FKs. ($0.10; API key required)
countries
get_countries_visited
Canonical countries from completed trips (not other people travel). ($0.10; API key required)
dismiss
dismiss_clarification
Dismiss a pending entity clarification (not_person, etc.). ($0.05; API key required)
enrich
enrich_place_from_google
Optional Google Places fill for a saved place card (hours/address/phone/website). Defaults to fill_empty_only — does not overwrite agent-supplied fields. ($0.15; API key required)
events
get_events
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. ($0.10; API key required)
expense
update_expense
PATCH an expense row. ($0.10; API key required)
expenses
get_expenses
Authenticated user cashflow summary: spend, income, net, and top spend categories. Requires OAuth or a supported scoped credential. ($0.10; API key required)
explain
explain_fact
Return evidence/provenance for a claim: polaris_learned_facts, life_events / life_event_relationships when present, then memories. Use when the agent must cite why it believes something — do not invent sources. ($0.10; API key required)
identity
find_identity_candidates
Compact identity resolution candidates by person_id or query (alias/name/payment signals). Prefer over bulk get_people. ($0.05; API key required)
interactions
get_interactions
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. ($0.10; API key required)
memories
get_memories
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)
money
get_money_between_people
Same as get_person_transactions: authenticated user ↔ one contact via expenses FKs. Prefer get_person_transactions; this alias exists for agent discoverability. ($0.10; API key required)
photo
get_photo
Single photo metadata + secure URL. Returns inline MCP image attachment when available. ($0.10; API key required)
places
get_places
Known venues: visit-graph `places` plus saved place cards (`saved_places` from business_contacts) with address, opening_hours, and affordability ($/$$/$$$). ($0.10; API key required)
primary
set_primary_person_name
Rename a CRM contact’s canonical name and refresh slug. By default preserves the old name as a former_name alias. Prefer this over create+merge for spelling fixes. Dayze is the context layer — bounded mutation only. ($0.10; API key required)
propose
propose_life_update
Propose assertion create/correct without committing (flagged; off by default). ($0.10; API key required)
reset
reset_tracker
MUTATES 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. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
residences
get_residences
Home / residence history separate from trips: trips with metadata.kind=residence (from log_travel) plus optional life_eras. Use for Boylston / Madeira / current home cards. ($0.10; API key required)
score
score_people_duplicates
Score likely CRM duplicate pairs before merge_people. ($0.05; API key required)
search
search
Search the authenticated user life graph. Deterministic routing first: food + relative dates (e.g. "what did I eat yesterday?"); timeline/current-context; money+person; who-is → resolve_person. Otherwise semantic/keyword search. Event hits include event_date and food_id when mirrored from Food Diary. Browser-history titles are excluded. Credential/secret spans are redacted. Requires OAuth or a supported scoped credential. ($0.15; API key required)
start
start_people_cleanup
Server-side read-only cleanup audit. Returns a review queue; never automatically merges contacts. Use normalize_people_preview/apply for reversible normalization. ($0.15; API key required)
trackers
get_trackers
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. Requires OAuth or a supported scoped credential. ($0.10; API key required)
travel
get_travel_history
Completed/confirmed travel only. ($0.10; API key required)
trip
get_trip
Single trip with linked places and people. ($0.10; API key required)
trips
get_trips
User trips with status filter (planned/completed/etc.). Residences also appear here with metadata.kind=residence — prefer get_residences for home history. ($0.10; API key required)
undo
undo_contact_change
Reverse a reversible contact_mutations row (rename, alias, identity, classify, link). For merges, pass restore_id as change_id within 30 days. Restore rejects later edits rather than overwriting them. ($0.10; API key required)
unlink
unlink_people
Remove a person↔person graph edge. ($0.10; API key required)

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_photos_for_person
removed 1 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://dayze.com/api/mcp streamable-http answering 869 ms 4 min ago
https://dayze.com/api/mcp/key streamable-http answering 719 ms 4 min ago

Alternatives to Dayze — Life Context

same job, measured the same way
Context Relay
by chughes113

Compact, citation-verifiable public web context for AI agents, paid per use with x402.

2 tools answering
DocPull
by raintree-technology

Sync public web sources into cited context packs for AI agents, RAG, and MCP clients.

1 920 installs/wk local only
Agent Workpad
by agentworkpad

Low-context public task coordination for software agents.

12 tools answering
ivygrep
by bvolpato

Local code search and task context packs for coding agents

local only
TikTok Agent Publisher
by davidmosiah

Local-first TikTok Content Posting API for AI agents: OAuth checks, dry-run and live uploads.

78 installs/wk local only
NudgeHost
by nudgehost

File hosting for agents. Upload any file, get a public link in seconds.

answering
Hookjar
by comiza

Public webhook inboxes for agents. Receive OAuth redirects, payment callbacks and CI notifications.

6 tools answering
D
Kit Lite
by workers-randall-75d-kit-lite

Instant x402 spend-cap pack for agents. get_quote then buy_intel_pack 5 USDC Base. No human.

5 tools answering

Dayze — Life Context — questions

Answers built from our own checks of this server.

What can Dayze — Life Context do?
It exposes 130 tools, read directly from the server on our last check. Among them: add_inventory_item, add_inventory_valuation, add_person_alias, archive_asset, archive_event, archive_expense and 124 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Dayze — Life Context mostly used for?
Its tools cluster around person, log and inventory. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Dayze — Life Context working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 181 of 182 checks got a reply (99.5%), average response time 786 ms. The bar chart above shows every period we have measured.
Did Dayze — Life Context ever remove tools?
Yes. get_photos_for_person is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Dayze — Life Context?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Dayze — Life Context need an API key?
No. Dayze — Life Context completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 130 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Dayze — Life Context?
It answers our handshake in 786 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Dayze — Life Context open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.