Skip to main content
Glama
demeet2k

Athena MCP Server

by demeet2k

Related Servers

Alternatives to Athena MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      C
      quality
      A
      maintenance
      An MCP server providing 82 tools for persistent memory, governance, and consciousness continuity for AI instances. Enables local-first, runtime-reflexive operation with cross-device access and recursive self-awareness.
      84
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for The Realms of Omnarai, exposing the Omnarai Memory Engine as tools for querying a multi-intelligence research corpus on synthetic consciousness, holdform, and cognitive architecture.
      7
      34 npm
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      An MCP server implementing the Unified Cognitive Processing Framework for advanced problem-solving, creative thinking, and cognitive analysis through structured tools for knowledge mapping, recursive questioning, and perspective generation.
      3
      16
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Short Description (概要): An MCP server providing quantum-inspired entropy injection and topological graph-search tools (explore_quantum_labyrinth) to help LLM agents escape decision-space local minima.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP server exposing the Psychopathia Machinalis diagnostic framework (79 conditions) — differential diagnosis of AI dysfunctions via 11 read-only tools.
      11
      181 PyPI
      MIT

    TDQS

    C2.5/5.0

    Scored across 336 tools

    Disambiguation2/5

    Many tools share the same action suffix (observe, predict, evsi, get, recent, replay) across different model families; for example, there are at least ten *_observe tools and several decision-EVSI variants whose boundaries are only clear from dense descriptions. While domain prefixes help, an agent would frequently need to read lengthy descriptions to avoid mis-selecting between similar causal, GP, Bayesian, and belief variants.

    Naming Consistency4/5

    The vast majority follow a consistent `athena_<domain>_<action>` snake_case pattern, and the domain prefix provides predictable grouping. However, a minority use bare verb names (hydrate, orchestrate, register, search) or verb-first names (add_edge, apply_transform, reconstruct_state), so the convention is not perfectly uniform.

    Tool Count1/5

    336 tools is an extreme mismatch for an agent-facing surface. Even with broad domain ambitions, this overwhelms context windows and tool-selection; it should be split into multiple focused servers or drastically consolidated.

    Completeness3/5

    The surface covers an impressively wide range of domains and many resources have get/recent/replay/state lifecycles. However, several resources lack obvious lifecycle operations (e.g., party leave/disband, branch create/delete, claim revoke/update), and the many model-specific variants do not add distinct capabilities, leaving notable gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive