Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Dayze — Life Context

REMOTE · DAYZE.COM · 2 COMPONENTS

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

0 this week 67 Trust /100

Last scanned (12 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Memory and Knowledge

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 16557 tokens (~367/item across 45 items; 42 tools + 3 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 Management20
  • Stability check failed: schema churn in the 30 days we've observed: 144 tool removals, 1 breaking changes, 0 auth/transport breaks, 6 additions. See how to fix → Fail
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 42 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 44 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

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 →

Changelog

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.

  • 19 Nov 26 0
    • Tool “update_person” rewrote its description, which is the text the model reads security
    • Server version: 1.77.2 → 1.77.4 functional
    • “create_person” added an optional parameter “remove_education_ids” cosmetic
    • “create_person” added an optional parameter “education” cosmetic
    • “create_person” added an optional parameter “locations” cosmetic
    • “update_person” added an optional parameter “remove_location_ids” cosmetic
    • “update_person” added an optional parameter “remove_education_ids” cosmetic
    • “update_person” added an optional parameter “locations” cosmetic
    • “update_person” added an optional parameter “education” cosmetic
    • “create_person” added an optional parameter “remove_location_ids” cosmetic
    • “update_person” added an optional parameter “discovery_source” cosmetic
    • “update_person” added an optional parameter “contact_origin” cosmetic
    • “update_person” reworded the description of “relationships” cosmetic
    • “update_person” reworded the description of “context_tags” cosmetic
    • “update_person” reworded the description of “last_interaction_at” cosmetic
    • “update_person” reworded the description of “person_id” cosmetic
    • “update_person” reworded the description of “request_id” cosmetic
  • 18 Nov 26 0
    • Tool “update_person” rewrote its description, which is the text the model reads security
    • Server version: 1.77.1 → 1.77.2 functional
    • “update_person” added an optional parameter “hobbies” cosmetic
    • “update_person” added an optional parameter “interests” cosmetic
    • “update_person” reworded the description of “preserve_old_name_as_alias” cosmetic
    • “update_person” reworded the description of “request_id” cosmetic
    • “update_person” reworded the description of “tier” cosmetic
    • “update_person” reworded the description of “wallets” cosmetic
    • “update_person” reworded the description of “is_favorite” cosmetic
    • “update_person” reworded the description of “name” cosmetic
  • 14 Nov 26 0
    • Server version: 1.77.0 → 1.77.1 functional
  • 11 Nov 26 −12
    • Schema quality: 233 → 365 ▼ functional
    • Destructive annotations: 100 → pass functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 10 Nov 26 +1
    • Schema quality: 197 → 233 ▼ functional
    • Tool coverage: 64% → 100% ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 9 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 8 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 7 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

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 21 Nov 2026 · Probed https://dayze.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dayze.com CN=YE1,O=Let's Encrypt,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA384 6fe233b3b1bfd9c2b9d0e1fec960b1d076d
SANs: *.dayze.com, dayze.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dayze.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dayze.com. 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; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dayze.com/api/mcp Verified 200
http (plaintext) http://dayze.com/api/mcp HTTPS enforced 301 https://dayze.com/api/mcp
MCP tools · 42 exposed · ~16,064 tokens

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 →

Tool Tokens
create_goal ~441

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.10; API key required)

NameTypeReqDescription
categorystring–Goal category, e.g. health.
checkin_frequencystring–How often to check in on the goal: daily, weekly or monthly, e.g. weekly.
current_valuenumber–Progress so far in target_unit, e.g. 5.
descriptionstring–What the goal is, e.g. Run a half marathon by March.
habit_frequencystring–How often the habit repeats, e.g. weekly.
habit_target_countinteger–Times per period needed to hit the habit target, e.g. 3.
idempotency_keystring–Alias for request_id.
motivationstring–Why the goal matters to the user, e.g. To stay healthy for my kids.
obstaclesstring–What might get in the way, e.g. Long work travel.
prioritystring–Priority level: high, medium or low, e.g. medium.
request_idstring–Client idempotency key (retries return original result).
start_datestring–Start date YYYY-MM-DD, e.g. 2026-10-17.
target_datestring–Target date YYYY-MM-DD, e.g. 2026-12-31.
target_typestring–Goal type: completion, numeric, rate or habit, e.g. numeric.
target_unitstring–Unit for target_value, e.g. km.
target_valuenumber–Number the goal aims for, e.g. 21.
titlestringyesGoal title, e.g. Run a half marathon.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
goalobject|nullyes–
goal_idstringyes–
inspect_notestring–What inspect_url opens. Never quote the record id.
inspect_urlstring–The Dayze page that shows the saved record.
messagestringyes–
progress_loggedboolean––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
verifiedboolean––

No examples provided.

create_pending_reply ~580

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 one (or pass person_id); otherwise the reply is saved unlinked and person_link says why. An unsent reply for the same thread or person comes back instead of a second one (created: false, deduplicated: true); update_existing: true replaces its draft and summary. Never sends anything. Requires API key or OAuth with context.write; share tokens cannot write. ($0.10; API key required)

NameTypeReqDescription
categorystring–Default personal.
channelstring–Where to reply: whatsapp, email, sms, call, imessage, telegram, instagram, facebook, signal, linkedin, twitter, slack, reddit, teams, work_email, zoom, dayze, other; the platform the conversation is…
draftstring–The reply text to send later, max 20,000 characters. Replaces the saved draft; empty or null clears. Alias: draft_message.
draft_messagestring–Alias for draft.
idempotency_keystring–Alias for request_id.
person_idstring–An owned contact id; links that contact directly.
person_namestringyesWho the reply is owed to, as the user said it (e.g. "Ilana").
received_atstring–When they wrote (ISO date-time). Default now.
recipient_emailstring–Optional recipient email (auto-link; never sends).
recipient_handlestring–Optional recipient handle (auto-link; never sends).
recipient_phonestring–Optional recipient phone (auto-link; never sends).
request_idstring–Client idempotency key (retries return original result).
sourceobject–The email the reply answers, as ids only (e.g. a search_gmail id is a message_id). Never a subject, sender or text. On update, null clears it.
summarystring–One line (max 280) in your own words: what the reply is about. Never paste the email body, subject line or sender address.
update_existingboolean–When an unsent reply for this thread or person exists, write draft/summary onto it instead of returning it unchanged.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
app_urlstring––
createdbooleanyesTrue when this call saved a new reply.
deduplicatedbooleanyesTrue when an unsent reply for the same thread or person was returned instead of a new one.
life_state_rebuiltbooleanyes–
matched_onstring|nullyessource_thread, source_message or person when deduplicated.
messagestringyes–
person_linkobjectyesWhether a contact was linked. Linked only on one resolve_person match or an owned person_id.
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
replyobjectyesOne reply the user owes (Inbox → Pending Replies). Dayze never sends it.
source_savedbooleanyesFalse when a source was given and could not be stored.
updatedbooleanyesTrue when an existing unsent reply was changed (update_existing).

No examples provided.

create_person ~547

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 create_contact. ($0.10; API key required)

NameTypeReqDescription
aliasesarray–Alternate names stored as aliases, e.g. ["Lex","Alex C"].
birthdaystring–YYYY-MM-DD, YYYY-MM, YYYY, or MM-DD / --MM-DD when the year is unknown (same as update_person)
companystring|null–company. Omit to leave unchanged; null or blank clears.
context_tagsarray–Context tags such as Work, Personal or Family, e.g. ["Work"].
educationarray–Merge school entries by id. New entry needs school only; omit unknown qualifications/dates.
emailstring|null–email. Omit to leave unchanged; null or blank clears.
idempotency_keystring–Alias for request_id.
is_favoriteboolean–Mark the contact as a favorite, e.g. true.
locationsarray–Merge by id; omitted entries/fields stay. City or approximate area suffices. Never infer a residence.
namestringyesDisplay name, e.g. Alex Chen.
notesstring–Free-text note, e.g. Follow up next week.
occupationstring|null–Occupation / job title. Omit to leave unchanged; null or blank clears.
phonestring|null–phone. Omit to leave unchanged; null or blank clears.
relationshipstring–Relationship label, e.g. friend or sister.
relationshipsarray–Who they are to the user, primary first, e.g. ["friend","colleague"].
remove_education_idsarray–Explicitly remove only these school entry ids; legacy summary stays.
remove_location_idsarray–Explicitly remove only these location ids.
request_idstring–Client idempotency key (retries return original result).
tierstring–Relationship priority: vip, normal or low, e.g. vip.
walletsarray–PHI-930: ENS (.eth) / SNS (.sol) names and/or addresses for this contact. Stored in social_handles (legacy ens/ens_address kept).
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
aliasesarray–Aliases saved on the new contact.
aliases_not_savedarray–Aliases not saved (another contact has them); the contact was still created.
birthdaystring–As stored: YYYY-MM-DD. A year-unknown birthday is 1900-MM-DD (Feb 29: 1904-02-29).
birthday_precisionstring|null–day, month, year, month_day (year unknown) or approximate.
candidatesarray––
changedobject––
codestring––
companystring|null––
createdboolean––
created_atstring––
duplicateboolean–True when the contact already existed: nothing on it was changed.
educationarray––
education_summarystring|null––
emailstring|null––
has_locationsboolean––
hintstring––
hygiene_flagsarray––
idstring––
idempotent_replayboolean––
inspect_notestring–What inspect_url opens. Never quote the record id.
inspect_urlstring–The Dayze page that shows the saved record.
locationsarray––
locations_withheldboolean––
matched_viastring|null––
messagestring––
namestring––
needs_clarificationboolean–Ask which contact the user means; no contact was created or changed.
not_appliedarray–On a duplicate: the fields sent that were not saved.
occupationstring|null––
peoplearray––
personobject–CRM person record.
person_idstring–The new contact, or the existing one on a duplicate.
person_idsarray––
phonestring|null––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
role_expandboolean––
skippedboolean––
slugstring|null––
walletsarray––

No examples provided.

create_tracker ~194

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)

