Home / MCP registry index / com.dayze/life-context
Dayze — Life Context
com.dayze/life-context in the official MCP registry.
Endpoint https://dayze.com/api/mcp. Source: github.com/gohluke/dayze-mcp.
The registry describes it as: Life context for agents: get_context_pack + public notable packs. x402 + OAuth.
We read its 183 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
notable_search notable_profile notable_pack notable_pack_premium compare_lives get_life_context get_context_pack get_life_graph get_berklee_relationship_map get_person_neighborhood get_events get_people update_person update_notable log_food update_food delete_food attach_food_photo log_event update_event log_moment update_moment create_pending_reply get_pending_replies update_pending_reply resolve_pending_reply log_interaction delete_event log_favorite_song get_memories delete_memory merge_memory correct_memory_atom get_expenses resolve_person get_person_aliases list_contact_lists create_contact_list add_people_to_list remove_people_from_list get_person_transactions get_money_between_people get_person_interactions get_interactions explain_fact list_clarifications get_trackers reset_tracker search search_gmail list_gmail_accounts read_gmail_message read_gmail_attachment get_goals create_goal update_goal get_event_fact_source list_event_fact_corrections apply_event_fact_correction undo_event_fact_correction and 123 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-dayze-life-context)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| io.github.praneeth12098/x402-factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |