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 (17 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 15766 tokens (~118/item across 133 items; 130 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 Management90
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 2 breaking changes, 1 auth/transport breaks, 115 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 132 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, 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'
{
"mcpServers": {
"com-dayze-life-context": {
"url": "https://dayze.com/api/mcp"
}
}
} {
"servers": {
"com-dayze-life-context": {
"type": "http",
"url": "https://dayze.com/api/mcp"
}
}
} [mcp_servers.com-dayze-life-context] url = "https://dayze.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dayze-life-context": {
"type": "remote",
"url": "https://dayze.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-dayze-life-context --url 'https://dayze.com/api/mcp' --transport streamable-http
mcp_servers:
com-dayze-life-context:
url: "https://dayze.com/api/mcp" {
"McpServers": {
"com-dayze-life-context": {
"Transport": "http",
"Url": "https://dayze.com/api/mcp"
}
}
} assistant mcp add com-dayze-life-context -t streamable-http -u 'https://dayze.com/api/mcp'
{
"mcpServers": {
"com-dayze-life-context": {
"type": "http",
"url": "https://dayze.com/api/mcp"
}
}
} 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.
- 21 Sept 26 0
- Tool “get_interactions” rewrote its description, which is the text the model reads security
- 20 Sept 26 0
- New tool “get_interactions” functional
- 18 Sept 26 0
- “update_event” reworded the description of “request_id” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 17 Sept 26 −14
- Authorization: pass → fail ▼ critical
- New tool “archive_event”, which the server declares destructive security
- New tool “archive_expense”, which the server declares destructive security
- New tool “archive_trip”, which the server declares destructive security
- New tool “cleanup_apply”, which the server declares destructive security
- Tool “resolve_person” 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 “undo_contact_change” rewrote its description, which is the text the model reads security
- Tool “update_person” 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” 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 “merge_people” 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 “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
- Tool “bulk_dismiss_clarifications” is now declared destructive security
- Tool “commit_life_update” is now declared destructive security
- Tool “convert_contact_entity” is now declared destructive security
- “normalize_people_apply” added a required parameter “candidate_hash”, so existing callers break ▼ functional
- “merge_people” added a required parameter “preview_id”, so existing callers break ▼ functional
- “merge_people” added a required parameter “restore_window_acknowledged”, 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.33.0 functional
- New tool “restore_cleanup” functional
- New tool “restore_event” functional
- New tool “restore_expense” functional
- New tool “restore_trip” functional
- New tool “cleanup_preview” functional
- “merge_people_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
- “search_transactions” added an optional parameter “cursor” cosmetic
- “search_transactions” added an optional parameter “include_archived” cosmetic
- “get_events” added an optional parameter “cursor” cosmetic
- “get_events” added an optional parameter “include_archived” cosmetic
- “get_events” added an optional parameter “limit” cosmetic
- “get_people” added an optional parameter “cursor” cosmetic
- “get_transactions” added an optional parameter “cursor” cosmetic
- “get_transactions” added an optional parameter “include_archived” cosmetic
- “get_trips” added an optional parameter “cursor” cosmetic
- “get_trips” added an optional parameter “include_archived” cosmetic
- “log_transaction” added an optional parameter “account_id” cosmetic
- “log_transaction” added an optional parameter “extractor_version” cosmetic
- “log_transaction” added an optional parameter “message_id” cosmetic
- “merge_people_preview” added an optional parameter “idempotency_key” cosmetic
- “normalize_people_apply” reworded the description of “request_id” cosmetic
- Tool “resolve_person” changed its title: Resolve Person → Resolve Contact cosmetic
- Tool “update_person” changed its title: Update Person (CRM write) → Update Contact (CRM write) cosmetic
- Tool “create_person” changed its title: Create Person → Create Contact cosmetic
- Tool “get_people” changed its title: User Contacts → Dayze Contacts cosmetic
- 14 Sept 26 0
- New tool “remove_person_alias”, which the server declares destructive security
- Tool “log_event” rewrote its description, which is the text the model reads security
- Tool “link_people” rewrote its description, which is the text the model reads security
- Tool “get_trips” rewrote its description, which is the text the model reads security
- Tool “get_transactions” rewrote its description, which is the text the model reads security
- Tool “get_location_history” rewrote its description, which is the text the model reads security
- Tool “get_context_pack” rewrote its description, which is the text the model reads security
- Tool “get_cities_visited” rewrote its description, which is the text the model reads security
- Tool “search_transactions” rewrote its description, which is the text the model reads security
- Tool “update_person” rewrote its description, which is the text the model reads security
- Tool “search_gmail” rewrote its description, which is the text the model reads security
- Tool “read_gmail_message” 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 “log_transaction” rewrote its description, which is the text the model reads security
- Schema quality: 11141 → 14499 ▼ functional
- Destructive annotations: 5 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_people_preview" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does. functional
- Server version: 1.29.0 → 1.30.2 functional
- New tool “get_residences” functional
- New tool “add_person_alias” functional
- New tool “audit_people” functional
- New tool “classify_contact” functional
- New tool “convert_contact_entity” functional
- New tool “find_identity_candidates” functional
- New tool “get_people_cleanup_result” functional
- New tool “get_people_links” functional
- New tool “import_uber_gmail” functional
- New tool “import_venmo_gmail” functional
- New tool “list_gmail_accounts” functional
- New tool “log_place_visit” functional
- New tool “log_travel” functional
- New tool “merge_people_preview” functional
- New tool “normalize_people_apply” functional
- New tool “normalize_people_preview” functional
- New tool “read_gmail_attachment” functional
- New tool “set_primary_person_name” functional
- New tool “start_people_cleanup” functional
- New tool “undo_contact_change” functional
- New tool “update_notable” functional
- New tool “update_people_link” functional
- New tool “update_person_alias” functional
- New tool “update_person_identity” functional
- “get_transactions” added an optional parameter “type” cosmetic
- “get_transactions” added an optional parameter “to” cosmetic
- “get_transactions” added an optional parameter “tag” cosmetic
- “get_transactions” added an optional parameter “project” cosmetic
- “get_transactions” added an optional parameter “limit” cosmetic
- “get_transactions” added an optional parameter “from” cosmetic
- “get_context_pack” added an optional parameter “include_quiz_results” cosmetic
- “read_gmail_message” added an optional parameter “email” cosmetic
- “read_gmail_message” added an optional parameter “account” cosmetic
- “search_gmail” added an optional parameter “account” cosmetic
- “search_gmail” added an optional parameter “email” cosmetic
- “search_transactions” added an optional parameter “limit” cosmetic
- “search_transactions” added an optional parameter “project” cosmetic
- “search_transactions” added an optional parameter “tag” cosmetic
- “update_event” added an optional parameter “date_precision” cosmetic
- “update_expense” added an optional parameter “external_id” cosmetic
- “update_expense” added an optional parameter “project” cosmetic
- “update_expense” added an optional parameter “tags” cosmetic
- “update_person” added an optional parameter “name” cosmetic
- “update_person” added an optional parameter “preserve_old_name_as_alias” cosmetic
- “log_transaction” added an optional parameter “tags” cosmetic
- “log_transaction” added an optional parameter “project” cosmetic
- “log_transaction” added an optional parameter “mirror_event” cosmetic
- “update_event” reworded the description of “event_date” cosmetic
- “update_person” reworded the description of “birthday” cosmetic
- 12 Sept 26 −1
- Tool “get_places” rewrote its description, which is the text the model reads security
- Tool “log_event” rewrote its description, which is the text the model reads security
- Tool coverage: 50% → 45% ▼ functional
- Schema quality: 9827 → 11141 ▼ functional
- Server version: 1.28.0 → 1.29.0 functional
- New tool “create_place” functional
- New tool “commit_life_update” functional
- New tool “enrich_place_from_google” functional
- New tool “get_current_states” functional
- New tool “get_place” functional
- New tool “propose_life_update” functional
- New tool “update_current_location” functional
- New tool “update_place” functional
- “get_places” added an optional parameter “area” cosmetic
- “get_places” added an optional parameter “affordability” cosmetic
- “get_places” added an optional parameter “tag” cosmetic
- “get_places” added an optional parameter “near” cosmetic
- 11 Sept 26 0
- Tool “search_inventory” rewrote its description, which is the text the model reads security
- Tool “update_food” rewrote its description, which is the text the model reads security
- Tool “log_transaction” rewrote its description, which is the text the model reads security
- Tool “get_trackers” rewrote its description, which is the text the model reads security
- Server version: 1.25.0 → 1.28.0 functional
- New tool “reset_tracker” functional
- New tool “log_income” functional
- “update_food” added an optional parameter “payment_method” cosmetic
- “update_food” added an optional parameter “append_notes” cosmetic
- “update_expense” added an optional parameter “source” cosmetic
- “update_expense” added an optional parameter “payment_method” cosmetic
- “update_expense” added an optional parameter “description” cosmetic
- “update_expense” added an optional parameter “currency” cosmetic
- “log_transaction” added an optional parameter “payment_method” cosmetic
- 9 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New prompt “sleep_check” functional
- Server version: 1.19.0 → 1.25.0 functional
- New tool “update_sleep” functional
- New tool “log_sleep” functional
- New tool “get_sleep_summary” functional
- New tool “get_sleep” functional
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 24 Sept 2026 · Probed https://dayze.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dayze.com | CN=YE1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6fe233b3b1bfd9c2b9d0e1fec960b1d076d |
| SANs: *.dayze.com, dayze.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dayze.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | 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 | Verified | 200 | |
| http (plaintext) | http://dayze.com/api/mcp | HTTPS enforced | 301 | https://dayze.com/api/mcp |
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 →
add_inventory_item Add Inventory Item ~66
Add an owned object to Life Inventory. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| name | string | yes | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| inventory_id | string | – | – |
| item | object | – | Inventory item record. |
| message | string|null | – | – |
No examples provided.
add_inventory_valuation Add Inventory Valuation ~79
Append immutable valuation observation. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| inventory_id | string | yes | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| value | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string|null | – | – |
| valuation | object | – | – |
No examples provided.
add_person_alias Add Person Alias ~96
Add a nickname/payment handle/misspelling alias for one CRM person. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | – |
| 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 | string | – | – |
| aliases | array | – | – |
| change_id | string|null | – | – |
| message | string|null | – | – |
| person_id | string | – | – |
No examples provided.
archive_asset Archive Asset ~75
Soft-delete an asset (sets archived_at). Original rows are preserved for versioning. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| asset | object | – | – |
| asset_id | string | – | – |
| message | string|null | – | – |
No examples provided.
archive_event archive event ~78
Reversibly archive one owned event; preserve linked data and return restore_id. Use a new request_id for each intended action. ($0; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| reason | string | – | – |
| request_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.
archive_expense archive expense ~79
Reversibly archive one owned expense; preserve linked data and return restore_id. Use a new request_id for each intended action. ($0; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| expense_id | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| reason | string | – | – |
| request_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.
archive_inventory_item Archive Inventory Item ~72
Archive instead of destructive delete. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| inventory_id | string | yes | – |
| reason | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| inventory_id | string | – | – |
| message | string|null | – | – |
No examples provided.
archive_trip archive trip ~78
Reversibly archive one owned trip; preserve linked data and return restore_id. Use a new request_id for each intended action. ($0; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Alias for request_id. |
| reason | string | – | – |
| request_id | string | yes | – |
| trip_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.
attach_asset Attach Asset ~157
Link an existing asset_id to another entity by creating a linked copy (does not move the original row). Roles: original | processed | thumbnail | cover | document | receipt | certificate | other. Legacy: pass url instead of asset_id. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | – | – |
| asset_type | string | – | – |
| entity_id | string | yes | – |
| entity_type | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| metadata | object | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| role | string | – | original | cover | thumbnail | … |
| url | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | object | – | – |
| asset_id | string | – | – |
| attached | boolean | – | – |
| message | string|null | – | – |
No examples provided.
audit_people Audit People (compact) ~79
CONTEXT LAYER: server-side contact hygiene. Returns compact candidate clusters only (duplicates, entity-type hints, normalization, payment-handle collisions). Do NOT use get_people bulk dumps for cleanup. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| limit | number | – | – |
| min_confidence | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | – |
| count | number | yes | – |
| guidance | string | – | – |
| summary | object | yes | – |
No examples provided.
bulk_dismiss_clarifications Bulk Dismiss Clarifications ~81
Dismiss non-person / typed junk from the clarification queue. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| entity_type | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| reason | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| dismissed | number | – | – |
| message | string|null | – | – |
No examples provided.
classify_contact Classify Contact ~116
Set entity_type (person/company/merchant/…) on a CRM row without losing transactions or links. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| entity_id | string | – | – |
| entity_type | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| identity_status | string | – | – |
| person_id | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | string|null | – | – |
| message | string|null | – | – |
| person | object | – | – |
No examples provided.
cleanup_apply cleanup apply ~90
Atomically archive the exact reviewed preview. Requires preview_id, candidate_hash and request_id. Refuses changed sources. Returns per-row statuses and restore_id; replay performs no additional actions. ($0; API key required)
| 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 |
|---|---|---|---|
| candidate_hash | string | – | – |
| changed | boolean | – | – |
| expires_at | string | – | – |
| preview_id | string | – | – |
| restore_id | string | – | – |
| rows | array | – | – |
| server_time | string | – | – |
No examples provided.
cleanup_preview cleanup preview ~104
Read-only account audit and durable archive plan for events, expenses or trips. Returns source hashes, linked records, field differences, rollback payloads and a review queue. Review the exact candidate set before cleanup_apply. Preview expires after 30 minutes. ($0; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | – | Client idempotency key (retries return original result). |
| 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.
commit_life_update Commit Life Update ~81
Owner approve+commit via payload_hash + owner_session_id (flagged; off by default). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | – |
| owner_session_id | string | yes | – |
| payload_hash | string | yes | – |
| proposal_id | string | yes | – |
| request_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assertionIds | array | – | – |
| enabled | boolean | – | – |
| graphVersion | number | – | – |
| message | string|null | – | – |
No examples provided.
compare_lives Compare Two Lives ~103
Side-by-side notable packs for two slugs (life_in_days + day_number timelines). One call instead of two notable_pack. Example: elon-musk vs steve-jobs. ($0.08)
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD target date for both packs |
| peers | number | – | – |
| similar | number | – | – |
| slug_a | string | yes | First person slug |
| slug_b | string | yes | Second person slug |
| Name | Type | Req | Description |
|---|---|---|---|
| a | object | yes | First notable-person knowledge pack. |
| b | object | yes | Second notable-person knowledge pack. |
| compare | object | yes | Computed comparison fields and URLs. |
| pack | string | yes | – |
No examples provided.
convert_contact_entity Convert Contact Entity ~92
Convert a contact’s entity_type (same as classify_contact). Preserves FKs. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| person_id | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| target_type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | string|null | – | – |
| message | string|null | – | – |
| person | object | – | – |
No examples provided.
create_person Create Contact ~126
Add a Dayze Contacts record; checks duplicates first. Advertised name create_person is stable; tools/call also accepts create_contact. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | – | – |
| string | – | – | |
| idempotency_key | string | – | Alias for request_id. |
| name | string | yes | – |
| notes | string | – | – |
| phone | string | – | – |
| relationship | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| tier | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | – | – |
| message | string|null | – | – |
| person | object | – | CRM person record. |
No examples provided.
create_place Create Place Card ~270
Save a venue card (business_contacts): address, opening_hours, affordability ($/$$/$$$), notes, tags. Idempotent by name or idempotency_key — does not create calendar notes. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| affordability | string | – | $ | $$ | $$$ (or 1–3) |
| area | string | – | – |
| category | string | – | restaurant|cafe|supermarket|shop|hawker|… (aliases mapped to business_contacts.category) |
| city | string | – | – |
| country | string | – | – |
| description | string | – | – |
| hours | string | – | Alias for opening_hours |
| hours_source | string | – | agent | google_places | user |
| idempotency_key | string | – | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| notes | string | – | – |
| opening_hours | string | – | – |
| phone | string | – | – |
| phone_numbers | array | – | – |
| price_level | string | – | Alias for affordability |
| request_id | string | – | Client idempotency key (retries return original result). |
| tags | array | – | – |
| website | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| business_contact_id | string | – | – |
| created | boolean | – | – |
| duplicate | boolean | – | – |
| message | string|null | – | – |
| place | object | – | Saved place card. |
| place_id | string | – | – |
No examples provided.
delete_event Delete Event (calendar remove) ~123
Reversibly archives one owned event. Required event_id and request_id. Returns the prior row in deleted for compatibility, changed, restore_id and life_state_rebuilt. All food, people and asset links are preserved. Restore with restore_event. Replays perform no additional action. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | UUID of a calendar event the authenticated user owns |
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | yes | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | object | yes | A Dayze calendar event record. |
| event_id | string | yes | – |
| food_deleted_ids | array | yes | – |
| life_state_rebuilt | boolean | yes | – |
No examples provided.
delete_food Delete Food (Food Diary remove) ~135
MUTATES by removing one Food Diary row the authenticated user owns and its mirrored calendar event. Required: food_id (UUID). Prefer this over delete_event for meals logged via log_food. Unknown or other-user food_id returns an error. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| food_id | string | yes | UUID of a Food Diary row the authenticated user owns |
| idempotency_key | string | – | Alias for request_id. |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | object | yes | Deleted food diary row. |
| event_id | string|null | – | – |
| food_id | string | yes | – |
| life_state_rebuilt | boolean | yes | – |
No examples provided.
dismiss_clarification Dismiss Clarification ~79
Dismiss a pending entity clarification (not_person, etc.). ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| clarification_id | string | yes | – |
| idempotency_key | string | – | Alias for request_id. |
| reason | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| dismissed | boolean | – | – |
| message | string|null | – | – |
No examples provided.
enrich_place_from_google Enrich Place from Google ~110
Optional Google Places fill for a saved place card (hours/address/phone/website). Defaults to fill_empty_only — does not overwrite agent-supplied fields. ($0.15; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| business_contact_id | string | – | – |
| fill_empty_only | boolean | – | – |
| idempotency_key | string | – | Alias for request_id. |
| place_id | string | – | – |
| request_id | string | – | Client idempotency key (retries return original result). |
| Name | Type | Req | Description |
|---|---|---|---|
| applied_fields | array | – | – |
| business_contact_id | string | – | – |
| enriched | boolean | – | – |
| message | string|null | – | – |
| place | object | – | Saved place card. |
| place_id | string | – | – |
No examples provided.
explain_fact Explain Fact ~103
Return evidence/provenance for a claim: polaris_learned_facts, life_events / life_event_relationships when present, then memories. Use when the agent must cite why it believes something — do not invent sources. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| fact | string | – | Alias for query |
| limit | number | – | Max evidence rows 1–20, default 8 |
| query | string | yes | Fact or phrase to explain |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| evidence | array | yes | – |
| message | string|null | – | – |
| query | string | yes | – |
No examples provided.
find_identity_candidates Find Identity Candidates ~61
Compact identity resolution candidates by person_id or query (alias/name/payment signals). Prefer over bulk get_people. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| person_id | string | – | – |
| query | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | – |
| count | number | yes | – |
No examples provided.
get_asset Get Asset ~48
Fetch one asset by asset_id with signed_url for download/processing. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | – |
| include_signed_url | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | object | – | – |
| count | number | yes | – |
No examples provided.
get_cities_visited Cities Visited ~67
Canonical cities from confirmed/completed trips only (excludes soft pins / status=possible). Inference requires category=travel + structured location — not todo titles. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| cities | array | yes | – |
| count | number | yes | – |
No examples provided.
get_context_pack Life Context Pack ~260
Life Context Protocol (LCP) pack for the authenticated user: identity, pulse, who_matters, whats_next, memories, quiz_results. Pass include_relationships/include_memories/include_quiz_results false to omit those sections; location and money stay opt-in. Spec: https://dayze.com/docs/life-context ($0.20; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | Optional focus hint echoed in the pack (e.g. places, travel, people) |
| include_location | boolean | – | Include city/country label; never returns a precise address |
| include_memories | boolean | – | Include recent memories (default true). A query always enables focused memories. |
| include_money | boolean | – | Include the private cashflow summary |
| include_places | boolean | – | Include recent canonical places (venue-level, no GPS points) |
| include_quiz_results | boolean | – | Include latest quiz results (slug, result_type, result_data). Default true. |
| include_relationships | boolean | – | Include who_matters (inner-circle, relationship health, reach-out). Default true. |
| include_trips | boolean | – | Include recent/upcoming trips from completed travel history |
| query | string | – | Optional focus query for semantic memories |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Present when life state is unavailable. |
| focus | string|null | – | – |
| generated_at | string | – | – |
| identity | object | yes | – |
| memories | object | – | – |
| ok | boolean | – | – |
| partial | boolean | – | – |
| places | object | – | Recent canonical places when include_places=true. |
| preferred_tool | string | yes | – |
| protocol | object | yes | Life Context Protocol metadata. |
| pulse | object | yes | – |
| query | string|null | – | – |
| sections | object | – | Per-section ok/error status for partial packs. |
| trips | object | – | Recent trips when include_trips=true. |
| whats_next | object | yes | – |
| who_matters | object | – | – |
No examples provided.
get_countries_visited Countries Visited ~55
Canonical countries from completed trips (not other people travel). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| include_residence | boolean | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| countries | array | yes | – |
No examples provided.
get_current_states Current States ~83
Permitted assertion states for a person (flagged life-graph; off by default). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| known_at | string | – | – |
| people_id | string | – | CRM people.id UUID |
| person_id | string | – | Alias for people_id |
| predicates | array | – | – |
| valid_at | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| enabled | boolean | – | – |
| states | array | – | – |
No examples provided.
get_entity_assets Get Entity Assets ~63
List assets linked to an entity (role, signed_url, versions). entity_type inventory_item → inventory. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | – |
| entity_id | string | yes | – |
| entity_type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | – | – |
| count | number | yes | – |
No examples provided.
get_entity_links Get Entity Links ~48
List graph edges for an event, trip, place, or person. ($0.05; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | yes | – |
| entity_type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| links | array | – | – |
No examples provided.
get_events Calendar Events ~173
Authenticated user's calendar events. Prefer explicit from/to (YYYY-MM-DD). Shortcuts: today|week|month|year (calendar year)|decade. Browsing noise excluded by default. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| from | string | – | Inclusive YYYY-MM-DD (preferred over range) |
| include_archived | boolean | – | – |
| include_browsing | boolean | – | Include extension "Browsed domain · Xm" auto-events (default false) |
| include_calendar_blocks | boolean | – | Include Focus Time / calendar_block rows (default false) |
| kinds | array | – | Filter event_kind e.g. ["life_event","todo"] |
| limit | number | – | – |
| range | string | – | – |
| to | string | – | Inclusive YYYY-MM-DD |
| Name | Type | Req | Description |
|---|---|---|---|
| cap | number | yes | – |
| events | array | yes | – |
| expires_at | string | – | – |
| from | string|null | yes | Inclusive YYYY-MM-DD lower bound; null for all records. |
| has_more | boolean | – | – |
| next_cursor | string|null | – | – |
| ordering | string | – | – |
| range | string | yes | – |
| server_time | string | – | – |
| snapshot_at | string | – | – |
| snapshot_id | string | – | – |
| to | string|null | yes | Inclusive YYYY-MM-DD upper bound; null for all records. |
| total | number | – | – |
| truncated | boolean | yes | – |
No examples provided.
get_expenses Expense Summary ~44
Authenticated user cashflow summary: spend, income, net, and top spend categories. Requires OAuth or a supported scoped credential. ($0.10; API key required)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| by_currency | array | – | – |
| count | number | – | – |
| currency | string|null | – | – |
| income | number | – | – |
| multi_currency | boolean | – | – |
| net | number | – | – |
| period | string | yes | – |
| period_days | number | – | – |
| spend | number | – | – |
| top_categories | array | – | – |
| usd | object | – | Totals converted to USD (approximate FX). |
No examples provided.
get_interactions Life Update Interactions ~206
Bounded graph read over life_updates (PHI-54/61): traverse interaction → person/event/expense/place with source/confidence on every hop. When life_update edges are missing, projects hops from CRM interactions, event_people, and expense person FKs (PHI-100). Prefer for “who was I with at X?”, “when am I meeting Y next?”, “how much at Z?”. 93-day default window. Pass person_name, place_query, or ids. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | – | – |
| expense_id | string | – | – |
| from | string | – | Inclusive YYYY-MM-DD |
| limit | number | – | Max 1–50, default 25 |
| person_id | string | – | – |
| person_name | string | – | – |
| place_id | string | – | – |
| place_query | string | – | Venue/merchant substring |
| to | string | – | Inclusive YYYY-MM-DD |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string|null | – | – |
| interactions | array | – | – |
| no_data | boolean | – | – |
| ok | boolean | – | – |
| truncated | boolean | – | – |
| window | object | – | Bounded from/to lookback window. |
No examples provided.
get_inventory Get Inventory ~23
Browse owned inventory with filters. ($0.10; API key required)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| items | array | – | – |
No examples provided.
get_inventory_item Get Inventory Item ~36
Full item with valuations, people links, assets. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| inventory_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | – | – |
| item | object | – | Inventory item record. |
| people_links | array | – | – |
| valuations | array | – | – |
No examples provided.
get_inventory_valuations Get Inventory Valuations ~36
Chronological valuation history for an item. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| inventory_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| valuations | array | – | – |
No examples provided.
get_life_context Life Context Snapshot ~144
Get a snapshot of the authenticated user's current life context (identity, today/upcoming events, pulse, trackers). Relationships and memories are included by default; pass include_*=false to omit. Location is opt-in. Requires an authenticated Dayze account via OAuth; scoped API keys are also supported for direct clients. ($0.15; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| include_location | boolean | – | Include city/country label; never returns a precise address |
| include_memories | boolean | – | Include recent memory summaries (default true; set false to omit) |
| include_relationships | boolean | – | Include inner-circle and relationship summaries (default true; set false to omit) |
| Name | Type | Req | Description |
|---|---|---|---|
| active_trackers | array | – | – |
| energy_score | number|null | – | – |
| identity | object | yes | Account identity and timezone. |
| inner_circle | array | – | – |
| mood_score | number|null | – | – |
| pending_responses | array | – | – |
| pending_responses_count | number | – | – |
| pulse_streak | number|null | – | – |
| recent_memories | array | – | – |
| relationship_health | array | – | – |
| social_edges | array | – | – |
| today_events | array | yes | – |
| upcoming_events | array | yes | – |
No examples provided.
get_life_graph Life Graph Export ~105
Explicit private life-graph export: favorites/VIP plus people with edges or recent event tags. Pass full=true for a larger capped list. Optional event–people links. Requires OAuth or a supported scoped credential. ($0.25; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| event_links_limit | number | – | – |
| full | boolean | – | Include additional people by last interaction, up to max_people |
| include_event_links | boolean | – | – |
| max_people | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| edge_count | number | yes | – |
| edges | array | yes | – |
| event_people_links | array | – | – |
| hot | boolean | yes | – |
| max_people_requested | number | – | – |
| node_count | number | yes | – |
| nodes | array | yes | – |
No examples provided.
get_location_context Location Context ~39
Likely current or at-time place with confidence and provenance. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | ISO timestamp |
| Name | Type | Req | Description |
|---|---|---|---|
| at | string|null | – | – |
| confidence | number | – | – |
| place | object|null | – | Canonical place record. |
| provenance | array | – | – |
No examples provided.
get_location_history Location History ~87
Normalized visit history (venue-level by default). Merges GPS location_visits + place_visits (MCP/Uber digs). ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| country | string | – | – |
| from | string | – | – |
| place | string | – | – |
| precision | string | – | – |
| to | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| visits | array | – | – |
No examples provided.
get_memories Agent Memories ~81
Authenticated user memories from Dayze Agent. Pass query for semantic/keyword retrieval. Prefer search for event-first trip and calendar titles. Requires OAuth or a supported scoped credential. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max rows 1–50, default 20 |
| query | string | – | Semantic focus (optional) |
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | – |
| memories | array | yes | – |
| mode | string | yes | – |
| people | array | – | – |
| query | string | – | – |
No examples provided.
get_money_between_people Money Between People ~114
Same as get_person_transactions: authenticated user ↔ one contact via expenses FKs. Prefer get_person_transactions; this alias exists for agent discoverability. ($0.10; API key required)
| 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 |
|---|---|---|---|
| entries | array | – | – |
| model | string | – | – |
| name | string | – | – |
| person_id | string | – | – |
| totals | 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).
Is the Dayze — Life Context MCP server safe to use?
Dayze — Life Context scores 77 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 130 tools: notable_search, notable_profile, notable_pack, notable_pack_premium, compare_lives, and 125 more. Their descriptions and schemas cost roughly 15,551 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 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.