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 →
upload_asset Upload Asset ~214
Upload image bytes to Dayze storage (WebP re-encode strips EXIF/AI metadata). Returns asset_id. For inventory item photos: pass entity_type=inventory, entity_id=inventory_id, role=photo, image_base64 from chat images. Or upload then attach_asset. ($0.15; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | photo | receipt | certificate | document | thumbnail | … |
| description | string | – | – |
| entity_id | string | – | – |
| entity_type | string | – | inventory_item maps to inventory |
| filename | string | – | – |
| idempotency_key | string | – | Alias for request_id. |
| image_base64 | string | – | – |
| metadata | object | – | – |
| mime_type | string | – | – |
| parent_asset_id | string | – | – |
| 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 | – | – |
| message | string|null | – | – |
| metadata_stripped | boolean | – | – |
No examples provided.
upload_photo Upload Photo ~73
Upload a photo to a Life Graph entity. Accepts image_base64 or url (one required). Re-encodes via WebP (strips EXIF/AI metadata). Person uploads also write the CRM gallery (person_photos) and avatar when set_as_avatar=true. ($0.15; API key required)
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | object | – | – |
| asset_id | string | – | – |
| avatar_updated | boolean | – | – |
| message | string|null | – | – |
| metadata_stripped | boolean | – | – |
| optimized | object | – | – |
| photo_id | string|null | – | – |
| url | string|null | – | – |
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.