Dayze — Life in Days + Notable People
REMOTE · DAYZE.COM · SCANNED AUG 3
People + life-in-days knowledge for AI agents. Public MCP; x402 on Base; OAuth for private tools.
Available components
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 →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 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
- Tool/resource definitions use about 1108 tokens (~61/item across 18 items; 15 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · dayze.com
claude mcp add --transport http com-dayze-life-context 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": {
"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.
- 3 Aug 26 +1
- Tool “notable_pack” rewrote its description, which is the text the model reads security
- Tool “notable_profile” rewrote its description, which is the text the model reads security
- Schema quality: 997 → 1108 ▼ functional
- Schema quality: fair → good functional
- Server version: 1.8.1 → 1.9.0 functional
- New tool “compare_lives” functional
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 71
First indexed and scored.
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 3 Aug 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=YE2,O=Let's Encrypt,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 58fd49985dcc460b3497d8dc1cfd0387167 |
| SANs: *.dayze.com, dayze.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="dayze-mcp", resource_metadata="https://dayze.com/.well-known/oauth-protected-resource", error="unauthorized", error_description="This tool requires authentication. Use Bearer dayze_at_*, dayze_k_*, or dayze_share_*"
Bearer realm="dayze-mcp", resource_metadata="https://dayze.com/.well-known/oauth-protected-resource", error="unauthorized", error_description="This tool requires authentication. Use Bearer dayze_at_*, dayze_k_*, or dayze_share_*"| 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) |
Protected resource metadata
| Document | https://dayze.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://dayze.com/api/mcp |
| Authorisation server | https://dayze.com |
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.
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 |
No output schema declared.
No examples provided.
get_context_pack Life Context Pack ~89
Life Context Protocol (LCP) reference pack for a Dayze user: identity + who matters (edges) + week calendar + semantic/recent memories. Includes protocol.version. Optional query focuses memories. Requires API key or share token. Spec: https://dayze.com/docs/life-context ($0.20; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | — | Optional focus query for semantic memories |
No output schema declared.
No examples provided.
get_events Calendar Events ~45
User calendar events (range: today|week|month|year|decade). Requires API key. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | — | — |
No output schema declared.
No examples provided.
get_expenses Expense Summary ~30
List user expenses / cashflow summary. Requires API key. ($0.10; API key required)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_life_context Life Context Snapshot ~55
Get the authenticated user's current life context — identity, today's events, mood, inner circle, and social edges. Prefer get_context_pack for a full session bootstrap. Requires API key. ($0.15; API key required)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_life_graph Life Graph Export ~67
Life-graph export: people nodes + person_connections edges. Optional event–people links. Requires API key. ($0.25; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| event_links_limit | number | — | — |
| include_event_links | boolean | — | — |
| max_people | number | — | — |
No output schema declared.
No examples provided.
get_memories Agent Memories ~68
User memories from Dayze Agent. Pass query for semantic retrieval; omit for recent chronological. Requires API key. ($0.10; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max rows 1–50, default 20 |
| query | string | — | Semantic focus (optional) |
No output schema declared.
No examples provided.
get_people User Contacts ~42
List user CRM people (flat list). Each row includes contact_origin (personal|online|imported). Requires API key. ($0.10; API key required)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_person_neighborhood Person Neighborhood ~45
Subgraph around one person_id — profile plus all declared connections. Requires API key. ($0.15; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| person_id | string | yes | UUID |
No output schema declared.
No examples provided.
get_trackers Habit Trackers ~31
List user trackers / habits / streaks. Requires API key. ($0.10; API key required)
Input schema present but exposes no named parameters.
No output schema declared.
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 |
No output schema declared.
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 |
No output schema declared.
No examples provided.
notable_profile Notable Person Profile ~71
Bio-only profile JSON by slug (no life-in-days, similar, or birthday peers). Prefer notable_pack for “who is X / age in days / peers”. Example: taylor-swift. ($0.02)
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Person slug, e.g. albert-einstein |
No output schema declared.
No examples provided.
notable_search Search Notable People ~78
Search the public Dayze notable-people catalog by name, occupation, or slug. Use when you need to find a person before fetching a pack. Example slug: albert-einstein. ($0.01)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results 1–20 |
| q | string | yes | Search query (alias: query) |
No output schema declared.
No examples provided.
search Semantic Life Search ~69
Semantic search across the authenticated user life graph (events, people, memories). Requires API key. ($0.15; API key required)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results 1–50 |
| q | string | — | Alias for query |
| query | string | yes | Search query (primary) |
No output schema declared.
No examples provided.