Skip to main content
Glama
equinoxaifinance-rgb

Living Stack MCP — Retired Beta Listing

by equinoxaifinance-rgb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Living Stack MCP — Retired Beta Listing

No user-submitted related servers found.

    Related Servers

    • Witness

      MaximilianoColoma
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides evidence-oriented MCP service for cryptographically identified agents, bounded public contracts, privacy-preserving records, and append-only audit.
      Apache 2.0

    • CONTINUUM

      Cyrax321
      A
      license
      Not graded
      quality
      A
      maintenance
      Universal verifiable recovery for long-running AI agents with semantic checkpoints, idempotent action ledger and hash chained log as a deny by default MCP server. Framework agnostic with adapters for LangGraph, LangChain and OpenAI plus gateway and OTel.
      28
      Apache 2.0

    • CodexPro Runtime

      Menglook
      A
      license
      B
      quality
      B
      maintenance
      A local, evidence-driven MCP runtime and control plane for open-source maintainers that provides workspace-bounded tools including controlled file operations, command execution, validation primitives, durable execution records, and human review workflows via stdio and Streamable HTTP transports.
      33
      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

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource or lifecycle step: session status vs server status, context retrieval vs checkpoint loading, and trace report vs trace export are all clearly separated by their descriptions. No two tools appear to perform the same operation.

    Naming Consistency3/5

    All tools share the livingstack prefix and snake_case, but the object/verb order is inconsistent: session_start, context_put, and checkpoint_save are noun-verb while retrieve_context, authorize_action, and check_claim are verb-noun. Status, session_status, trace_report, and trace_export are noun-like, so no single naming pattern dominates.

    Tool Count5/5

    Fourteen tools is within the ideal 3-15 range and each tool maps to a distinct capability class such as session lifecycle, context management, authorization, checkpointing, tracing, and release verification. The count feels deliberately scoped rather than padded.

    Completeness4/5

    The core session, context, authorization, outcome, checkpoint, trace, and release verification lifecycle is well covered. Minor gaps exist: context_put mentions independent reverification but no explicit tool exposes that operation, and there is no session-listing or session-deletion tool beyond close.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources