Dayze — Life Context
REMOTE · DAYZE.COM · 2 COMPONENTS · SCANNED SEP 25
Life context for agents: get_context_pack + public notable packs. x402 + OAuth.
Available components
Recent critical change
Authorization (18 Sept 2026). See the changelog before you install this server.
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_food). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 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 15748 tokens (~119/item across 132 items; 129 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 Management45
- Stability check failed: schema churn in the 14 days we've observed: 0 tool removals, 2 breaking changes, 1 auth/transport breaks, 42 additions. See how to fix → Fail
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
- 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
- All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 131 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
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
claude mcp add --transport http com-dayze-life-context 'https://dayze.com/api/mcp/key'
{
"mcpServers": {
"com-dayze-life-context": {
"url": "https://dayze.com/api/mcp/key"
}
}
} {
"servers": {
"com-dayze-life-context": {
"type": "http",
"url": "https://dayze.com/api/mcp/key"
}
}
} [mcp_servers.com-dayze-life-context] url = "https://dayze.com/api/mcp/key"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dayze-life-context": {
"type": "remote",
"url": "https://dayze.com/api/mcp/key",
"enabled": true
}
}
} openclaw mcp add com-dayze-life-context --url 'https://dayze.com/api/mcp/key' --transport streamable-http
mcp_servers:
com-dayze-life-context:
url: "https://dayze.com/api/mcp/key" {
"McpServers": {
"com-dayze-life-context": {
"Transport": "http",
"Url": "https://dayze.com/api/mcp/key"
}
}
} assistant mcp add com-dayze-life-context -t streamable-http -u 'https://dayze.com/api/mcp/key'
{
"mcpServers": {
"com-dayze-life-context": {
"type": "http",
"url": "https://dayze.com/api/mcp/key"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 35 to 38.
- 22 Sept 26 0
- Tool “get_interactions” rewrote its description, which is the text the model reads security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 28 to 32.
- 20 Sept 26 0
- New tool “get_interactions” functional
- 18 Sept 26 −10
- Authorization: Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_food). critical
- Tool “archive_event” is now declared destructive security
- Tool “archive_expense” is now declared destructive security
- Tool “archive_trip” is now declared destructive security
- Tool “bulk_dismiss_clarifications” is now declared destructive security
- Tool “cleanup_apply” is now declared destructive security
- Tool “commit_life_update” is now declared destructive security
- Tool “convert_contact_entity” is now declared destructive security
- Tool “delete_event” is now declared destructive security
- Tool “normalize_people_apply” is now declared destructive security
- Tool “reset_tracker” is now declared destructive security
- Tool “start_people_cleanup” is now declared destructive security
- Tool “undo_contact_change” is now declared destructive security
- Server version: 1.32.1 → 1.33.0 functional
- “cleanup_preview” added an optional parameter “idempotency_key” cosmetic
- “cleanup_preview” added an optional parameter “request_id” cosmetic
- “normalize_people_preview” added an optional parameter “idempotency_key” cosmetic
- “normalize_people_preview” added an optional parameter “request_id” cosmetic
- “update_event” reworded the description of “request_id” cosmetic
- 17 Sept 26 +1
- Stability: 0.17 → fail ▼ security
- Tool “update_person” rewrote its description, which is the text the model reads security
- Tool “undo_contact_change” rewrote its description, which is the text the model reads security
- Tool “start_people_cleanup” rewrote its description, which is the text the model reads security
- Tool “resolve_person” rewrote its description, which is the text the model reads security
- Tool “merge_people_preview” rewrote its description, which is the text the model reads security
- Tool “merge_people” rewrote its description, which is the text the model reads security
- Tool “get_people” rewrote its description, which is the text the model reads security
- Tool “delete_event” rewrote its description, which is the text the model reads security
- Tool “create_person” rewrote its description, which is the text the model reads security
- Tool “delete_event” no longer declares itself destructive security
- “normalize_people_apply” added a required parameter “candidate_hash”, so existing callers break ▼ functional
- “merge_people” added a required parameter “restore_window_acknowledged”, so existing callers break ▼ functional
- “merge_people” added a required parameter “preview_id”, so existing callers break ▼ functional
- “normalize_people_apply” made “request_id” required, so existing callers break ▼ functional
- “delete_event” made “request_id” required, so existing callers break ▼ functional
- Destructive annotations: All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Server version: 1.30.2 → 1.32.1 functional
- New tool “restore_trip” functional
- New tool “restore_expense” functional
- New tool “restore_event” functional
- New tool “restore_cleanup” functional
- New tool “cleanup_preview” functional
- New tool “cleanup_apply” functional
- New tool “archive_trip” functional
- New tool “archive_expense” functional
- New tool “archive_event” functional
- “search_transactions” added an optional parameter “include_archived” cosmetic
- “search_transactions” added an optional parameter “cursor” cosmetic
- “merge_people_preview” added an optional parameter “request_id” cosmetic
- “merge_people_preview” added an optional parameter “idempotency_key” cosmetic
- “log_transaction” added an optional parameter “message_id” cosmetic
- “log_transaction” added an optional parameter “extractor_version” cosmetic
- “log_transaction” added an optional parameter “account_id” cosmetic
- “get_trips” added an optional parameter “include_archived” cosmetic
- “get_trips” added an optional parameter “cursor” cosmetic
- “get_transactions” added an optional parameter “include_archived” cosmetic
- “get_transactions” added an optional parameter “cursor” cosmetic
- “get_people” added an optional parameter “cursor” cosmetic
- “get_events” added an optional parameter “limit” cosmetic
- “get_events” added an optional parameter “include_archived” cosmetic
- “get_events” added an optional parameter “cursor” cosmetic
- “normalize_people_apply” reworded the description of “request_id” cosmetic
- Tool “update_person” changed its title: Update Person (CRM write) → Update Contact (CRM write) cosmetic
- Tool “resolve_person” changed its title: Resolve Person → Resolve Contact cosmetic
- Tool “get_people” changed its title: User Contacts → Dayze Contacts cosmetic
- Tool “create_person” changed its title: Create Person → Create Contact cosmetic
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 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. | present | 19718 | 13 | Verified |
| dayze.com. | absent | 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 |
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 →
notable_profile Notable Person Profile ~71
Bio-only profile JSON by slug (no life-in-days, similar, or birthday peers). Prefer notable_pack for “who is X / age in days / peers”. Example: taylor-swift. ($0.02)
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Person slug, e.g. albert-einstein |
| Name | Type | Req | Description |
|---|---|---|---|
| about | string|null | – | – |
| bio | string|null | – | – |
| birth_date | string|null | – | – |
| death_date | string|null | – | – |
| handle | string|null | – | – |
| image_url | string|null | – | – |
| name | string | yes | – |
| occupation | string|null | – | – |
| profile_url | string | yes | – |
| slug | string | yes | – |
| sources | array | – | – |
| timeline | array | – | – |
No examples provided.
notable_search Search Notable People ~52
Search the public Dayze notable-people catalog by name, occupation, or slug. Use when you need to find a person before fetching a pack. Example slug: albert-einstein. ($0.01)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| total | number | yes | Number of matches returned. |
No examples provided.
propose_life_update Propose Life Update ~106
Propose assertion create/correct without committing (flagged; off by default). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | – | – |
| idempotency_key | string | – | – |
| operations | array | – | – |
| people_id | string | – | – |
| person_id | string | – | – |
| predicate | string | – | – |
| request_id | string | – | – |
| source_text | string | – | – |
| value | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | – |
| message | string|null | – | – |
| payload_hash | string | – | – |
| proposal_id | string | – | – |
No examples provided.
read_gmail_attachment Read Gmail Attachment (read-only) ~110
Download one Gmail attachment by message_id + attachment_id (from read_gmail_message.attachments). Returns utf-8 text for text/csv/vcf/vcard; binary types return filename/mime/size + a note (no base64 dump). Optional account. Read-only. Share tokens cannot call. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| attachment_id | string | yes | – |
| string | – | – | |
| message_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| attachment | object | yes | – |
| message_id | string | yes | – |
No examples provided.
read_gmail_message Read Gmail Message (read-only) ~149
Read one Gmail message by id from search_gmail. Returns subject, from, canonical date, account-local date_local, time_zone, snippet, plain-text body (truncated), and attachments[] metadata (attachment_id, filename, mime_type, size). Use read_gmail_attachment for text/csv/vcf contents. Optional account when multiple mailboxes. Read-only. Share tokens cannot call. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Mailbox selector (email or connection id) |
| string | – | Alias for account | |
| id | string | – | Alias for message_id |
| message_id | string | yes | Gmail message id from search_gmail |
| Name | Type | Req | Description |
|---|---|---|---|
| message | object | yes | – |
No examples provided.
record_purchase Record Purchase ~86
Atomic expense + optional inventory item creation. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| currency | string | – | – |
| date | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| name | string | yes | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| expense_id | string|null | – | – |
| inventory_id | string|null | – | – |
| message | string|null | – | – |
| transaction | object | – | Expense/income transaction row. |
No examples provided.
record_sale Record Sale ~92
Mark inventory sold + record sale proceeds with gain/loss. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| currency | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| inventory_id | string | yes | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| sold_at | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| expense_id | string|null | – | – |
| inventory_id | string | – | – |
| message | string|null | – | – |
| realized_gain_loss | string|null | – | – |
No examples provided.
remove_person_alias Remove Person Alias ~74
Remove one alias from a CRM person. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| person_id | string | yes | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | – | – |
| change_id | string|null | – | – |
| message | string|null | – | – |
| person_id | string | – | – |
| removed | boolean | – | – |
No examples provided.
reset_tracker Reset Streak Tracker ~184
MUTATES a sobriety/streak tracker for the authenticated user (sets current value to 0 and restarts the clock). Prefer tracker_id from get_trackers, or tracker_title fuzzy match. Optional reset_at (ISO) and note. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| note | string | – | Optional note stored in tracking history |
| request_id | string | – | Client idempotency key (retries return original result). |
| reset_at | string | – | ISO datetime of the reset (default now) |
| title | string | – | Alias of tracker_title |
| tracker_id | string | – | Event UUID of the tracker |
| tracker_title | string | – | Title match when id unknown |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| invalidates | array | – | – |
| life_state_rebuilt | boolean | – | – |
| message | string | – | – |
| ok | boolean | – | – |
| previous_days | number | – | – |
| reset_date | string | – | – |
| reset_time | string | – | – |
| tracker_id | string | – | – |
| tracker_reset_count | number | – | – |
| tracker_title | string|null | – | – |
No examples provided.
resolve_clarification Resolve Clarification ~85
Link a clarification surface to an existing person. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| clarification_id | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| person_id | string | – | – |
| person_name | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string|null | – | – |
| person_id | string | – | – |
| resolved | boolean | – | – |
No examples provided.
resolve_person Resolve Contact ~151
Resolve a nickname or surface name to a Dayze Contacts row via person_aliases → exact name → slug → unique substring. Returns avatar_url, photo_count, has_photos, and photos[{url,is_primary}] preview; use get_person_photos for full gallery. Notes omitted unless include_notes=true (redacted). Prefer this before money or relationship tools when the agent only has a nickname. Advertised name resolve_person is stable; tools/call also accepts resolve_contact. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| include_notes | boolean | – | Include redacted notes (default false) |
| name | string | yes | Nickname or display name to resolve |
| query | string | – | Alias for name |
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | – | – |
| candidates | array | – | – |
| matched_via | string|null | – | – |
| person | object | – | – |
| query | string | – | – |
| resolved | boolean | – | – |
No examples provided.
resolve_place Resolve Place ~51
Canonicalize a venue name via place aliases and fuzzy match. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| place | string | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | – | – |
| matched_via | string|null | – | – |
| place | object|null | – | Canonical place record. |
| query | string | yes | – |
| resolved | boolean | yes | – |
No examples provided.
restore_cleanup restore cleanup ~71
Restore an archive or normalization receipt. Requires restore_id and request_id. Refuses intervening edits; repeats are no-ops. ($0; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | yes | – |
| restore_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_hash | string | – | – |
| changed | boolean | – | – |
| expires_at | string | – | – |
| preview_id | string | – | – |
| restore_id | string | – | – |
| rows | array | – | – |
| server_time | string | – | – |
No examples provided.
restore_event restore event ~71
Restore an archive or normalization receipt. Requires restore_id and request_id. Refuses intervening edits; repeats are no-ops. ($0; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | yes | – |
| restore_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_hash | string | – | – |
| changed | boolean | – | – |
| expires_at | string | – | – |
| preview_id | string | – | – |
| restore_id | string | – | – |
| rows | array | – | – |
| server_time | string | – | – |
No examples provided.
restore_expense restore expense ~72
Restore an archive or normalization receipt. Requires restore_id and request_id. Refuses intervening edits; repeats are no-ops. ($0; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | yes | – |
| restore_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_hash | string | – | – |
| changed | boolean | – | – |
| expires_at | string | – | – |
| preview_id | string | – | – |
| restore_id | string | – | – |
| rows | array | – | – |
| server_time | string | – | – |
No examples provided.
restore_trip restore trip ~71
Restore an archive or normalization receipt. Requires restore_id and request_id. Refuses intervening edits; repeats are no-ops. ($0; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | yes | – |
| restore_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_hash | string | – | – |
| changed | boolean | – | – |
| expires_at | string | – | – |
| preview_id | string | – | – |
| restore_id | string | – | – |
| rows | array | – | – |
| server_time | string | – | – |
No examples provided.
score_people_duplicates Score People Duplicates ~59
Score likely CRM duplicate pairs before merge_people. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| min_probability | number | – | – |
| person_id | string | – | Score against one person; omit for global scan. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | – |
| count | number | yes | – |
No examples provided.
search Semantic Life Search ~101
Search the authenticated user life graph. Deterministic routing first: food + relative dates (e.g. "what did I eat yesterday?"); timeline/current-context; money+person; who-is → resolve_person. Otherwise semantic/keyword search. Event hits include event_date and food_id when mirrored from Food Diary. Browser-history titles are excluded. Credential/secret spans are redacted. Requires OAuth or a supported scoped credential. ($0.15; API key required)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | – | – |
| mode | string | yes | – |
| results | array | yes | – |
No examples provided.
search_gmail Search Gmail (read-only) ~343
Search one of the authenticated user's connected Gmail inboxes (read-only). Reuses Integrations hub Gmail (service_connections provider=gmail). Optional account/email selects a mailbox when multiple are connected — call list_gmail_accounts first. Prefer Gmail operators: from:, subject:, is:unread, newer_than:7d, has:attachment. For clock-time constraints, pass after/before as account-local civil datetimes; the tool converts them to precise UTC instants. Returns id, subject, from, canonical date, account-local date_local, time_zone, and snippet only (no body). Follow up with read_gmail_message. Cannot send, archive, or delete. Never invent email contents. If Gmail is not connected, connect at /integrations. Requires API key or OAuth with scope context. Share tokens cannot call this tool. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Mailbox email, connection id, or Google subject (from list_gmail_accounts) |
| after | string | – | Exclusive lower bound as account-local YYYY-MM-DDTHH:mm, or an offset-aware ISO instant |
| before | string | – | Exclusive upper bound as account-local YYYY-MM-DDTHH:mm, or an offset-aware ISO instant |
| string | – | Alias for account | |
| max_results | number | – | Max messages to return (default 10, max 20) |
| q | string | – | Alias for query |
| query | string | yes | Gmail search query, e.g. "is:unread newer_than:7d", "from:airline subject:itinerary", "receipt newer_than:30d" |
| Name | Type | Req | Description |
|---|---|---|---|
| account | string|null | – | – |
| after | string | – | – |
| before | string | – | – |
| messages | array | yes | – |
| query | string | yes | – |
| result_size_estimate | number|null | yes | – |
| time_zone | string | yes | – |
No examples provided.
search_inventory Search Inventory ~56
Search owned inventory by name/brand/model/notes. Returns photo_count, has_photos, cover_url; when empty, photo_hint explains upload_asset linkage. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| items | array | – | – |
| query | string|null | – | – |
No examples provided.
search_photos Search Photos ~72
Search person photos and entity assets by query/metadata. Returns inline MCP image attachments. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| person_ids | array | – | – |
| place_id | string | – | – |
| query | string | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| photos | array | – | – |
| query | string|null | – | – |
No examples provided.
search_transactions Search Transactions ~93
Keyword search over merchant/description/category, or exact tag query (project:/ext:/rail:). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Continue the same immutable one-hour snapshot; other filters remain frozen. |
| include_archived | boolean | – | – |
| limit | number | – | – |
| project | string | – | – |
| query | string | – | – |
| tag | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| query | string | – | – |
| transactions | array | – | – |
No examples provided.
set_primary_person_name Set Primary Person Name ~122
Rename a CRM contact’s canonical name and refresh slug. By default preserves the old name as a former_name alias. Prefer this over create+merge for spelling fixes. Dayze is the context layer — bounded mutation only. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| name | string | yes | – |
| person_id | string | yes | – |
| preserve_old_name_as_alias | boolean | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | string|null | – | – |
| message | string|null | – | – |
| person | object | – | CRM person record. |
| previous_name | string | – | – |
No examples provided.
start_people_cleanup Start People Cleanup ~94
Server-side read-only cleanup audit. Returns a review queue; never automatically merges contacts. Use normalize_people_preview/apply for reversible normalization. ($0.15; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| auto_merge_threshold | number | – | – |
| checks | array | – | – |
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| auto_merged_count | number | – | – |
| cleanup_id | string | – | – |
| items_needing_approval | number | – | – |
| message | string|null | – | – |
| status | string | – | – |
No examples provided.
undo_contact_change Undo Contact Change ~101
Reverse a reversible contact_mutations row (rename, alias, identity, classify, link). For merges, pass restore_id as change_id within 30 days. Restore rejects later edits rather than overwriting them. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | string | – | – |
| message | string|null | – | – |
| undone | boolean | – | – |
No examples provided.
unlink_people Unlink People ~84
Remove a person↔person graph edge. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| other_person_id | string | – | – |
| person_id | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string|null | – | – |
| unlinked | boolean | – | – |
No examples provided.
update_asset Update Asset ~128
Patch role, metadata, description, or parent_asset_id (e.g. mark as processed). ($0.08; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | – |
| asset_type | string | – | – |
| description | string | – | – |
| filename | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| metadata | object | – | – |
| parent_asset_id | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| role | string | – | original | cover | thumbnail | … |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | object | – | – |
| asset_id | string | – | – |
| message | string|null | – | – |
| updated | boolean | – | – |
No examples provided.
update_current_location Update Current Location ~250
MUTATES where the user is now: profiles.location + polaris current_city/country (same as in-app Dayze chat). Pass location ("The Madeira, Singapore") and/or city+country; optional place/venue + lat/lon records a fresh location_visits check-in so get_location_context returns is_current. set_home defaults true; check_in defaults true when place or coordinates are set. Does not invent GPS when omitted. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| check_in | boolean | – | Write a location_visits row when place or coordinates are set (default true in that case) |
| city | string | – | – |
| country | string | – | – |
| idempotency_key | string | – | – |
| latitude | number | – | – |
| location | string | – | Freeform “City, Country” or “Venue, City, Country” |
| longitude | number | – | – |
| place | string | – | Venue / residence name (e.g. The Madeira) |
| request_id | string | – | – |
| set_home | boolean | – | Also write profiles.location / home_location (default true) |
| venue | string | – | Alias for place |
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | boolean | – | – |
| context | object | – | Fresh get_location_context after write. |
| current_city | string|null | – | – |
| current_country | string|null | – | – |
| location | string|null | – | – |
| message | string | – | – |
| place | string|null | – | – |
| set_home | boolean | – | – |
| updated | boolean | – | – |
| visit_id | string|null | – | – |
No examples provided.
update_event Update Event (calendar patch) ~455
MUTATES one existing calendar event the authenticated user owns. Required: event_id (UUID). Optional patch (same fields as log_event): title, date / event_date, time / event_time, end_date, end_time, location, description, category, external_url, people / with / person_ids. Unknown or other-user event_id returns an error and does not create a row. For food-diary meals, prefer update_food (it syncs the mirrored event). Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | e.g. funeral, family, work, travel. Stored as events.category and event_type. |
| date | string | – | Alias for event_date. |
| date_precision | string | – | Soft date precision stored in metadata. |
| description | string | – | Empty or null clears |
| end_date | string | – | Optional end date YYYY-MM-DD (all-day multi-day). |
| end_time | string | – | Optional end time (same formats as event_time). |
| event_date | string | – | Start date YYYY-MM-DD, YYYY-MM, or YYYY. Alias: date. |
| event_id | string | yes | UUID of a calendar event the authenticated user owns |
| event_time | string | – | Start time: 8pm, 20:00, or 20:00:00. Empty or null clears. Alias: time. |
| external_url | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| location | string | – | Empty or null clears |
| people | array | – | People names or person UUIDs to add (event_people role=with). Does not remove existing tags. |
| people_names | array | – | – |
| person_ids | array | – | Owned person UUIDs to tag (user-scoped). |
| person_name | string | – | – |
| request_id | string | – | Client idempotency key (retries return original successful result). |
| time | string | – | Alias for event_time. |
| title | string | – | Updated title (replaces). Cannot be empty. |
| with | array | – | Alias for people. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | object | yes | Changed fields with before and after values. |
| event | object | yes | A Dayze calendar event record. |
| life_state_rebuilt | boolean | yes | – |
| people_tagged | array | yes | – |
| unresolved_people | array | yes | – |
No examples provided.
update_expense Update Expense ~187
PATCH an expense row. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | – |
| category | string | – | – |
| currency | string | – | – |
| date | string | – | YYYY-MM-DD expense_date |
| description | string | – | – |
| expense_id | string | yes | – |
| external_id | string | – | Optional; merges ext:{source}:{id} into tags |
| idempotency_key | string | – | Alias for request_id. |
| merchant | string | – | – |
| notes | string | – | – |
| payment_method | string | – | e.g. venmo, cash, card |
| project | string | – | Venture label → project:{slug} tag |
| request_id | string | – | Client idempotency key (retries return original result). |
| source | string | – | Alias of payment_method |
| tags | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | object | – | – |
| expense | object | – | Expense/income transaction row. |
| message | string|null | – | – |
No examples provided.
update_food Update Food (diary patch) ~453
MUTATES one existing Food Diary row the authenticated user owns. Required: food_id (UUID). Optional patch (same fields as log_food): what, kind, place, merchant, notes, append_notes (concat), consumed_at (ISO instant) / meal_period (profile TZ), amount, currency, paid_by / payment_method, with / people_names / person_ids. Example: add hot tea onto an existing Salmon Bento → update_food({ food_id, what: "Salmon Bento + hot tea" }). Unknown or other-user food_id returns an error and does not create a row. Syncs the mirrored calendar event and rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Price if mentioned |
| append_notes | string | – | Append text to existing notes (newline-separated) |
| consumed_at | string | – | ISO instant; wins over meal_period |
| currency | string | – | ISO currency, e.g. SGD |
| food_id | string | yes | UUID of a food diary row the authenticated user owns |
| idempotency_key | string | – | Alias for request_id. |
| kind | string | – | – |
| meal_period | string | – | Spoken period when consumed_at is omitted, e.g. "late lunch" |
| merchant | string | – | Restaurant, stall, or shop. Empty or null clears |
| notes | string | – | Replaces notes. Empty or null clears |
| paid_by | string | – | Who paid (name or alias) |
| payment_method | string | – | Alias of paid_by for expense-style agents |
| people_names | array | – | Alias for with |
| person_ids | array | – | Owned person UUIDs to tag (user-scoped) |
| place | string | – | Venue or location. Empty or null clears |
| request_id | string | – | Client idempotency key (retries return original result). |
| what | string | – | Full updated dish/drink text (replaces, does not append). Example: Salmon Bento + hot tea |
| with | array | – | Companion names, aliases, or ids to add (does not remove existing tags) |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | object | yes | Changed fields with before and after values. |
| event_id | string|null | yes | – |
| food_id | string | yes | – |
| food_log | object | yes | Updated Food Diary row. |
| life_state_rebuilt | boolean | yes | – |
| people_tagged | array | yes | – |
| unresolved_people | array | yes | – |
No examples provided.
update_inventory_item Update Inventory Item ~243
PATCH semantics — unspecified fields untouched. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| category | string | – | Broad type: clothing, instruments, electronics, … |
| condition | string | – | – |
| estimated_value | number | – | – |
| idempotency_key | string | – | Alias for request_id. |
| inventory_id | string | yes | – |
| item_type | string | – | Alias for subtype. |
| location | string | – | – |
| model | string | – | – |
| name | string | – | What the user naturally calls the item. |
| notes | string | – | – |
| purchase_price | number | – | – |
| reference_number | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| serial_number | string | – | – |
| status | string | – | – |
| subtype | string | – | Specific subtype (sweatshirt, jacket, guitar). Alias: item_type. |
| subtype_confidence | number | – | 0–1 confidence when subtype is uncertain (agent_inferred). |
| tags | array | – | Replace tags array (sanitized against category mismatches). |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | object | – | – |
| item | object | – | Inventory item record. |
| message | string|null | – | – |
No examples provided.
update_notable Update Notable (catalog write) ~240
MUTATES public notable_people. Superuser only. Patch by slug (bio, about, occupation, birth_place, birth_date, net_worth, residence, before_fame, trivia, family_life, zodiac, flag). Rejects unknown fields. No create/delete. Stamps last_updated_via=mcp. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | – |
| before_fame | string | – | – |
| bio | string | – | – |
| birth_date | string | – | YYYY, YYYY-MM, or YYYY-MM-DD. Null/empty clears |
| birth_place | string | – | – |
| family_life | string | – | – |
| flag | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| net_worth | string | – | – |
| occupation | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| residence | string | – | – |
| slug | string | yes | Notable person slug (e.g. taylor-swift) |
| trivia | string | – | – |
| zodiac | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | object | yes | Changed fields with before and after values. |
| person | object | yes | Updated notable catalog row (name, slug). |
No examples provided.
update_people_link Update People Link ~121
Patch an existing person↔person graph edge (type/context/source/confidence). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| connection_id | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| notes | string | – | – |
| other_person_id | string | – | – |
| person_id | string | – | – |
| relationship_type | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| connection | object | – | – |
| message | string|null | – | – |
| updated | boolean | – | – |
No examples provided.
update_person Update Contact (CRM write) ~380
MUTATES Dayze Contacts. Patch one existing contact the user owns (person_id UUID required). Optional fields: name (renames + refreshes slug), is_favorite, tier (vip|normal|low), relationship, notes (replaces stored notes — read first if you need to append), birthday (YYYY|YYYY-MM|YYYY-MM-DD|MM-DD|--MM-DD or null to clear; MM-DD stores month_day precision). Rejects unknown fields. Does not create or delete contacts. Rebuilds life_state so the next get_context_pack inner_circle is fresh. Advertised name update_person is stable; tools/call also accepts update_contact. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| birthday | string | – | YYYY, YYYY-MM, YYYY-MM-DD, or MM-DD / --MM-DD (year unknown). Null/empty clears |
| idempotency_key | string | – | Alias for request_id. |
| is_favorite | boolean | – | Favorite flag. Favorites (and VIP) appear in get_context_pack inner_circle |
| name | string | – | Rename contact (also refreshes URL slug). Prefer this over create+merge for spelling fixes |
| notes | string | – | Replaces people.notes (does not append). Empty or null clears |
| person_id | string | yes | UUID of a person the authenticated user owns |
| preserve_old_name_as_alias | boolean | – | When renaming, keep the previous name as a former_name alias (default true) |
| relationship | string | – | Relationship label (friend, sister, …). Empty or null clears |
| request_id | string | – | Client idempotency key (retries return original result). |
| tier | string | – | Relationship priority. VIP stays in inner_circle even when not favorited |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | object | yes | Changed fields with before and after values. |
| life_state_rebuilt | boolean | yes | – |
| person | object | yes | A Dayze person or contact record. |
No examples provided.
update_person_alias Update Person Alias ~99
Update alias_kind/source/display for an existing alias. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | – |
| alias_display | string | – | – |
| alias_kind | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| person_id | string | yes | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| alias | object | – | – |
| change_id | string|null | – | – |
| message | string|null | – | – |
| person_id | string | – | – |
No examples provided.
update_person_identity Update Person Identity ~159
Patch identity fields (legal/preferred name, pronouns, social handles, user_relationships[]). Never infer sensitive identity from appearance. Confirmed user_relationships are preserved unless force=true. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | – | – |
| force | boolean | – | – |
| idempotency_key | string | – | Alias for request_id. |
| legal_name | string | – | – |
| person_id | string | yes | – |
| preferred_name | string | – | – |
| pronouns | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| social_handles | object | – | – |
| user_relationships | array | – | – |
| website | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | string|null | – | – |
| changed | object | – | – |
| message | string|null | – | – |
| person | object | – | – |
No examples provided.
update_place Update Place Card ~240
Patch a saved place card by place_id / business_contact_id. Unspecified fields stay unchanged (hours, affordability, address, notes, …). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| affordability | string | – | – |
| area | string | – | – |
| business_contact_id | string | – | – |
| category | string | – | – |
| city | string | – | – |
| country | string | – | – |
| description | string | – | – |
| hours | string | – | – |
| hours_source | string | – | – |
| id | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | – | – |
| notes | string | – | – |
| opening_hours | string | – | – |
| phone | string | – | – |
| phone_numbers | array | – | – |
| place_id | string | – | – |
| price_level | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| tags | array | – | – |
| website | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| business_contact_id | string | – | – |
| message | string|null | – | – |
| place | object | – | Saved place card. |
| place_id | string | – | – |
| updated | boolean | – | – |
No examples provided.
update_sleep Update Sleep ~114
Sleep: patch an existing sleep record by sleep_id. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| ended_at | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| notes | string | – | – |
| quality | number | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| sleep_id | string | yes | – |
| sleep_type | string | – | – |
| started_at | string | – | – |
| timezone | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string|null | – | – |
| ok | boolean | – | – |
| sleep | object | – | – |
No examples provided.
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 71 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 129 tools: notable_search, notable_profile, notable_pack, notable_pack_premium, compare_lives, and 124 more. Their descriptions and schemas cost roughly 15,533 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 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.