NameTypeReqDescription
emojistring–Single emoji, e.g. 🎂.
idempotency_keystring–Alias for request_id.
request_idstring–Client idempotency key (retries return original result).
start_datestring–YYYY-MM-DD. Default today.
target_datestring–YYYY-MM-DD.
target_daysinteger–Number of days to reach, e.g. 30.
titlestringyesTracker title, e.g. Days sober.
tracker_typestring–Tracker kind: streak, sobriety, countdown or counter, e.g. streak.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
createdboolean––
event_idstring––
messagestring|null––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.

No examples provided.

get_birthdays ~247

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_since_birthday. Counts contacts without a birthday. Excludes Me, never-share and deceased contacts (include_deceased adds them as remembrance). ($0.05; API key required)

NameTypeReqDescription
days_aheadinteger–Days after today (default 30).
days_backinteger–Days before today, for missed birthdays (default 30).
fromstring–Window start YYYY-MM-DD (instead of days_back).
include_deceasedboolean–Add deceased contacts, marked remembrance (default false).
limitinteger–Per list (default 25).
tostring–Window end YYYY-MM-DD (instead of days_ahead). At most 366 days in all.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
countnumberyes–
inspect_notestring–How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.
missing_birthdaysobject–{ count, hint }: contacts without a birthday in Dayze.
notestring––
recentarray––
recent_countnumber––
remembrance_notestring––
timezonestring––
todaystring–Today in the account timezone (YYYY-MM-DD).
truncatedboolean––
upcomingarray––
upcoming_countnumber––
windowobject–{ from, to }: the inclusive civil window.
without_dayobject–{ count, hint }: contacts with only a birth year or year and month.

