Skip to main content
Glama
SIDDARTHAREDDY8

dhp

by SIDDARTHAREDDY8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dhp

No user-submitted related servers found.

    Related Servers

    • everrun

      UcelX
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides durable mission state for AI agents, enabling crash-safe recovery, verified completion, and explicit reconciliation of uncertain side effects without duplicate or blind retries.
      4
      Apache 2.0

    • MCPX

      azazhang
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables durable, crash-safe control of long-running AI-agent workflows with idempotent operations and scope-aware reconciliation over MCP filesystem and execution tools.
      1
      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.
      24
      Apache 2.0

    • L-Dopa

      mshanghai570
      A
      license
      A
      quality
      C
      maintenance
      It enables AI agents to recover from failures by diagnosing issues, refocusing broad tasks, restoring session context, and managing retries safely with bounded memory and credential redaction.
      6
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target distinct protocol actions (claim, checkpoint, complete, recover, approve/deny), but several read/write or lifecycle pairs (claim vs recover, checkpoint vs last_checkpoint, record_effect vs effect_done, status vs approval_status) require careful reading. Descriptions clarify the boundaries, and no true duplicates exist.

    Naming Consistency4/5

    All names use a consistent dhp_ prefix and snake_case, which is easy to parse. The verb_noun pattern is not universal (heartbeat, status, health, approve, deny, dispatch, last_checkpoint), so it is mostly rather than perfectly consistent.

    Tool Count4/5

    18 tools is on the heavy side for a single protocol server, but each maps to a distinct lifecycle, safety, or observability concern (lease, checkpoint, effects, approvals, budget, capabilities). The surface is defensible, though it could likely be consolidated slightly.

    Completeness4/5

    Core durable handoff lifecycle (dispatch, claim, recover, checkpoint, complete), approvals, side-effect deduplication, budget tracking, and capability checks are all covered. Minor gaps remain, such as no explicit cancel/abandon handoff or list-handoffs operation, but agents can largely work around these via status and recover.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources