RMCP.DEV
← Registry

General Tools

dayze.com

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

x402 supported3 endpoints120 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://dayze.com/api/mcp

No auth detected

MCP server metadata

Name
dayze-life-context
Version
1.10.2
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 18

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: identity, who_matters (incl.

Inferred read-only
get_life_graph

Hot life-graph export: favorites/VIP + people with edges or recent event tags.

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
update_person

MUTATES the authenticated user CRM.

Inferred read-only
log_food

MUTATES the authenticated user Food Diary and calendar.

Inferred read-only
log_event

MUTATES the authenticated user calendar.

Inferred read-only
get_memories

User memories from Dayze Agent.

Inferred read-only
get_expenses

Cashflow summary: spend, income, net, and top spend categories.

Inferred read-only
get_trackers

Live trackers only — expired countdowns and dead streaks omitted.

Inferred read-only
search

Search 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.

ENDPOINT 3

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

No auth detected

MCP server metadata

Name
dayze
Version
1.28.0
Capabilities
toolspromptsresources
Server instructions

Public notable_* tools need no API key (x402 after free tier). Private life-graph tools need OAuth (Bearer dayze_at_*) or API key (Bearer dayze_k_*) with scope "context". Prefer get_context_pack for a signed-in user life-graph bootstrap; use notable_pack only for the public notable-people catalog. Sleep: log_sleep / get_sleep / get_sleep_summary / update_sleep (pack sleep section is read-only). Person photos: get_person_photos returns inline MCP image attachments. Inventory photos: search_inventory → upload_asset(image_base64, entity_type=inventory, entity_id, role=photo) or upload_asset then attach_asset.

Known tools 87

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 a snapshot of the authenticated user's current life context (identity, today/upcoming events, pulse, trackers).

Inferred read-only
get_context_pack

Life Context Protocol (LCP) pack for the authenticated user: identity, pulse, who_matters, whats_next, memories.

Inferred read-only
get_life_graph

Explicit private life-graph export: favorites/VIP plus people with edges or recent event tags.

Inferred read-only
get_person_neighborhood

Subgraph around one user-owned person_id — profile (avatar_url, photo_count, has_photos) plus declared connections.

Inferred read-only
get_events

Authenticated user's calendar events.

Inferred read-only
get_people

List the authenticated user's CRM people.

Inferred read-only
update_person

MUTATES the authenticated user CRM.

Inferred read-only
log_food

MUTATES the authenticated user Food Diary and calendar.

Inferred read-only
update_food

MUTATES one existing Food Diary row the authenticated user owns.

Inferred read-only
delete_food

MUTATES by removing one Food Diary row the authenticated user owns and its mirrored calendar event.

Inferred read-only
log_event

MUTATES the authenticated user calendar.

Inferred read-only
update_event

MUTATES one existing calendar event the authenticated user owns.

Inferred read-only
delete_event

MUTATES by removing one existing calendar event the authenticated user owns.

Inferred read-only
log_favorite_song

MUTATES the authenticated user favorite tracks list at /music.

Inferred read-only
get_memories

Authenticated user memories from Dayze Agent.

Inferred read-only
get_expenses

Authenticated user cashflow summary: spend, income, net, and top spend categories.

Inferred read-only
resolve_person

Resolve a nickname or surface name to a CRM person via person_aliases → exact name → slug → unique substring.

Inferred read-only
get_person_aliases

List canonical aliases (nicknames) for a CRM person.

Inferred read-only
get_person_transactions

Me↔contact money ledger from expenses (paid_to_person_id / income_from_person_id).

Inferred read-only
get_money_between_people

Same as get_person_transactions: authenticated user ↔ one contact via expenses FKs.

Inferred read-only
get_person_interactions

Relationship timeline for one CRM person: interactions rows (message/call/meeting/note + extended kinds like visit/gift/stayed_over encoded in summary) plus co-tagged calendar events.

Potential side effects
explain_fact

Return evidence/provenance for a claim: polaris_learned_facts, life_events / life_event_relationships when present, then memories.

Inferred read-only
list_clarifications

Ranked clarification queue: only person-typed mentions + duplicate CRM people.

Inferred read-only
get_trackers

Authenticated user live trackers only; expired countdowns and inactive streaks are omitted.

Inferred read-only
reset_tracker

MUTATES a sobriety/streak tracker for the authenticated user (sets current value to 0 and restarts the clock).

Inferred read-only
search

Search the authenticated user life graph.

Inferred read-only
search_gmail

Search the authenticated user's already-connected Gmail inbox (read-only).

Inferred read-only
read_gmail_message

Read one Gmail message by id from search_gmail.

Potential side effects
log_sleep

Sleep: log overnight or nap.

Inferred read-only
get_sleep

Sleep: list typed sleep/nap records with duration_minutes.

Inferred read-only
get_sleep_summary

Sleep: day/week/month totals and averages.

Inferred read-only
update_sleep

Sleep: patch an existing sleep record by sleep_id.

Inferred read-only
resolve_place

Canonicalize a venue name via place aliases and fuzzy match.

Inferred read-only
get_places

Known canonical places in the user Life Graph.

Inferred read-only
get_place_visits

When was I at a venue — merges place_visits, location_visits, and event locations.

Inferred read-only
get_location_history

Normalized visit history (venue-level by default, not raw GPS noise).

Inferred read-only
get_location_context

Likely current or at-time place with confidence and provenance.

Inferred read-only
get_trips

User trips with status filter (planned/completed/etc.

Inferred read-only
get_trip

Single trip with linked places and people.

Inferred read-only
get_travel_history

Completed/confirmed travel only.

Inferred read-only
get_countries_visited

Canonical countries from completed trips (not other people travel).

Inferred read-only
get_cities_visited

Canonical cities from completed trips.

Inferred read-only
create_person

Add a CRM contact; checks duplicates first.

Inferred read-only
merge_people

Merge duplicate CRM contacts into a primary person.

Inferred read-only
score_people_duplicates

Score likely CRM duplicate pairs before merge_people.

Inferred read-only
link_people

Create person↔person graph edge (knows/friends/…).

Potential side effects
get_person_connections

List graph edges for one CRM person.

Inferred read-only
unlink_people

Remove a person↔person graph edge.

Potential side effects
dismiss_clarification

Dismiss a pending entity clarification (not_person, etc.

Inferred read-only
resolve_clarification

Link a clarification surface to an existing person.

Inferred read-only
bulk_dismiss_clarifications

Dismiss non-person / typed junk from the clarification queue.

Inferred read-only
link_entities

Link Trip→Stay→Place / Event→Person (graph, not prose).

Inferred read-only
get_entity_links

List graph edges for an event, trip, place, or person.

Inferred read-only
add_inventory_item

Add an owned object to Life Inventory.

Inferred read-only
get_inventory

Browse owned inventory with filters.

Inferred read-only
get_inventory_item

Full item with valuations, people links, assets.

Inferred read-only
update_inventory_item

PATCH semantics — unspecified fields untouched.

Inferred read-only
archive_inventory_item

Archive instead of destructive delete.

Potential side effects
search_inventory

Search owned inventory by name/brand/model/notes.

Inferred read-only
add_inventory_valuation

Append immutable valuation observation.

Inferred read-only
get_inventory_valuations

Chronological valuation history for an item.

Inferred read-only
link_inventory_person

Provenance link e.

Inferred read-only
upload_asset

Upload image bytes to Dayze storage (WebP re-encode strips EXIF/AI metadata).

Potential side effects
get_asset

Fetch one asset by asset_id with signed_url for download/processing.

Inferred read-only
update_asset

Patch role, metadata, description, or parent_asset_id (e.

Inferred read-only
archive_asset

Soft-delete an asset (sets archived_at).

Potential side effects
upload_photo

Upload a photo to a Life Graph entity.

Potential side effects
attach_asset

Link an existing asset_id to another entity by creating a linked copy (does not move the original row).

Inferred read-only
get_entity_assets

List assets linked to an entity (role, signed_url, versions).

Inferred read-only
log_expense

Create an outgoing expense only.

Potential side effects
log_transaction

Income/expense/transfer write.

Potential side effects
log_income

Record money received (Stripe, refunds, payroll, Venmo).

Inferred read-only
update_expense

PATCH an expense row.

Inferred read-only
record_purchase

Atomic expense + optional inventory item creation.

Inferred read-only
record_sale

Mark inventory sold + record sale proceeds with gain/loss.

Inferred read-only
get_transactions

List expense/income/transfer rows.

Potential side effects
search_transactions

Keyword search over transactions.

Inferred read-only
search_photos

Search person photos and entity assets by query/metadata.

Inferred read-only
get_photo

Single photo metadata + secure URL.

Inferred read-only
get_photos_for_event

Assets linked to an event.

Inferred read-only
get_person_photos

Gallery image URLs for a CRM contact.

Inferred read-only
get_photos_for_place

Assets linked to a canonical place.

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]
url = "https://dayze.com/api/mcp/key"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "dayze": {
      "type": "http",
      "url": "https://dayze.com/api/mcp/key"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: dayze
Remote MCP URL: https://dayze.com/api/mcp/key

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": {
      "url": "https://dayze.com/api/mcp/key"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "dayze": {
      "type": "http",
      "url": "https://dayze.com/api/mcp/key"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "dayze",
  "transport": "streamable-http",
  "url": "https://dayze.com/api/mcp/key"
}
MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for dayze.com was fetched 2026-08-23T20:03:28.695Z and is being refreshed.

Trust status Trusted

dayze.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

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