No examples provided.

get_context_pack ~490

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_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.20; API key required)

NameTypeReqDescription
atstring–ISO date-time to answer as of (default now), e.g. 2026-09-26T09:00:00+08:00.
budget_tokensnumber–Whole-pack token budget (clamped to 300–12000); list omissions are recorded in budget.sections.
focusstring–Optional focus hint echoed in the pack (e.g. places, travel, people)
include_locationboolean–Include city/country label; never returns a precise address
include_memoriesboolean–Include recent memories.
include_moneyboolean–Include the private cashflow summary
include_place_visitsboolean–Include recent venue visits; never a GPS trail
include_placesboolean–Include recent canonical places.
include_quiz_resultsboolean–Include latest quiz results.
include_relationshipsboolean–Include people and relationship context.
include_taste_profileboolean–Include the bounded taste_profile section (visual / writing / dont cards with inspect_url). Not hobbies or learned facts.
include_tripsboolean–Include up to 10 stored trips via get_trips (no inferred trips); count is returned items, total/has_more/next_cursor expose paging, budget.sections exposes token cuts
include_week_eventsboolean–Include calendar-week events; defaults on except focus next_actions/current/now. False keeps an empty compatibility list with omitted_for_focus semantics.
qstring–Alias for query.
querystring–Question that guides facts and memories.
timezonestring–IANA time zone for today (default: where the user is now, else their home zone).
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
briefingobject–Daily projection clock, fingerprint and section availability for a requested briefing. Priorities are in whats_next.recommended_actions.
budgetobject–Whole-pack token budget and per-list truncation ledger: budget_tokens is the effective budget, requested_tokens what was sent (null if none), adjustment why they differ (clamped_to_min, clamped_to_ma…
errorstring–Present when life state is unavailable.
factsarray–Question-aware personal facts, in selection order.
focusstring|null––
generated_atstring––
identityobjectyes–
inspect_notestring–How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.
known_factsarray––
locationobject–City/country-only get_location_context projection when include_location=true.
memoriesobject––
okboolean––
omittedarray–Facts left out, counted by reason.
partialboolean––
place_visitsarray––
placesobject–Recent canonical places when include_places=true.
preferred_toolstringyes–
protocolobjectyesLife Context metadata.
pulseobjectyes–
querystring|null––
quiz_resultsobject–Latest results when include_quiz_results=true; items/count and limit.
redactionobject–pii redacted|raw; sensitive_topics the caller may receive; counts of sensitive trackers / memories withheld.
sectionsobject–Per-section ok/error status for partial packs.
taste_profileobject–PHI-2124: bounded taste brief when include_taste_profile=true; items (with inspect_url)/count/limit/live_cap.
traceobject–Which facts were supplied and why. fact_ids equals facts[].id.
tripsobject–Stored trips when include_trips=true; items/count, limit, total/has_more/next_cursor. Budget cuts are in budget.sections.
whats_nextobjectyesCalendar buckets, trackers, goals and replies. With include_money: money (summary or null) and money_status: ok, no_data, not_shared (privacy settings withhold money aggregates) or unavailable.
who_mattersobject––

No examples provided.

get_events ~522

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)

NameTypeReqDescription
atstring–ISO date-time to answer as of (default now), e.g. 2026-09-26T09:00:00+08:00.
cursorstring–Opaque pagination cursor from the previous page's next_cursor, e.g. eyJvIjoyMH0.
date_fromstring–Alias for from.
date_tostring–Alias for to.
event_kindsarray–Alias for kinds.
fromstring–Inclusive YYYY-MM-DD (preferred over range)
include_archivedboolean–Include archived rows, e.g. false.
include_browsingboolean–Include extension "Browsed domain · Xm" auto-events (default false)
include_calendar_blocksboolean–Include Focus Time / calendar_block rows (default false)
kindsarray–Filter by event_kind: life_event, calendar_block, todo, goal, travel_segment, food_log, health_record, transaction, media_log, work, family, personal. Alias "food" (also meal/drink/snack) matches the…
limitnumber–Maximum rows to return, e.g. 20.
offsetnumber–Skip this many matching rows of a new snapshot (a cursor carries its own).
querystring–Literal substring in title, description or location.
rangestring–Shortcut window instead of from and to: today, week, month, year, decade or all, e.g. week.
redact_piiboolean–true: redact contact details, card and account numbers and secrets in description, location and scoreboard, even where this connection may see them. Never unredacts: without travel_secrets:read they…
timezonestring–IANA time zone for today (default: where the user is now, else their home zone).
tostring–Inclusive YYYY-MM-DD
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
capnumberyes–
eventsarrayyes–
expires_atstring––
fromstring|nullyesInclusive YYYY-MM-DD lower bound; null for all records.
has_moreboolean––
inspect_notestring–How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.
next_cursorstring|null––
orderingstring––
rangestringyes–
server_timestring––
snapshot_atstring––
snapshot_idstring––
timezonestringyesResolved timezone used for this event window and as fallback for rows without one.
tostring|nullyesInclusive YYYY-MM-DD upper bound; null for all records.
totalnumber––
truncatedbooleanyes–

No examples provided.

get_expenses ~70

Cashflow totals at Finance FX. Use period all for all-time requests, never year. Requires OAuth or scoped credentials. ($0.10; API key required)

NameTypeReqDescription
periodstring–all: no date filter; month: last 30 days (default); year: last 365 days.
NameTypeReqDescription
by_currencyarray––
countnumber––
currencystring|null––
incomenumber––
multi_currencyboolean––
netnumber––
partialboolean–True when the headline USD totals exclude unconverted currencies.
periodstringyes–
period_daysnumber–Window length in days; 0 means all time (no date filter).
spendnumber––
top_categoriesarray––
unconvertedarray––
usdobject–Totals converted to USD (approximate FX).

No examples provided.

get_goals ~164

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)

NameTypeReqDescription
goal_idstring–Goal id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
limitinteger–Maximum rows to return, e.g. 20.
statusstring–Goal status filter, default active, e.g. active.
NameTypeReqDescription
countnumberyes–
goalsarrayyes–

No examples provided.

get_interactions ~405

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. 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)

NameTypeReqDescription
event_idstring–Calendar event id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
expense_idstring–Finance transaction id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
fromstring–Inclusive YYYY-MM-DD
limitnumber–Max 1–50, default 25
person_idstring–Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
person_namestring–Contact name when there is no person_id, e.g. Alex Chen.
place_idstring–Place id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
place_querystring–Venue/merchant substring
tostring–Inclusive YYYY-MM-DD
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
degradedboolean––
errorstring|null––
inspect_notestring–How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.
interactionsarray––
no_databoolean––
okboolean––
truncatedboolean––
windowobject–Bounded from/to lookback window.

No examples provided.

get_memories ~122

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)

NameTypeReqDescription
focusstring–Ranks memories toward this focus. next_actions (or current, now) returns only up to 4 next-action memories.
limitnumber–Max rows 1–50, default 20
qstring–Alias for query.
querystring–Semantic focus (optional)
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
eventsarray––
inspect_notestring–How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.
memoriesarrayyes–
modestringyes–
peoplearray––
querystring––

No examples provided.

get_moments ~223

List owned Moments by date, title, type, tag, person or place. Stable moment_id and inspect_url for each. ($0.05; API key required)

NameTypeReqDescription
fromstring–YYYY-MM-DD inclusive
limitinteger–Maximum rows to return, e.g. 20.
moment_typestring–Moment type such as first_met, milestone, trip or memory, e.g. milestone.
offsetinteger–Rows to skip for paging, e.g. 0.
person_idstring–Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
placestring–Place text to filter by, e.g. Lisbon.
tagstring–Tag to filter by, e.g. travel.
titlestring–Words to match in the moment title, e.g. Lisbon.
tostring–YYYY-MM-DD inclusive
NameTypeReqDescription
limitnumberyes–
momentsarrayyes–
next_offsetnumber|nullyes–
offsetnumberyes–

No examples provided.

get_pending_replies ~255

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 while snoozed until snooze_until). Read-only. ($0.05; API key required)

NameTypeReqDescription
limitnumber–1-200, default 50.
person_idstring–Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
person_namestring–Contact name when there is no person_id, e.g. Alex Chen.
reply_idstring–Read one reply (ignores the filters).
statusstring–Reply state filter: unsent, sent, dismissed or all, e.g. unsent.
NameTypeReqDescription
app_urlstring––
countnumberyes–
has_morebooleanyes–
pending_repliesarrayyes–
statusstringyesThe filter applied: unsent, sent, dismissed or all.

No examples provided.

get_people ~593

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 owner-reviewed wealth-category contacts: returns id and name only, even with include_notes=true. That mode searches names only, uses offset rather than cursor, and cannot combine with occupation or context_tags. Without it, each contact includes avatar_url, photo_count, and has_photos; use get_person_photos(person_id) for the full gallery. With financial_details:read, net_worth_assessment includes category, scope, estimated range (when supported), confidence, methodology, caveat, dated source URLs, and review date. Context-only and insufficient-evidence assessments carry no personal number. birthday_precision says which parts of birthday are real: month_day means the year is unknown (stored 1900, or 1904 for Feb 29), year means only the year. 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)

NameTypeReqDescription
context_tagsarray–Require every exact context tag, case insensitive (for example ["model"]). Cannot combine with wealth_category.
cursorstring–Opaque pagination cursor from the previous page's next_cursor, e.g. eyJvIjoyMH0.
include_listsboolean–When true, each contact includes lists: [{ id, name, slug }]. Default false.
include_notesboolean–When true, include notes (server-redacted). Default false.
limitnumber–Page size (default 100, max 500)
listsarray–Only contacts on any of these contact lists (ids or slugs from list_contact_lists), by name; page with offset. Cannot combine with query, occupation, context_tags, wealth_category or cursor.
occupationstring–Require this literal substring in the occupation field. Cannot combine with wealth_category.
offsetnumber–Skip N rows (default 0)
querystring–Literal substring search over name, slug, email, occupation and context tags; with wealth_category=reviewed, name only. No fuzzy fallback.
wealth_categorystring–Only explicitly owner-reviewed wealth-category contacts. Returns id and name only; cannot combine with occupation or context_tags.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
context_tagsarray––
expires_atstring––
has_moreboolean––
include_notesboolean––
inspect_notestring–How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.
limitnumberyes–
match_modestring–unfiltered, structured or literal_substring; get_people has no fuzzy fallback.
next_cursorstring|null––
no_matchboolean–True when a query or profession filter matched no contacts.
occupationstring|null––
offsetnumberyes–
orderingstring––
peoplearrayyes–
querystring|null––
scan_limitedboolean–Legacy compatibility field; filtered database searches return false.
self_notestring–Present when the page includes the user's own card (Me): that person has is_self: true and a display_name ending in (Me), and is not counted in total.
server_timestring––
snapshot_atstring––
snapshot_idstring––
totalnumberyes–
truncatedbooleanyes–
wealth_categorystring–reviewed when the result is restricted to explicitly reviewed wealth-category contacts.

No examples provided.

get_person_photos ~141

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)

NameTypeReqDescription
limitinteger–Maximum rows to return, e.g. 20.
offsetinteger–Rows to skip for paging, e.g. 0.
person_idstringyesContact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
NameTypeReqDescription
countnumberyes–
person_idstring––
photosarray––

No examples provided.

get_sleep ~94

Sleep: list typed sleep/nap records with duration_minutes. ($0.05; API key required)

NameTypeReqDescription
fromstring–Inclusive start date YYYY-MM-DD, e.g. 2026-10-01.
limitnumber–Maximum rows to return, e.g. 20.
tostring–Inclusive end date YYYY-MM-DD, e.g. 2026-10-31.
NameTypeReqDescription
countnumberyes–
sleepsarray––

No examples provided.

get_sleep_summary ~47

Sleep: day/week/month totals and averages. ($0.05; API key required)

NameTypeReqDescription
rangestring–Summary window: day, week or month, e.g. week.
NameTypeReqDescription
average_minutesnumber––
countnumberyes–
nightsnumber––
rangestring––
total_minutesnumber––

No examples provided.

get_timeline ~213

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)

NameTypeReqDescription
atstring–Optional ISO instant to read "today" at (defaults to now).
datestring–Alias for from (one day).
fromstring–First civil day, YYYY-MM-DD, in the account timezone. Alone = that one day. Default: today.
timezonestring–Optional IANA zone of the user's device (e.g. Asia/Singapore). Used only when the account has no zone set; the profile zone wins.
tostring–Last civil day, YYYY-MM-DD, inclusive.
NameTypeReqDescription
countsobject–Rows returned per section.
eventsarrayyes–
foodarrayyes–
fromstringyes–
momentsarrayyes–
timezonestringyes–
tostringyes–
todaystring––
truncatedobject–true per section when more rows exist than were returned.
unavailablearray––

No examples provided.

get_today ~138

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)

NameTypeReqDescription
atstring–Optional ISO instant to read "today" at (defaults to now).
currencystring–Optional 3-letter display currency for the money totals (default: the account's most used).
timezonestring–Optional IANA zone of the user's device (e.g. Asia/Singapore). Used only when the account has no zone set; the profile zone wins.
NameTypeReqDescription
countsobject–Rows returned per section.
datestringyes–
eventsarrayyes–
foodarrayyes–
fromstring––
local_timestring––
momentsarrayyes–
moneyobject–Today's money totals.
timezonestringyes–
tostring––
truncatedobject–true per section when more rows exist than were returned.
unavailablearray––

No examples provided.

get_trackers ~160

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 `limit` trackers (default 50, max 200; get_context_pack's active_trackers keeps 6); total and truncated say whether more exist. Requires OAuth or a supported scoped credential. ($0.10; API key required)

NameTypeReqDescription
limitnumber–Max trackers 1–200, default 50
NameTypeReqDescription
limitnumber––
notestring––
totalnumber––
trackersarrayyes–
truncatedboolean––

No examples provided.

log_event ~639

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: category sleep, event_date=wake day, end_time only. Past-tense: reminder_enabled=false. Prefer log_travel for trips/residences. Share tokens cannot write. ($0.10; API key required)

NameTypeReqDescription
amountnumber–Money; prefer log_transaction
categorystring–Category, e.g. sleep, work
citystring–City name
countrystring–Country name
currencystring–ISO currency
datestring–Alias: event_date
date_precisionstring–Soft dates keep this precision
descriptionstring–Notes
directionstring–from=in, to=out
end_datestring–End date YYYY-MM-DD
end_timestring–End time; alone for wake-only sleep
event_datestring–YYYY-MM-DD/YYYY-MM/YYYY; if the user gave none, ask. Don't use today
event_timestring–Start time, e.g. 20:00
event_typestring–Kind, e.g. todo
external_idstring–Dedupe key
external_urlstring–Source URL
idempotency_keystring–Retry key
image_urlstring–Cover URL
locationstring–Place, or city + country
mirror_transactionboolean–false = calendar only
notesstring–Alias: description
peoplearray–People to tag
people_namesarray–Alias: people
person_idstring–Contact id
person_idsarray–Owned person ids
person_namestring–Person to tag
reminder_enabledboolean–Push reminder; false for past-tense/log entries
reminder_minutes_beforenumber–Lead time, minutes
request_idstring–Alias: idempotency_key
scoreboardobject–Status data; state required if new; null clears
share_witharray–Handles
sourcestring–Rail, e.g. venmo
source_email_participantsarray–Gmail identities; not with people
source_gmail_idstring–Gmail id
timestring–Alias: event_time
timezonestring–IANA zone
titlestringyesEvent title
visibilitystring–Default private; public returns share_url
witharray–Alias: people
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
eventobjectyesA Dayze calendar event record.
import_hygiene_flagsarrayyes–
inspect_notestring–What inspect_url opens. Never quote the record id.
inspect_urlstring–The Dayze page that shows the saved record.
life_state_rebuiltbooleanyes–
people_email_anchoredarrayyes–
people_name_matchedarrayyes–
people_taggedarrayyes–
places_from_namesarray––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
unresolved_peoplearrayyes–
unresolved_source_peoplearrayyes–

No examples provided.

log_expense ~615

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)

NameTypeReqDescription
amountnumberyesPositive money amount in the stated currency, e.g. 12.50.
cash_movedboolean–With category "IOU lend": true (default) = cash changed hands as a loan (Finance); false = an owed share (IOU only). Ignored for iou_type invoice.
categorystring–"IOU repayment" = paying a contact back; "IOU lend" = lending a contact cash (both need person_id).
client_labelstring–Optional free-text client label for an invoice IOU.
currencystring–ISO 4217 currency code, e.g. USD.
datestring–YYYY-MM-DD; default today. Prefer with time + timezone when the source has a clock time.
descriptionstring–Alias for notes.
external_idstring–The provider's id for this payment; dedupes imports. Without a request_id it is required.
idempotency_keystring–Alias for request_id.
iou_typestring–loan (default) or invoice. Invoice = unpaid receivable (no Finance outflow); payment is income "Invoice payment". "I lent…" → loan.
merchantstring–Payee name (defaults when omitted)
notesstring–Free text about the payment. Alias: description.
occurred_atstring–Offset-aware ISO timestamp from the source. Never use ingestion/created_at.
payment_methodstring–Alias for source.
person_idstring–The contact paid (needed for "IOU repayment" / "IOU lend").
person_namestring–Contact by name when there is no person_id (IOU categories need one).
projectstring–Project label stored as project:{slug} tag, e.g. Max Soko poker venture.
request_idstring–Client idempotency key (retries return original result).
sourcestring–Payment rail or app: venmo, zelle, cashapp, card, cash, … Alias: payment_method.
tagsarray–Optional tags. Prefer project: / ext: / rail: grammar.
timestring–HH:mm or HH:mm:ss; no default. Pair with timezone or occurred_at.
time_certaintystring–exact, inferred, or unknown. Default exact when time/occurred_at is set.
timezonestring–IANA timezone or ±HH:MM; required for an exact instant with date+time.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
expenseobject–Expense/income transaction row.
expense_idstring––
inspect_notestring–What inspect_url opens. Never quote the record id.
inspect_urlstring–The Dayze page that shows the saved record.
messagestring|null––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.

No examples provided.

log_food ~590

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), place/merchant, amount, consumed_at (ISO). Explicit calories override the automatic heuristic. 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)

NameTypeReqDescription
amountnumber–Price if mentioned
caloriesnumber–Kilocalories explicitly stated by the user; overrides the automatic heuristic and is stored with user provenance
consumed_atstring–ISO instant; wins over meal_period
currencystring–ISO currency, e.g. SGD
dish_itemsarray–Ordered dishes in this entry. Each requires name; price and rating are optional.
expense_idstring–Link this entry to ONE existing Finance transaction you own (UUID from get_expenses / log_expense) instead of recording a new one
idempotency_keystring–Alias for request_id.
kindstring–Meal type: meal, snack or drink, e.g. meal.
meal_periodstring–Spoken period when consumed_at is omitted, e.g. "late lunch"
merchantstring–Restaurant, stall, or shop
notesstring–Free-text note, e.g. Follow up next week.
paid_bystring–Who paid. A person's name or alias for a third party; "self" / "me" = the user paid (recorded in Finance); "unknown" = payer not known. Not a payment method: use payment_method
payment_methodstring–How it was paid (cash, card, PayLah, PayNow…). Saved on the Finance transaction; never the payer
people_namesarray–Alias for with
person_idsarray–Owned person UUIDs to tag (user-scoped)
placestring–Venue or location
request_idstring–Client idempotency key (retries return original result).
whatstringyesWhat they ate or drank (required). Example: Mee Pok
witharray–Companion names, aliases, ids, or group tokens. "my parents" / Mum / Dad resolve via aliases; "family" expands to CRM rows with family relationship labels
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
event_idstring|nullyes–
food_idstringyes–
food_logobjectyesSaved Food Diary row.
inspect_notestring–What inspect_url opens. Never quote the record id.
inspect_urlstring–The Dayze page that shows the saved record.
life_state_rebuiltbooleanyes–
messagestringyes–
people_taggedarrayyes–
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
request_idstring|null–The request key used for exact replay of this food write.
unresolved_peoplearrayyes–

No examples provided.

log_income ~691

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 money once). ($0.10; API key required)

