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 →
get_people_links Get People Links ~40
Alias of get_person_connections — list graph edges for one CRM person. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| person_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| connections | array | – | – |
| count | number | yes | – |
| person | object | – | – |
No examples provided.
get_person_aliases Person Aliases ~73
List canonical aliases (nicknames) for a CRM person. Pass person_id or name (resolved via aliases). Requires OAuth or a supported scoped credential. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Surface name if person_id unknown |
| person_id | string | – | CRM people.id |
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | – | – |
| candidates | array | – | – |
| name | string|null | – | – |
| person_id | string|null | – | – |
No examples provided.
get_person_connections Get Person Connections ~34
List graph edges for one CRM person. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| person_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| connections | array | – | – |
| count | number | yes | – |
| person | object | – | – |
No examples provided.
get_person_interactions Person Interactions ~155
Relationship timeline for one CRM person: interactions rows (message/call/meeting/note + extended kinds like visit/gift/stayed_over encoded in summary) plus co-tagged calendar events. Prefer this over dumping people.notes for “when did I last see X?”. Pass person_id or name. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Inclusive YYYY-MM-DD filter |
| kind | string | – | Optional filter: meeting, visit, gift, stayed_over, met, … |
| limit | number | – | Max rows 1–100, default 40 |
| name | string | – | – |
| person_id | string | – | – |
| to | string | – | Inclusive YYYY-MM-DD filter |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| events | array | – | – |
| matched_via | string|null | – | – |
| name | string | – | – |
| person_id | string | – | – |
| truncated | boolean | – | – |
No examples provided.
get_person_neighborhood Person Neighborhood ~102
Subgraph around one user-owned person_id — profile (avatar_url, photo_count, has_photos) plus declared connections. Use get_person_photos for the full gallery. Notes omitted unless include_notes=true (redacted). Requires OAuth or a supported scoped credential. ($0.15; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| include_notes | boolean | – | When true, include center.notes (server-redacted). Default false. |
| person_id | string | yes | UUID |
| Name | Type | Req | Description |
|---|---|---|---|
| center | object | yes | A Dayze person or contact record. |
| connection_count | number | yes | – |
| connections | array | yes | – |
| include_notes | boolean | – | – |
No examples provided.
get_person_photos Person Photos ~62
Gallery image URLs for a CRM contact. Returns photos[{ id, url, is_primary, created_at }] plus inline MCP image attachments for chat render. Accepts person_id. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| person_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| person_id | string | – | – |
| photos | array | – | – |
No examples provided.
get_person_transactions Person Transactions ~126
Me↔contact money ledger from expenses (paid_to_person_id / income_from_person_id). Pass person_id or name. Returns entries + per-currency totals. Reuses existing expenses — no parallel ledger table. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Inclusive YYYY-MM-DD filter |
| limit | number | – | Max rows 1–200, default 50 |
| name | string | – | Surface name if person_id unknown |
| person_id | string | – | CRM people.id |
| to | string | – | Inclusive YYYY-MM-DD filter |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| entries | array | – | – |
| name | string | – | – |
| person_id | string | – | – |
| totals | array | – | – |
No examples provided.
get_photo Get Photo ~40
Single photo metadata + secure URL. Returns inline MCP image attachment when available. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| photo_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| photo | object | – | Photo or entity asset metadata. |
No examples provided.
get_photos_for_event Photos For Event ~34
Assets linked to an event. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| event_id | string | – | – |
| photos | array | – | – |
No examples provided.
get_photos_for_place Photos For Place ~35
Assets linked to a canonical place. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| place_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| photos | array | – | – |
| place_id | string | – | – |
No examples provided.
get_place Get Place Card ~63
Fetch one saved place card (business_contacts) by place_id — address, opening hours, affordability, notes. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| business_contact_id | string | – | – |
| id | string | – | – |
| place_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| business_contact_id | string | – | – |
| message | string|null | – | – |
| place | object | – | Saved place card. |
| place_id | string | – | – |
No examples provided.
get_place_visits Place Visits ~76
When was I at a venue — merges place_visits, location_visits, and event locations. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| person_ids | array | – | – |
| place | string | yes | – |
| place_id | string | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| count | number | yes | – |
| matching_events | array | – | – |
| people_present | array | – | – |
| place | string | yes | – |
| visits | array | yes | – |
No examples provided.
get_places List Places ~120
Known venues: visit-graph `places` plus saved place cards (`saved_places` from business_contacts) with address, opening_hours, and affordability ($/$$/$$$). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| affordability | string | – | $ | $$ | $$$ |
| area | string | – | – |
| city | string | – | – |
| country | string | – | – |
| limit | number | – | – |
| near | string | – | Filter saved cards by area/tag/notes (e.g. Madeira). |
| tag | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| places | array | – | – |
| saved_count | number | – | – |
| saved_places | array | – | – |
No examples provided.
get_residences List Residences ~95
Home / residence history separate from trips: trips with metadata.kind=residence (from log_travel) plus optional life_eras. Use for Boylston / Madeira / current home cards. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| include_eras | boolean | – | Include life_eras rows (default true) |
| limit | number | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| eras | array | – | – |
| residences | array | – | – |
No examples provided.
get_sleep Get Sleep ~50
Sleep: list typed sleep/nap records with duration_minutes. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| limit | number | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| sleeps | array | – | – |
No examples provided.
get_sleep_summary Sleep Summary ~34
Sleep: day/week/month totals and averages. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| average_minutes | number | – | – |
| count | number | yes | – |
| nights | number | – | – |
| range | string | – | – |
| total_minutes | number | – | – |
No examples provided.
get_trackers Habit Trackers ~71
Authenticated user live trackers only; expired countdowns and inactive streaks are omitted. Sobriety/streak trackers remain visible at day 0 after a reset. Merges event-backed trackers with the trackers table when present. Requires OAuth or a supported scoped credential. ($0.10; API key required)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| trackers | array | yes | – |
No examples provided.
get_transactions Get Transactions ~138
List expense/income/transfer rows (includes tags, payment_method). Filter with tag=project:… or project=… ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Continue the same immutable one-hour snapshot; other filters remain frozen. |
| from | string | – | – |
| include_archived | boolean | – | – |
| limit | number | – | – |
| project | string | – | Project label or slug → project:{slug} |
| tag | string | – | Exact tag, e.g. project:max-soko-poker-venture or rail:zelle |
| to | string | – | – |
| type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| transactions | array | – | – |
No examples provided.
get_travel_history Travel History ~39
Completed/confirmed travel only. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| trips | array | – | – |
No examples provided.
get_trip Get Trip ~33
Single trip with linked places and people. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| trip_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| people | array | – | – |
| places | array | – | – |
| trip | object | – | – |
No examples provided.
get_trips List Trips ~105
User trips with status filter (planned/completed/etc.). Residences also appear here with metadata.kind=residence — prefer get_residences for home history. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Continue the same immutable one-hour snapshot; other filters remain frozen. |
| from | string | – | – |
| include_archived | boolean | – | – |
| limit | number | – | – |
| status | string | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| trips | array | – | – |
No examples provided.
import_uber_gmail Import Uber Gmail ~140
Search connected Gmail for Uber trip receipts and write log_place_visit rows with sources gmail:uber-{gmail_id} (idempotent). Optional dry_run, max_results, query, account. ($0.15; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| dry_run | boolean | – | – |
| string | – | – | |
| idempotency_key | string | – | Alias for request_id. |
| max_results | number | – | – |
| query | string | – | Override Gmail search (default from:uber.com receipt/trip) |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicates | number | yes | – |
| imported | number | yes | – |
| query | string | yes | – |
| results | array | yes | – |
| scanned | number | yes | – |
| skipped | number | yes | – |
No examples provided.
import_venmo_gmail Import Venmo Gmail ~178
Search connected Gmail for Venmo receipts and write log_transaction rows with external_id=venmo-gmail-{gmail_id} (idempotent). Optional dry_run, max_results, query, mirror_event, account. Prefer this over calendar-only Money · digs. ($0.15; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Mailbox email or connection id |
| dry_run | boolean | – | – |
| string | – | Alias for account | |
| idempotency_key | string | – | Alias for request_id. |
| max_results | number | – | – |
| mirror_event | boolean | – | Also create Money · calendar annotations |
| query | string | – | Override Gmail search (default from:venmo.com paid/payment) |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| duplicates | number | yes | – |
| imported | number | yes | – |
| query | string | yes | – |
| results | array | yes | – |
| scanned | number | yes | – |
| skipped | number | yes | – |
No examples provided.
link_entities Link Entities ~113
Link Trip→Stay→Place / Event→Person (graph, not prose). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from_id | string | yes | – |
| from_type | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| link_type | string | – | – |
| notes | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| to_id | string | yes | – |
| to_type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| link | object | – | – |
| linked | boolean | – | – |
| message | string|null | – | – |
No examples provided.
link_inventory_person Link Inventory Person ~86
Provenance link e.g. inherited_from, gifted_by. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| inventory_id | string | yes | – |
| person_id | string | yes | – |
| relationship | string | yes | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| link | object | – | – |
| message | string|null | – | – |
No examples provided.
link_people Link People ~142
NON-DESTRUCTIVE: create/update a person_connections edge between two distinct people (friends/family/knows/…). Both contacts remain. Do not use for duplicate cleanup — use merge_people. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| direction | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| notes | string | – | – |
| other_person_id | string | yes | – |
| person_id | string | yes | – |
| relationship_type | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| connection | object | – | – |
| linked | boolean | – | – |
| message | string|null | – | – |
No examples provided.
list_clarifications List Clarifications ~108
Ranked clarification queue: only person-typed mentions + duplicate CRM people. Non-person junk (places, orgs, media, command fragments) is auto-dismissed. Existing contacts auto-link. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| auto_cleanup | boolean | – | Auto-dismiss non-person / auto-link existing (default true) |
| kind | string | – | Optional: entity_mention | duplicate_people |
| limit | number | – | Max rows 1–50, default 15 |
| Name | Type | Req | Description |
|---|---|---|---|
| clarifications | array | yes | – |
| count | number | yes | – |
| message | string|null | – | – |
| truncated | boolean | – | – |
No examples provided.
list_gmail_accounts List Gmail Accounts ~76
List connected Gmail mailboxes for the authenticated user (id, email, is_default). Use account on search_gmail / read_gmail_* / import_*_gmail to pick a mailbox. Connect another inbox at /integrations (multi-mailbox after migration). Share tokens cannot call. ($0.05; API key required)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | array | yes | – |
| connect_url | string | yes | – |
| count | number | yes | – |
No examples provided.
log_event Log Event (calendar write) ~367
MUTATES the authenticated user calendar. Use for non-food days — funeral, cremation, appointment, dinner, anything that is not a food log. Do not store this as a chat memory. Example (funeral tonight): log_event({ title: "Funeral service — Mr Goh Choo Taw", date: "2026-08-29", time: "8pm", location: "Multi Purpose Hall, Blk 661 Jurong West St 64", category: "funeral" }). Example (Sunday cremation): log_event({ title: "Cremation — Mr Goh Choo Taw", date: "2026-08-30", location: "Mandai Crematorium", category: "funeral" }). Required: title + event_date (YYYY-MM-DD, YYYY-MM, or YYYY; alias date). Soft dates expand to first-of-period and set metadata.date_precision (day|month|year|approx). Optional: event_time (8pm or 20:00; alias time), end_date, end_time, location / city+country, description, category, external_url, visibility (private|friends|public), image_url, timezone, date_precision, share_with (Dayze handles e.g. ["boof"]), people / with / person_ids, idempotency_key (recommended; retries reuse the first write). For trips/residences prefer log_travel({ city, country, start_date, kind }). Unknown people names do not fail the write. Public events return share_url (/e/{id}) for Explore + social. Inserts public.events, optional event_people / shared_events, then rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | A Dayze calendar event record. |
| life_state_rebuilt | boolean | yes | – |
| people_tagged | array | yes | – |
| unresolved_people | array | yes | – |
No examples provided.
log_expense Log Expense ~140
Create an outgoing expense only. For money received (Venmo/Cash App/PayPal/Zelle) use log_transaction with direction=from and type=income. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| category | string | – | – |
| currency | string | – | – |
| date | string | – | – |
| description | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| merchant | string | – | Payee name (defaults when omitted) |
| notes | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| expense | object | – | Expense/income transaction row. |
| expense_id | string | – | – |
| message | string|null | – | – |
No examples provided.
log_favorite_song Log Favorite Song (music write) ~248
MUTATES the authenticated user favorite tracks list at /music. Use when they favorite or save a song — do not store this as a chat memory or in music_preferences. Example: “Henry Mancini - Piano And Strings (1995 Remastered)” → log_favorite_song({ track: "Henry Mancini - Piano And Strings (1995 Remastered)" }) or title + artist. Optional year_note, source_url. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | – | Artist name (required unless track blob parses) |
| idempotency_key | string | – | Alias for request_id. |
| remaster_note | string | – | Alias for year_note |
| request_id | string | – | Client idempotency key (retries return original result). |
| source_url | string | – | Optional https link |
| title | string | – | Track title (required unless track blob parses) |
| track | string | – | Optional "Artist - Title (year remaster)" blob |
| url | string | – | Alias for source_url |
| year_note | string | – | Optional year or remaster note |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | True when a new favorite was created. |
| message | string | yes | – |
| track | object | yes | Saved favorite-track record. |
| track_id | string | yes | – |
No examples provided.
log_food Log Food (diary write) ~380
MUTATES the authenticated user Food Diary and calendar. Use when they ate or drank — do not store this as a chat memory. Example: “I had Mee Pok for late lunch with my parents” → log_food({ what: "Mee Pok", kind: "meal", meal_period: "late lunch", with: ["my parents"] }). Optional: place/merchant, amount, consumed_at (ISO). Resolves with/Mum/Dad via person aliases; unknown names do not fail the food write. Tags companions on the mirrored event. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Price if mentioned |
| consumed_at | string | – | ISO instant; wins over meal_period |
| currency | string | – | ISO currency, e.g. SGD |
| 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 |
| notes | string | – | – |
| paid_by | string | – | Who paid (name or alias) |
| people_names | array | – | Alias for with |
| person_ids | array | – | Owned person UUIDs to tag (user-scoped) |
| place | string | – | Venue or location |
| request_id | string | – | Client idempotency key (retries return original result). |
| what | string | yes | What they ate or drank (required). Example: Mee Pok |
| with | array | – | Companion names, aliases, ids, or group tokens. "my parents" / Mum / Dad resolve via aliases; "family" expands to CRM rows with family relationship labels |
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string|null | yes | – |
| food_id | string | yes | – |
| food_log | object | yes | Saved Food Diary row. |
| life_state_rebuilt | boolean | yes | – |
| message | string | yes | – |
| people_tagged | array | yes | – |
| unresolved_people | array | yes | – |
No examples provided.
log_income Log Income ~153
Record money received (Stripe, refunds, payroll, Venmo). Alias of log_transaction with type=income and direction=from. Use external_id for Stripe/Gmail idempotency. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| currency | string | – | – |
| date | string | – | – |
| external_id | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| merchant | string | – | – |
| notes | string | – | – |
| payment_method | string | – | – |
| person_id | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| duplicate | boolean | – | – |
| event_id | string|null | – | – |
| expense_id | string | – | – |
| message | string|null | – | – |
| transaction | object | – | Expense/income transaction row. |
| transaction_id | string | – | – |
| type | string | – | – |
No examples provided.
log_place_visit Log Place Visit ~228
MUTATES place_visits for map/history digs (Uber dropoff, address evidence). Required: place (or place_id) + arrived_at/date. Optional: departed_at, source (uber|mcp|…), evidence_expense_id (idempotent), city/country/address. Prefer this over stuffing streets only into expenses. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| arrived_at | string | – | ISO or YYYY-MM-DD |
| city | string | – | – |
| confidence | number | – | – |
| country | string | – | – |
| date | string | – | Alias for arrived_at |
| departed_at | string | – | – |
| evidence_event_id | string | – | – |
| evidence_expense_id | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| name | string | – | Alias for place |
| place | string | – | – |
| place_id | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created_place | boolean | – | – |
| duplicate | boolean | – | – |
| message | string|null | – | – |
| place | object | – | Canonical place record. |
| place_id | string | – | – |
| visit | object | – | Normalized place visit. |
No examples provided.
log_sleep Log Sleep ~154
Sleep: log overnight or nap. Cross-midnight OK (e.g. 14:00→03:00 = 13h / 780m). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| ended_at | string | yes | ISO end |
| idempotency_key | string | – | Alias for request_id. |
| notes | string | – | – |
| quality | number | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| sleep_type | string | – | – |
| source | string | – | – |
| started_at | string | yes | ISO start |
| timezone | string | – | – |
| timezone_end | string | – | – |
| timezone_start | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string|null | – | – |
| ok | boolean | – | – |
| sleep | object | – | – |
No examples provided.
log_transaction Log Transaction ~290
Income/expense/transfer write. direction=from + type=income for Venmo/Stripe/refunds received. Positive amount; external_id dedupes imports. Optional project/tags. Zelle always USD. Optional mirror_event creates a calendar Money · annotation (ledger is still the source of truth for /money). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Stable provider account identity for imported payments. |
| amount | number | yes | – |
| currency | string | – | – |
| date | string | – | – |
| direction | string | yes | – |
| external_id | string | – | – |
| extractor_version | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| merchant | string | – | – |
| message_id | string | – | – |
| mirror_event | boolean | – | Also insert optional Money · calendar event (default false) |
| notes | string | – | – |
| payment_method | string | – | – |
| person_id | string | – | – |
| project | string | – | Venture/project label → stored as project:{slug} tag (e.g. Max Soko poker venture) |
| request_id | string | – | Client idempotency key (retries return original result). |
| source | string | – | – |
| tags | array | – | Optional tags. Prefer project: / ext: / rail: grammar. |
| type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| duplicate | boolean | – | – |
| event_id | string|null | – | – |
| expense_id | string | – | – |
| message | string|null | – | – |
| transaction | object | – | Expense/income transaction row. |
| transaction_id | string | – | – |
| type | string | – | – |
No examples provided.
log_travel Log Travel ~241
MUTATES trips (+ optional calendar travel event). Prefer this over free-text log_event for map/history. Required: city + start_date. Optional: country, end_date, kind (trip|residence|soft_pin), confidence (confirmed|likely|possible), evidence, title, mirror_event. Soft pins default to status=possible and stay off cities/map until confidence=confirmed. Zelle/Venmo money belongs in log_transaction — not here. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| confidence | string | – | – |
| country | string | – | – |
| date | string | – | Alias for start_date |
| end_date | string | – | – |
| evidence | string | – | Source note (Gmail id, address, etc.) |
| idempotency_key | string | – | Alias for request_id. |
| kind | string | – | – |
| mirror_event | boolean | – | Also insert category=travel calendar event (default true) |
| request_id | string | – | Client idempotency key (retries return original result). |
| start_date | string | – | YYYY-MM-DD |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | string | – | – |
| event_id | string|null | – | – |
| kind | string | – | – |
| message | string|null | – | – |
| note | string|null | – | – |
| trip | object | – | – |
No examples provided.
merge_people Merge People ~178
Apply a reviewed durable preview atomically; undo_contact_change accepts restore_id for 30 days if unchanged. Fold duplicate CRM contact(s) into primary_person_id (same human, spelling variants). Prefer score_people_duplicates first. Not for “X knows Y” — use link_people for relationships. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate_person_ids | array | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| preview_id | string | yes | Durable preview_id returned by merge_people_preview; review the 30-day restore window before applying. |
| primary_person_id | string | yes | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| restore_window_acknowledged | boolean | yes | Must be true — confirms the 30-day restore window was reviewed before apply. |
| Name | Type | Req | Description |
|---|---|---|---|
| merged_person_ids | array | – | – |
| message | string|null | – | – |
| person | object | – | CRM person record. |
| restore_expires_at | string | – | – |
| restore_id | string | – | – |
| reversible | boolean | – | – |
No examples provided.
merge_people_preview Merge People Preview ~105
Save a durable restore snapshot without modifying contacts before merge_people. Returns resulting name/aliases, preserved counts, field conflicts, safe_to_merge. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| duplicate_person_ids | array | yes | – |
| field_choices | object | – | – |
| idempotency_key | string | – | Alias for request_id. |
| primary_person_id | string | yes | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| field_conflicts | array | – | – |
| graph_edges_preserved | number | – | – |
| interactions_preserved | number | – | – |
| manifest | object | – | – |
| photos_preserved | number | – | – |
| preview_id | string | – | – |
| primary_person_id | string | yes | – |
| restore_window_days | number | – | – |
| resulting_aliases | array | – | – |
| resulting_name | string|null | – | – |
| reversible | boolean | – | – |
| safe_to_merge | boolean | yes | – |
| transactions_preserved | number | – | – |
| warnings | array | – | – |
No examples provided.
normalize_people_apply Normalize People Apply ~65
Apply a normalize_people_preview by preview_id. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_hash | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| preview_id | string | yes | – |
| request_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| applied | number | – | – |
| change_id | string|null | – | – |
| message | string|null | – | – |
No examples provided.
normalize_people_preview Normalize People Preview ~75
Preview whitespace/phone/handle normalization changes (no title-case of stylized names). ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | – | Client idempotency key (retries return original result). |
| rules | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | yes | – |
| count | number | yes | – |
| preview_id | string | yes | – |
No examples provided.
notable_pack Notable Knowledge Pack ~100
DEFAULT for who is X: profile + life_in_days (age/day_number) + similar people + birthday peers. Timeline events include day_number. Prefer this over notable_profile. Example: albert-einstein. ($0.05)
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD target date |
| peers | number | – | – |
| similar | number | – | – |
| slug | string | yes | Person slug, e.g. albert-einstein |
| Name | Type | Req | Description |
|---|---|---|---|
| birthday_peers | array | – | – |
| life_in_days | object | – | Age and current day-number calculations. |
| profile | object | – | Public notable-person profile. |
| similar_people | array | – | – |
| timeline | array | – | – |
No examples provided.
notable_pack_premium Premium Notable Pack ~94
S-tier guaranteed pack (score≥85, timeline≥8, image, embedding). Errors if below bar. Use when you need high-quality, complete notable context. Example slug: elon-musk. ($0.10)
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| peers | number | – | – |
| similar | number | – | – |
| slug | string | yes | Person slug, e.g. elon-musk |
| Name | Type | Req | Description |
|---|---|---|---|
| birthday_peers | array | – | – |
| life_in_days | object | – | Age and current day-number calculations. |
| profile | object | – | Quality-gated public notable-person profile. |
| quality | object | – | Pack quality signals. |
| similar_people | array | – | – |
| timeline | array | – | – |
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.