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 (20 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.

  • 20 Nov 26 0
    • Server version: 1.77.3 → 1.77.4 functional
  • 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.3 functional
    • “create_person” added an optional parameter “remove_location_ids” cosmetic
    • “update_person” added an optional parameter “locations” cosmetic
    • “update_person” added an optional parameter “discovery_source” cosmetic
    • “update_person” added an optional parameter “contact_origin” cosmetic
    • “create_person” added an optional parameter “remove_education_ids” cosmetic
    • “create_person” added an optional parameter “locations” cosmetic
    • “create_person” added an optional parameter “education” 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 “education” cosmetic
    • “update_person” reworded the description of “request_id” cosmetic
    • “update_person” reworded the description of “relationships” cosmetic
    • “update_person” reworded the description of “person_id” cosmetic
    • “update_person” reworded the description of “last_interaction_at” cosmetic
    • “update_person” reworded the description of “context_tags” 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 “interests” cosmetic
    • “update_person” added an optional parameter “hobbies” cosmetic
    • “update_person” reworded the description of “name” cosmetic
    • “update_person” reworded the description of “is_favorite” 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
  • 15 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
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/key

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/key Verified 200
http (plaintext) http://dayze.com/api/mcp/key HTTPS enforced 301 https://dayze.com/api/mcp/key
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
log_moment ~693

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 changed, converted or deleted, and one event can have many moments. Don't also save the story as an event. Optional: description (the longer story), moment_date_precision (exact, month, year, circa), end_date, moment_type (default memory), location_name (only a place the user said), person_ids (owned contacts; any other id saves nothing), people_names (tag saved contacts only, never created), cover_image_url / media_urls (https links), tags. Always private: there is no visibility argument; the owner shares a moment in Dayze. Fix it later with update_moment. Requires API key or OAuth with context.write. ($0.10; API key required)

NameTypeReqDescription
cover_image_urlstring–Optional https image link for the moment's cover (max 2048).
datestring–Alias for moment_date.
descriptionstring–The longer story, in the user's words where possible.
end_datestring–Optional last day YYYY-MM-DD, for a moment that spans days.
event_idstring–A calendar event this story is about (owned, max 128). Links the new moment to it; the event is not changed.
idempotency_keystring–Alias for request_id.
locationstring–Alias for location_name (max 300).
location_namestring–Where it happened, only as the user said it (max 300). With event_id and no place, the event's location is used. Alias: location.
media_urlsarray–Optional https image links (max 10, 2048 characters each).
moment_datestring–When it happened: YYYY-MM-DD, YYYY-MM or YYYY (alias date). With event_id and no date, the event's date is used. Otherwise required.
moment_date_precisionstring–How exact the date is. YYYY-MM and YYYY default to month and year; circa for "around then".
moment_timestring–Optional local time-of-day when it happened (HH:mm or HH:mm:ss). Null/empty = date-only. Not the row created_at.
moment_typestring–Default memory.
people_namesarray–Names the user said (max 25, 120 characters each); tagged only when they match a saved contact (never created). Unmatched names come back in unresolved_people.
person_idsarray–Owned contact ids of people in the story (max 25). An id that isn't the user's saves nothing.
request_idstring–Client idempotency key (retries return original result).
tagsarray–Optional short tags (max 20, 40 characters each).
titlestringyesThe story in a few words (max 200), e.g. "Mia called the moon a banana".
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
inherited_from_eventarrayyesmoment_date and/or location_name, when taken from the linked event.
inspect_notestring–What inspect_url opens. Never quote the record id.
inspect_urlstring–The Dayze page that shows the saved record.
invalidatesarray––
linked_eventobject|nullyesThe event this moment links, unchanged by the call; null when none.
messagestringyes–
momentobjectyesA moment: a story or memory, private to the owner. event_id links the event it is about.
people_taggedarrayyes–
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
unresolved_peoplearrayyespeople_names that matched no saved contact (not tagged, not created).

No examples provided.

log_sleep ~241

Sleep: log overnight or nap. Cross-midnight OK (e.g. 14:00→03:00 = 13h / 780m). ($0.10; API key required)

NameTypeReqDescription
ended_atstringyesISO end
idempotency_keystring–Alias for request_id.
notesstring–Free-text note, e.g. Follow up next week.
qualitynumber–Sleep quality rating, e.g. 4.
request_idstring–Client idempotency key (retries return original result).
sleep_typestring–Sleep record type: overnight, nap or unknown, e.g. overnight.
sourcestring–Where the sleep record came from, e.g. manual.
started_atstringyesISO start
timezonestring–IANA time zone, e.g. America/Los_Angeles.
timezone_endstring–IANA time zone where it ended, e.g. Europe/London.
timezone_startstring–IANA time zone where it started, e.g. Asia/Singapore.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
inspect_notestring–What inspect_url opens. Never quote the record id.
inspect_urlstring–The Dayze page that shows the saved record.
messagestring|null––
okboolean––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
sleepobject––

No examples provided.

log_transaction ~681

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)

NameTypeReqDescription
account_idstring–Stable provider account identity for imported payments.
amountnumberyesPositive money amount.
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–Ledger category (e.g. Salary, Gift, Food & Dining). "IOU repayment" / "IOU lend" / "Invoice payment" need person_id.
client_labelstring–Optional free-text client label for an invoice IOU.
currencystring–ISO 4217 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.
directionstringyesfrom = received, to = paid.
external_idstring–Provider id; dedupes imports.
extractor_versionstring–Extractor/parser version for imports.
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.
message_idstring–Source Gmail message id.
mirror_eventboolean–Also insert optional Money calendar event (default false)
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–Alias for source.
person_idstring–Owned contact id; required for IOU categories. Unknown/other-user id errors and changes nothing.
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, e.g. venmo.
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.
typestring–Transaction type.
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.

reset_tracker ~347

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 } }), which stores the exact change without applying it. After the user confirms, call reset_tracker with preview_id, restore_window_acknowledged: true and request_id; the reviewed preview is applied exactly and a changed record is refused. Returns restore_id; restore_change({ restore_id }) undoes it for 30 days unless the record was edited since. Restore puts back the previous start date, streak and reset count. Requires API key or OAuth with context.delete. Share tokens cannot write. ($0.10; API key required)

NameTypeReqDescription
idempotency_keystring–Alias for request_id.
notestring–Optional note stored in tracking history
preview_idstringyespreview_id returned by preview_destructive_change for this tool.
request_idstringyesRequired idempotency key; retries return the original receipt.
reset_atstring–ISO datetime of the reset (default now)
restore_window_acknowledgedbooleanyesMust be true after reviewing the preview and its 30-day restore window.
titlestring–Alias of tracker_title
tracker_idstring–Event UUID of the tracker
tracker_titlestring–Title match when id unknown
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
errorstring––
idempotent_replayboolean––
invalidatesarray––
life_state_rebuiltboolean––
messagestring––
okboolean––
preview_idstring––
previous_daysnumber––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
reset_datestring––
reset_timestring––
restore_expires_atstring––
restore_idstring–Pass to restore_change to undo within restore_window_days.
restore_window_daysnumber––
reversibleboolean––
tracker_idstring––
tracker_reset_countnumber––
tracker_titlestring|null––

No examples provided.

resolve_pending_reply ~295

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); interaction in the result says what was written. Reopen with update_pending_reply status pending. Requires API key or OAuth with context.write. ($0.05; API key required)

NameTypeReqDescription
idempotency_keystring–Alias for request_id.
outcomestring–How the reply ended: sent or dismissed, e.g. sent.
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–Pending Reply id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
request_idstring–Client idempotency key (retries return original result).
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
already_resolvedbooleanyes–
interactionobject|null–The contact-history write-back of a reply marked sent by this call; null when nothing was marked sent now.
life_state_rebuiltbooleanyes–
messagestringyes–
outcomestringyessent or dismissed
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.
resolvedbooleanyesTrue when this call changed the reply.

No examples provided.

resolve_person ~191

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 omitted unless include_notes=true (redacted). person.lists names the contact lists they are on. 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)

NameTypeReqDescription
include_notesboolean–Include redacted notes (default false)
namestringyesNickname or display name to resolve
querystring–Alias for name
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
aliasesarray––
candidatesarray––
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.
matched_viastring|null––
personobject––
querystring––
resolvedboolean––

No examples provided.

search ~312

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 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. 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). Requires OAuth or a supported scoped credential. ($0.15; API key required)

NameTypeReqDescription
endstring–Alias for to.
entity_typestring–Route a Moment query to search_moments.
fromstring–Inclusive account-local YYYY-MM-DD lower bound for all search routes. May be used alone.
limitnumber–Max results 1–50
qstring–Alias for query.
querystring–Primary search query.
startstring–Alias for from.
tostring–Inclusive account-local YYYY-MM-DD upper bound for all search routes. May be used alone.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
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.
intentstring––
modestringyes–
resultsarrayyes–

No examples provided.

search_moments ~114

Search only owned Moment stories and titles within an optional date range. Returns stable moment_ids. ($0.05; API key required)

NameTypeReqDescription
fromstring–YYYY-MM-DD inclusive
limitinteger–Maximum rows to return, e.g. 20.
offsetinteger–Rows to skip for paging, e.g. 0.
querystringyesWords to match in Moment stories and titles, e.g. Lisbon.
tostring–YYYY-MM-DD inclusive
NameTypeReqDescription
momentsarrayyes–
next_offsetnumber|nullyes–
search_modestringyes–

No examples provided.

search_tools ~175

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)

NameTypeReqDescription
include_coreboolean–When true, also return matches from the default core set. Default false.
limitnumber–Max tools to return (1–50, default 20).
querystring–Case-insensitive match against tool name, title or description. Empty lists toolsets.
toolsetstring–Limit to one opt-in pack id (inventory, finance, crm, …) or "all" for every extra.
NameTypeReqDescription
enable_allobjectyesHow to restore the full expert catalog for this connection.
notestringyes–
querystring|null––
toolsarrayyes–
toolsetstring|null––
toolsetsarrayyes–

No examples provided.

update_event ~730

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 reminder off; needs a timed event to turn on), reminder_minutes_before. Adds a bedtime to a wake-only sleep: event_time (and event_date / end_date when it was the night before). 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)

NameTypeReqDescription
categorystring–Category, e.g. sleep, work
datestring–Alias for event_date
date_precisionstring–Soft date precision stored in metadata
descriptionstring–Notes about the event (replaces). Empty or null clears. Alias: notes.
end_datestring–Optional end date YYYY-MM-DD (multi-day, or a night that ends the next day)
end_timestring–Optional end time (same formats as event_time)
event_datestring–Start date YYYY-MM-DD, YYYY-MM, or YYYY. Alias: date.
event_idstringyesUUID of a calendar event the authenticated user owns
event_timestring–Start time: 8pm, 20:00, or 20:00:00. Empty or null clears. Alias: time.
expected_updated_atstring–Optional ISO updated_at you last read. Write applies only if unchanged; otherwise code "conflict" with the current record and changes nothing.
external_urlstring–Link to the source page, e.g. https://example.com/events/42.
idempotency_keystring–Alias for request_id
image_urlstring–Cover image URL. Empty or null clears.
locationstring–Empty or null clears
notesstring–Alias for description
peoplearray–People names or person UUIDs to add (event_people role=with). Does not remove existing tags.
people_namesarray–Alias: people
person_idsarray–Owned person ids
person_namestring–Person to tag
reminder_enabledboolean–Turn the push reminder on or off. A timed event is needed to turn it on; all-day events stay off.
reminder_minutes_beforenumber–Push lead time in minutes (snapped to 0, 5, 15, 30, 60, 1440 or 10080)
request_idstring–Client idempotency key (retries return original successful result)
scoreboardobject–Status data; state required if new; null clears
timestring–Alias for event_time
timezonestring–IANA timezone for wall-clock display. Empty or null clears.
titlestring–Updated title (replaces). Cannot be empty.
visibilitystring–Updates both events.visibility and the enforced events.is_private flag
witharray–Alias: people
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
changedobjectyesChanged fields with before and after values.
eventobjectyesA Dayze calendar event record.
life_state_rebuiltbooleanyes–
people_taggedarrayyes–
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
unresolved_peoplearrayyes–

No examples provided.

update_food ~646

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)

NameTypeReqDescription
amountnumber–Price if mentioned
append_notesstring–Append text to existing notes (newline-separated)
caloriesnumber–Corrected kcal (0 is real). User-stated unless calories_source is agent_estimate. null or calories_source "unknown" without calories clears to unknown (not zero). Omitted stays, except a corrected wh…
calories_sourcestring–user (default) or agent_estimate. unknown without calories clears the kcal value
consumed_atstring–ISO instant; wins over meal_period
contains_alcoholboolean–Whether it contains alcohol (beer, wine, spirits, cocktails)
currencystring–ISO currency, e.g. SGD
descriptionstring–Alias for what (the dish, not notes).
dish_itemsarray–Complete replacement ordered dish list; [] clears it.
dishesarray–Alias for dish_items.
expense_idstring–Link ONE owned Finance transaction UUID so the meal has one ledger row. Empty or null unlinks; the transaction stays
foodstring–Alias for what.
food_idstringyesUUID of a food diary row the authenticated user owns
idempotency_keystring–Alias for request_id.
itemstring–Alias for what.
kindstring–Meal type, e.g. meal.
meal_periodstring–Spoken period when consumed_at is omitted, e.g. "late lunch"
merchantstring–Restaurant, stall, or shop. Empty or null clears
notesstring–Replaces notes. Empty or null clears
paid_bystring–Who paid: name/alias; "self"/"me" = user (Finance); "unknown" = not known. Empty or null clears. Not a payment method
payment_methodstring–How it was paid (cash, card, PayLah…). Saved on the linked Finance transaction; never changes paid_by
peoplearray–Alias for with
people_namesarray–Alias for with
person_idsarray–Owned person UUIDs to tag (user-scoped)
person_namestring–One companion to add, by name
placestring–Venue or location. Empty or null clears
request_idstring–Client idempotency key (retries return original result).
whatstring–Full updated dish/drink text (replaces, does not append). Example: Salmon Bento + hot tea
witharray–Companion names, aliases, or ids to add (does not remove existing tags)
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
changedobjectyesChanged fields with before and after values.
event_idstring|nullyes–
food_idstringyes–
food_logobjectyesUpdated Food Diary row.
life_state_rebuiltbooleanyes–
linked_expenseobject–PHI-1334: fresh read of the Finance transaction this Food entry is linked to.
payment_method_statusstring––
people_taggedarrayyes–
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
unresolved_peoplearrayyes–

No examples provided.

update_goal ~491

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)

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–Absolute progress in target_unit, not a delta, e.g. 12.
descriptionstring–What the goal is, e.g. Run a half marathon by March.
goal_idstringyesGoal id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
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.
notestring–Progress note stored with this update, e.g. Finished week 3.
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).
statusstring–Goal status: active, in_progress, completed, paused or abandoned, e.g. completed.
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.
titlestring–Goal 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–
messagestringyes–
progress_loggedboolean––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
verifiedboolean––

No examples provided.

update_moment ~543

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 list ([] clears); event_id links an owned event (the event is not changed), empty or null unlinks. Visibility is not an argument. Returns changed_fields. Requires API key or OAuth with context.write. ($0.10; API key required)

NameTypeReqDescription
cover_image_urlstring–https image link (max 2048). Empty or null clears.
datestring–Alias for moment_date.
descriptionstring–Replaces the story text. Empty or null clears.
end_datestring–YYYY-MM-DD. Empty or null clears.
event_idstring–Link the moment to an owned event (the event is not changed, max 128). Empty or null unlinks.
idempotency_keystring–Alias for request_id.
locationstring–Alias for location_name (max 300).
location_namestring–Replaces the place (max 300). Empty or null clears. Alias: location.
media_urlsarray–Replaces the image links (max 10). [] clears.
moment_datestring–YYYY-MM-DD, YYYY-MM or YYYY (alias date).
moment_date_precisionstring–How exact the date is. YYYY-MM and YYYY default to month and year; circa for "around then".
moment_idstringyesUUID of a moment the user owns (from log_moment, max 128).
moment_timestring–Optional local HH:mm or HH:mm:ss. Empty or null clears (date-only).
moment_typestring–Default memory.
people_namesarray–Replaces the tagged people (with person_ids, max 25, 120 characters each); names match saved contacts only.
person_idsarray–Replaces the tagged people (with people_names, max 25). [] clears. Owned contact ids only.
request_idstring–Client idempotency key (retries return original result).
tagsarray–Replaces the tags (max 20, 40 characters each). [] clears.
titlestring–New title (max 200). Cannot be empty.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
changed_fieldsarrayyesThe columns this call changed; empty when nothing differed.
invalidatesarray––
messagestringyes–
momentobjectyesA moment: a story or memory, private to the owner. event_id links the event it is about.
people_taggedarrayyes–
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
unresolved_peoplearrayyes–

No examples provided.

update_pending_reply ~523

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 key or OAuth with context.write. ($0.10; API key required)

NameTypeReqDescription
categorystring–Reply category: personal or work, e.g. work.
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–Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
person_namestring–Contact name when there is no person_id, e.g. Alex Chen.
received_atstring–When the message arrived, as ISO date-time, e.g. 2026-10-17T15:30:00Z.
reply_idstringyesFrom create_pending_reply or get_pending_replies.
request_idstring–Client idempotency key (retries return original result).
snooze_untilstring–ISO date-time, with status snoozed.
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.
statusstring–Reply state, e.g. unsent.
summarystring–One line (max 280) in your own words: what the reply is about. Never paste the email body, subject line or sender address.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
changed_fieldsarrayyes–
life_state_rebuiltbooleanyes–
messagestringyes–
person_linkobject|null–Whether 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_savedbooleanyes–

No examples provided.

update_person ~775

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)

NameTypeReqDescription
addressstring|null–Postal address (one line). Null or blank clears
birth_timestring|null–HH:MM 24-hour. Null clears
birthdaystring–YYYY, YYYY-MM, YYYY-MM-DD, or MM-DD / --MM-DD (year unknown; 02-29 ok). Null/empty clears
cadence_daysinteger|null–Check-in every N days; null or 0 turns check-ins off. Next check-in is recomputed
companystring|null–company. Omit to leave unchanged; null or blank clears.
contact_originstring–Personal relationship, found online, or imported.
context_tagsarray–Custom context labels; [] clears.
death_datestring|null–YYYY-MM-DD; marks the contact deceased. Null clears
discovery_sourcestring|null–Where found, e.g. Facebook suggestions. Null clears.
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.
expected_updated_atstring–Optional ISO updated_at you last read. Write applies only if unchanged; otherwise code "conflict" with the current record and changes nothing.
first_metstring|null–When/how they first met (free text). Null or blank clears
first_met_locationstring|null–Where they first met. Null or blank clears
genderstring|null–Null or blank clears
hobbiesarray–Replace list; [] clears; omit to keep. Read before adding.
idempotency_keystring–Alias for request_id.
interestsarray–Replace list; [] clears; omit to keep. Read before adding.
is_deceasedboolean–false also clears death_date and the memorial reminder
is_favoriteboolean–Favorite; includes contact in inner_circle.
last_interaction_atstring–Owner correction: YYYY-MM-DD or zoned ISO time; not future.
locationsarray–Merge by id; omitted entries/fields stay. City or approximate area suffices. Never infer a residence.
namestring–Rename and refresh slug; use for spelling fixes.
notesstring–Replaces people.notes (does not append). Empty or null clears
occupationstring|null–Occupation / job title. Omit to leave unchanged; null or blank clears.
person_idstringyesOwned contact UUID.
phonestring|null–phone. Omit to leave unchanged; null or blank clears.
preserve_old_name_as_aliasboolean–Keep old name as former_name alias; default true.
pronounsstring|null–e.g. she/her. Null or blank clears
relationshipstring–Relationship label (friend, sister, …). Empty or null clears
relationshipsarray–Primary-first labels; [] clears.
remove_education_idsarray–Explicitly remove only these school entry ids; legacy summary stays.
remove_location_idsarray–Explicitly remove only these location ids.
request_idstring–Reuse for retries.
sexual_orientationstring|null–Private. Null or blank clears
tierstring–Priority; VIP stays in inner_circle.
walletsarray–ENS/SNS names or addresses. [] clears wallets; other social handles stay.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
change_idstring–Pass to undo_contact_change to revert this change, birthday and birthday_precision included.
changedobjectyesChanged fields with before and after values.
former_name_aliasobject–After a rename that keeps the old name (preserve_old_name_as_alias, default true): alias, saved, and reason when it could not be kept.
hintstring–Where the not_applied fields are changed instead (the Dayze profile).
is_selfboolean–True when the person is the user's own card (Me).
life_state_rebuiltbooleanyes–
not_appliedarray––
personobjectyesA Dayze person or contact record.
provenanceobject–Which connector wrote the record and which connected Dayze account received it.

No examples provided.

update_sleep ~251

Sleep: patch an existing sleep record by sleep_id. ($0.10; API key required)

NameTypeReqDescription
ended_atstring–End as ISO date-time, e.g. 2026-10-17T07:00:00+08:00.
idempotency_keystring–Alias for request_id.
notesstring–Free-text note, e.g. Follow up next week.
qualitynumber–Sleep quality rating, e.g. 4.
request_idstring–Client idempotency key (retries return original result).
sleep_idstringyesSleep record id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
sleep_typestring–Sleep record type: overnight, nap or unknown, e.g. overnight.
started_atstring–Start as ISO date-time, e.g. 2026-10-16T23:00:00+08:00.
timezonestring–IANA time zone, e.g. America/Los_Angeles.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
messagestring|null––
okboolean––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
sleepobject––

No examples provided.

upload_photo ~541

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. Answers attached: true only after readback confirms asset id, content_type, byte_size, and a viewable URL on the record — never from OCR text alone. Mobile file references without download_url fail clearly (attached: false). Person uploads also write the CRM gallery (person_photos) and avatar when set_as_avatar=true. ($0.15; API key required)

NameTypeReqDescription
asset_idstring–Repair saved upload: new request_id, no image bytes.
attachment_idstring–Alias for file_id (ChatGPT attachment id).
content_typestring–MIME type of the image, e.g. image/jpeg.
descriptionstring–Caption for the photo, e.g. Receipt from lunch.
entity_idstringyesRecord id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
entity_typestringyesType of the record the id refers to, e.g. event.
file_idstring–ChatGPT file / attachment id from the chat file bridge (not a Dayze asset_id). Pair with image or a ChatGPT file-storage url.
filenamestring–Original file name, e.g. receipt.jpg.
idempotency_keystring–Alias for request_id.
imageobject–ChatGPT chat attachment. Prefer this for images from the conversation; API clients may still use image_base64 or url.
image_base64string–Base64 image bytes (optional data: URL prefix).
mime_typestring–Alias for content_type.
request_idstring–Client idempotency key (retries return original result).
rolestring–original | cover | thumbnail | receipt | … (photo is stored as original). set_as_avatar implies cover.
set_as_avatarboolean–Also use this photo as the contact avatar, e.g. true.
titlestring–Photo title, e.g. Receipt from lunch.
urlstring–Remote image URL to fetch and store.
NameTypeReqDescription
accountobject–The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
assetobject––
asset_idstring––
attachedboolean––
avatar_updatedboolean––
byte_sizenumber––
content_typestring––
entity_idstring––
entity_typestring––
messagestring|null––
metadata_strippedboolean––
optimizedobject––
photo_idstring|null––
provenanceobject–Which connector wrote the record and which connected Dayze account received it.
urlstring|null––
view_urlstring––

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/key, 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/key'
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/key).

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.