# Dayze — Life in Days + Notable People (remote · dayze.com)

People + life-in-days knowledge for AI agents. Public MCP; x402 on Base; OAuth for private tools.

- Trust score: 80/100 (high trust)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `dayze.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-dayze-life-context/api-mcp.md), [page](https://verifymcp.io/servers/com-dayze-life-context/api-mcp)

## Channel facts

- Endpoint: `https://dayze.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1108 tokens (~61/item across 18 items; 15 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 59% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-dayze-life-context https://dayze.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-dayze-life-context]
url = "https://dayze.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dayze-life-context": {
      "type": "remote",
      "url": "https://dayze.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dayze-life-context --url https://dayze.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dayze-life-context:
    url: "https://dayze.com/api/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 80, +1)

- [security] 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
- [functional regression] Schema quality: 997 → 1108
- [functional] Schema quality: fair → good
- [functional] Server version: 1.8.1 → 1.9.0
- [functional] New tool “compare_lives”

### 2026-08-02 (score 79, +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.

### 2026-07-31 (score 78, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 72, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 73, +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.

### 2026-07-27 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 71)

First indexed and scored.

## MCP tools (15)

### `notable_search` (~78 tokens)

Search Notable People

Search the public Dayze notable-people catalog by name, occupation, or slug. Use when you need to find a person before fetching a pack. Example slug: albert-einstein. ($0.01)

Input parameters:

- `limit` (number): Max results 1–20
- `q` (string, required): Search query (alias: query)

### `notable_profile` (~71 tokens)

Notable Person Profile

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)

Input parameters:

- `slug` (string, required): Person slug, e.g. albert-einstein

### `notable_pack` (~100 tokens)

Notable Knowledge Pack

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)

Input parameters:

- `date` (string): YYYY-MM-DD target date
- `peers` (number)
- `similar` (number)
- `slug` (string, required): Person slug, e.g. albert-einstein

### `notable_pack_premium` (~94 tokens)

Premium Notable Pack

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)

Input parameters:

- `date` (string)
- `peers` (number)
- `similar` (number)
- `slug` (string, required): Person slug, e.g. elon-musk

### `compare_lives` (~103 tokens)

Compare Two Lives

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)

Input parameters:

- `date` (string): YYYY-MM-DD target date for both packs
- `peers` (number)
- `similar` (number)
- `slug_a` (string, required): First person slug
- `slug_b` (string, required): Second person slug

### `get_life_context` (~55 tokens)

Life Context Snapshot

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)

### `get_context_pack` (~89 tokens)

Life Context Pack

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)

Input parameters:

- `query` (string): Optional focus query for semantic memories

### `get_life_graph` (~67 tokens)

Life Graph Export

Life-graph export: people nodes + person_connections edges. Optional event–people links. Requires API key. ($0.25; API key required)

Input parameters:

- `event_links_limit` (number)
- `include_event_links` (boolean)
- `max_people` (number)

### `get_person_neighborhood` (~45 tokens)

Person Neighborhood

Subgraph around one person_id — profile plus all declared connections. Requires API key. ($0.15; API key required)

Input parameters:

- `person_id` (string, required): UUID

### `get_events` (~45 tokens)

Calendar Events

User calendar events (range: today|week|month|year|decade). Requires API key. ($0.10; API key required)

Input parameters:

- `range` (string)

### `get_people` (~42 tokens)

User Contacts

List user CRM people (flat list). Each row includes contact_origin (personal|online|imported). Requires API key. ($0.10; API key required)

### `get_memories` (~68 tokens)

Agent Memories

User memories from Dayze Agent. Pass query for semantic retrieval; omit for recent chronological. Requires API key. ($0.10; API key required)

Input parameters:

- `limit` (number): Max rows 1–50, default 20
- `query` (string): Semantic focus (optional)

### `get_expenses` (~30 tokens)

Expense Summary

List user expenses / cashflow summary. Requires API key. ($0.10; API key required)

### `get_trackers` (~31 tokens)

Habit Trackers

List user trackers / habits / streaks. Requires API key. ($0.10; API key required)

### `search` (~69 tokens)

Semantic Life Search

Semantic search across the authenticated user life graph (events, people, memories). Requires API key. ($0.15; API key required)

Input parameters:

- `limit` (number): Max results 1–50
- `q` (string): Alias for query
- `query` (string, required): Search query (primary)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dayze-life-context/api-mcp#diagnostics

## Score history

- 2026-08-03: 80
- 2026-08-02: 79
- 2026-08-01: 78
- 2026-07-31: 78
- 2026-07-30: 72
- 2026-07-29: 73
- 2026-07-28: 72
- 2026-07-27: 72
- 2026-07-26: 71

## Links

- Remote endpoint: https://dayze.com/api/mcp
- Repository: https://github.com/gohluke/dayze-mcp
- Website: https://dayze.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dayze-life-context/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dayze-life-context/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-dayze-life-context/api-mcp