Skip to main content
Glama
Sign In
chrysalis-mcp

chrysalis-mcp

by ancrz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to chrysalis-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-engram

      shuruheel
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to build and explore a cognitive neuroscience-inspired knowledge graph with SQLite, supporting search, graph traversal, temporal sequences, and structured reasoning.
      24
      MIT

    • Verantyx Vera MCP Server

      Ag3497120
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides LLM agents with hallucination-free external memory and knowledge tools, including ask, remember, forget, math, and code reasoning, with deterministic, traceable outputs.
      MIT

    • Cortex Intelligent

      adyoi
      A
      license
      C
      quality
      B
      maintenance
      Enables ordinary LLMs to be augmented fully offline — with no API keys or external services — through model-aware guardrails, exemplar retrieval, structured self-critique, compliance scoring, and an allowlisted verification runner. Also provides hybrid knowledge-base search, decaying long-term memory, and persistent plan/task management across 54 MCP tools usable from any MCP client such as OpenCode, Claude Desktop, Cursor, or VS Code.
      62
      MIT

    • Memento

      scrypster
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent memory for AI tools by building a local knowledge graph from conversations, enabling cross-session recall and context awareness without cloud dependencies.
      9
      MIT

    • Claude Soul

      SalmaMaxwell
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables persistent cross-session memory, correction-pattern tracking, and self-evolving behavioral frameworks, so past facts and decisions stay searchable by meaning and recurring mistakes fade over time. Runs entirely locally through 15 MCP tools plus hooks, with optional semantic search via Ollama embeddings and no cloud or API key required.
      6 npm
      MIT

    • Logica Mind

      Rovemark
      A
      license
      Not graded
      quality
      D
      maintenance
      Long-term memory for AI agents over MCP — episodic + semantic memory, a temporal knowledge graph, and a dialectic user model, exposed as 32 tools (recall, remember, context, graph, dreaming, peers). Zero dependencies, runs fully offline; leads the LoCoMo benchmark at ~35x fewer LLM calls.
      2
      Apache 2.0
    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.7/5.0

    Scored across 1 tool

    Disambiguation3/5

    With a single tool there is no inter-tool overlap, so classic misselection risk is eliminated. However, the ambiguity is pushed inward: the domain/action/params space is opaque from the tool listing, so an agent cannot tell what operations exist or which action to pick without first making an exploratory meta.schema or meta.discover call.

    Naming Consistency3/5

    The lone tool name 'chrysalis' matches the server and is not inconsistent with anything, but it is an opaque noun with no verb_noun convention to establish predictability. The actual naming surface (domain and action identifiers) is not visible here, so consistency cannot be verified from the tool set.

    Tool Count3/5

    One tool is intentionally thin as a dispatcher pattern, which is a legitimate design, but by the rubric a single entry point is borderline and forces a discovery round-trip before any real work. It is not a trivial tool, so it avoids the worst score, but the surface is not self-evident from the count alone.

    Completeness3/5

    The tool advertises schema discovery, batching, verbosity levels, and advisory memory, which suggests a broad internal surface, but none of the actual domains or actions are enumerated so coverage cannot be assessed. Completeness is deferred to a runtime meta.schema call, leaving a potential dead end if discovery fails or is skipped.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources