Skip to main content
Glama
amadeus-ex-machina

christina

by amadeus-ex-machina
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to christina

No user-submitted related servers found.

    Related Servers

    • Cordyceps Search

      ghassenTn
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables developer agents to perform semantic codebase search, dependency and impact analysis, cross-file refactoring, and full-stack API tracing through a unified query DSL over a high-performance graph engine.
      -

    • CogniLayer

      CyberdaemonAI
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent cross-session AI memory, code graph analysis, and subagent context compression so coding agents can resume work instantly and avoid re-reading the codebase.
      Elastic 2.0

    • onto-agent

      rinDBeans
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI coding agents with an embedded knowledge graph and architecture governance tools, enabling blast radius analysis, compliance checks, and smart context extraction from codebases.
      Apache 2.0

    • MindGraph

      dycm8009
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and analyze code across multiple repositories through a unified knowledge graph, with tools for symbol search, impact analysis, and graph algorithms.
      17 npm
      MIT

    • hive-memory

      moonx010
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with persistent, graph-connected memory across projects, enabling cross-project context retrieval via synaptic connections and hybrid search.
      6 npm
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a completely different subsystem: static code analysis, sandboxed execution, semantic memory, and concurrency/blackboard coordination. There is no overlap or plausible confusion between them.

    Naming Consistency4/5

    All tools follow a readable two-part snake_case format with domain-specific prefixes. However, the suffixes mix verbs (query, execute, evolve) with a noun (blackboard), creating a minor deviation from a fully uniform pattern.

    Tool Count5/5

    Four tools is a reasonable, focused count for a server whose scope appears to be a coordinated agent runtime: analyze, execute, remember, and coordinate. Each tool earns its place and none feel redundant.

    Completeness4/5

    The tool surface covers the major capabilities one would expect from this kind of system: code understanding, safe execution, memory persistence, and shared-state coordination. There are minor gaps such as explicit file/API interaction, but the broad sub-operations embedded in each tool make the overall surface feel fairly complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources