General Tools

dayze.com

Provides access to notable people profiles and user life context data.

x402 supported2 endpoints30 known toolsFirst detected July 25, 2026Last detected August 14, 2026

ENDPOINT 1

https://dayze.com/api/mcp

No auth detected

MCP server metadata

Name: dayze-life-context
Version: 1.9.0

Capabilities

toolspromptsresources

Server instructions

Public notable_* tools need no API key (x402 after free tier). Private life-graph tools need Authorization: Bearer dayze_k_... with scope "context". Prefer notable_pack for agent context.

Known tools 15

notable_search

Search the public Dayze notable-people catalog by name, occupation, or slug.

Inferred read-only

notable_profile

Bio-only profile JSON by slug (no life-in-days, similar, or birthday peers).

Inferred read-only

notable_pack

DEFAULT for who is X: profile + life_in_days (age/day_number) + similar people + birthday peers.

Inferred read-only

notable_pack_premium

S-tier guaranteed pack (score≥85, timeline≥8, image, embedding).

Inferred read-only

compare_lives

Side-by-side notable packs for two slugs (life_in_days + day_number timelines).

Inferred read-only

get_life_context

Get the authenticated user's current life context — identity, today's events, mood, inner circle, and social edges.

Inferred read-only

get_context_pack

Life Context Protocol (LCP) reference pack for a Dayze user: identity + who matters (edges) + week calendar + semantic/recent memories.

Inferred read-only

get_life_graph

Life-graph export: people nodes + person_connections edges.

Inferred read-only

get_person_neighborhood

Subgraph around one person_id — profile plus all declared connections.

Inferred read-only

get_events

User calendar events (range: today|week|month|year|decade).

Inferred read-only

get_people

List user CRM people (flat list).

Inferred read-only

get_memories

User memories from Dayze Agent.

Inferred read-only

get_expenses

List user expenses / cashflow summary.

Inferred read-only

get_trackers

List user trackers / habits / streaks.

Inferred read-only

search

Semantic search across the authenticated user life graph (events, people, memories).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

{
  "mcpServers": {
    "dayze-life-context": {
      "type": "http",
      "url": "https://dayze.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dayze-life-context
Remote MCP URL: https://dayze.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dayze-life-context": {
      "url": "https://dayze.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dayze-life-context": {
      "type": "http",
      "url": "https://dayze.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dayze-life-context",
  "transport": "streamable-http",
  "url": "https://dayze.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://dayze.com/api/v1/mcp

No auth detected

MCP server metadata

Name: dayze-life-context
Version: 1.9.0

Capabilities

toolspromptsresources

Server instructions

Public notable_* tools need no API key (x402 after free tier). Private life-graph tools need Authorization: Bearer dayze_k_... with scope "context". Prefer notable_pack for agent context.

Known tools 15

notable_search

Search the public Dayze notable-people catalog by name, occupation, or slug.

Inferred read-only

notable_profile

Bio-only profile JSON by slug (no life-in-days, similar, or birthday peers).

Inferred read-only

notable_pack

DEFAULT for who is X: profile + life_in_days (age/day_number) + similar people + birthday peers.

Inferred read-only

notable_pack_premium

S-tier guaranteed pack (score≥85, timeline≥8, image, embedding).

Inferred read-only

compare_lives

Side-by-side notable packs for two slugs (life_in_days + day_number timelines).

Inferred read-only

get_life_context

Get the authenticated user's current life context — identity, today's events, mood, inner circle, and social edges.

Inferred read-only

get_context_pack

Life Context Protocol (LCP) reference pack for a Dayze user: identity + who matters (edges) + week calendar + semantic/recent memories.

Inferred read-only

get_life_graph

Life-graph export: people nodes + person_connections edges.

Inferred read-only

get_person_neighborhood

Subgraph around one person_id — profile plus all declared connections.

Inferred read-only

get_events

User calendar events (range: today|week|month|year|decade).

Inferred read-only

get_people

List user CRM people (flat list).

Inferred read-only

get_memories

User memories from Dayze Agent.

Inferred read-only

get_expenses

List user expenses / cashflow summary.

Inferred read-only

get_trackers

List user trackers / habits / streaks.

Inferred read-only

search

Semantic search across the authenticated user life graph (events, people, memories).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.dayze-life-context]
url = "https://dayze.com/api/v1/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "dayze-life-context": {
      "type": "http",
      "url": "https://dayze.com/api/v1/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: dayze-life-context
Remote MCP URL: https://dayze.com/api/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "dayze-life-context": {
      "url": "https://dayze.com/api/v1/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "dayze-life-context": {
      "type": "http",
      "url": "https://dayze.com/api/v1/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "dayze-life-context",
  "transport": "streamable-http",
  "url": "https://dayze.com/api/v1/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.