NameTypeReqDescription
amountnumberyesPositive money amount in the stated currency, e.g. 12.50.
cash_movedboolean–With category "IOU lend": true (default) = cash changed hands as a loan (Finance); false = an owed share (IOU only). Ignored for iou_type invoice.
categorystring–e.g. Salary, Gift, Refund. "IOU repayment" and "IOU lend" need person_id.
client_labelstring–Optional free-text client label for an invoice IOU.
currencystring–ISO 4217 currency code, e.g. USD.
datestring–YYYY-MM-DD; default today. Prefer with time + timezone when the source has a clock time.
descriptionstring–Alias for notes.
external_idstring–Provider id that dedupes imports, e.g. venmo-gmail-18c2a1b.
idempotency_keystring–Alias for request_id.
iou_typestring–loan (default) or invoice. Invoice = unpaid receivable (no Finance outflow); payment is income "Invoice payment". "I lent…" → loan.
merchantstring–Merchant or payee name, e.g. Blue Bottle.
not_iou_repaymentboolean–true only when income from a contact with an open IOU is unrelated to it.
notesstring–Free text about the payment. Alias: description.
occurred_atstring–Offset-aware ISO timestamp from the source. Never use ingestion/created_at.
payment_methodstring–How it was paid, e.g. card.
person_idstring–Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
person_namestring–Contact by name when there is no person_id (IOU categories need one).
projectstring–Project label stored as project:{slug} tag, e.g. Max Soko poker venture.
request_idstring–Client idempotency key (retries return original result).
sourcestring–Payment rail or app, e.g. stripe.
tagsarray–Optional tags. Prefer project: / ext: / rail: grammar.
timestring–HH:mm or HH:mm:ss; no default. Pair with timezone or occurred_at.
time_certaintystring–exact, inferred, or unknown. Default exact when time/occurred_at is set.
timezonestring–IANA timezone or ±HH:MM; required for an exact instant with date+time.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
directionstring––
duplicateboolean––
event_idstring|null––
expense_idstring––
inspect_notestring–What inspect_url opens. Never quote the record id.
inspect_urlstring–The Dayze page that shows the saved record.
messagestring|null––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
transactionobject–Expense/income transaction row.
transaction_idstring––
typestring––

No examples provided.

log_interaction ~334

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 reply's one write-back (a later resolve adds no second). summary: one line in your own words, never email text or a subject. occurred_at: when it happened (ISO), default now; not in the future. A past occurred_at never moves the contact's last interaction backwards (to correct that date, use update_person last_interaction_at). Never sends anything. Requires API key or OAuth with context.write. ($0.05; API key required)

NameTypeReqDescription
idempotency_keystring–Alias for request_id.
kindstring–Default message.
occurred_atstring–When it happened (ISO date-time). Default now.
person_idstring–An owned contact id.
person_namestring–The contact as the user said it ("Vadim"); linked only on one match.
reply_idstring–A Pending Reply (get_pending_replies) this closes as sent.
request_idstring–Client idempotency key (retries return original result).
summarystring–One line (max 280) in your own words. Never the email body, subject or sender.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
createdbooleanyesFalse when it was already stored (a retry, or the reply's write-back).
inspect_notestring–What inspect_url opens. Never quote the record id.
inspect_urlstring–The Dayze page that shows the saved record.
interactionobjectyesThe interaction in the contact's history (private to the owner).
life_state_rebuiltbooleanyes–
messagestringyes–
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
replyobject|nullyesOne reply the user owes (Inbox → Pending Replies). Dayze never sends it.
reply_resolvedbooleanyesTrue when this call marked the reply sent.

No examples provided.

Install

How do I install the Dayze — Life Context MCP server?

Dayze — Life Context is a hosted endpoint at https://dayze.com/api/mcp, 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 · dayze.com

# add to Claude Code
claude mcp add --transport http com-dayze-life-context 'https://dayze.com/api/mcp'
Common questions

What is the Dayze — Life Context MCP server?

Dayze — Life Context is an MCP server listed in the public MCP registry as com.dayze/life-context. Life context for agents: get_context_pack + public notable packs. x402 + OAuth. This page covers its hosted endpoint (https://dayze.com/api/mcp).

Is the Dayze — Life Context MCP server safe to use?

Dayze — Life Context scores 67 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 Dayze — Life Context MCP server expose?

Dayze — Life Context exposes 42 tools: search_tools, get_context_pack, get_events, get_people, update_person, and 37 more. Their descriptions and schemas cost roughly 16,064 tokens of context every time the server is loaded.

Does the Dayze — Life Context MCP server require authentication?

No. We connected to Dayze — Life Context without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Dayze — Life Context MCP server still maintained?

Dayze — Life Context is still listed as active in the MCP registry. We last reached this channel on 21 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 Dayze — Life Context MCP server?

VerifyMCP ran 13 checks on Dayze — Life Context, 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.