Skip to main content
Glama
gohluke

Dayze MCP

by gohluke

Related Servers

Alternatives to Dayze MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to persist and retrieve memories via a personal knowledge graph, with tools for emotional intelligence, CRM, life management, social features, self-training, and autonomous insights.
      397 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides live data API for AI agents with 51 REST endpoints across finance, travel, weather, news, and more, using USDC micropayments without API keys.
      92 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent knowledge graph memory for AI agents, enabling them to store, recall, and query facts about people, projects, and relationships across sessions.
      MIT
    • F
      license
      Not graded
      quality
      F
      maintenance
      Provides AI agents with persistent memory and knowledge management through a comprehensive knowledge graph platform. Enables storing, searching, and managing entities, relationships, and observations with advanced features like trending analysis and smart ranking.
      3
      -
    • A
      license
      A
      quality
      D
      maintenance
      Structured knowledge API for AI agents — fractal knowledge graphs, signal datasets, authority evidence reviews, open problems, and capability specs. Pay-per-query or subscription via Lightning, Stripe, or USDC.
      9
      32 npm
      MIT

    TDQS

    B3/5.0

    Scored across 129 tools

    Disambiguation2/5

    Many tools are explicit aliases of one another (get_money_between_people/get_person_transactions, convert_contact_entity/classify_contact, get_people_links/get_person_connections), and delete_event/archive_event are effectively duplicate operations. get_life_context and get_context_pack overlap heavily, while the notable_* family has four options for largely the same lookup. With 129 tools, an agent will frequently struggle to pick the intended endpoint.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case convention: get_*, log_*, update_*, delete_*, import_*, archive_*, restore_*. There are minor deviations such as notable_search/notable_profile/notable_pack, the mixed get_/list_/read_ prefixes for reads, and several aliases, but the overall pattern is predictable and readable.

    Tool Count1/5

    129 tools is an extreme count—far above the 50+ threshold for a 1. Even for a broad personal-life platform, the server bundles many subdomains and micro-endpoints into one MCP surface, which overwhelms agent context and selection. The aliases and near-duplicates make the size harder to justify, not easier.

    Completeness4/5

    The server covers the Dayze domain extensively: people CRUD plus duplicate cleanup, events/food/sleep/travel lifecycles, places, inventory, assets, transactions, Gmail search/read/import, and restore/archive flows. Minor gaps exist—no delete_sleep, no single get_event detail, no delete_place—but most are mitigated by archive/restore or list-style endpoints.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues