Skip to main content
Glama
aurumflux20

effectfence

by aurumflux20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to effectfence

No user-submitted related servers found.

    Related Servers

    • seal-mcp

      aurumflux20
      F
      license
      A
      quality
      A
      maintenance
      Exactly-once execution for irreversible agent actions: an agent claims the right to run an effect, and a retry after a lost response returns the sealed result instead of charging again. 12 tools over stdio, including a gateway mode where the agent holds a single-use ticket and never the provider key.
      9
      17 PyPI
      -

    • 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
    • genpark-distributed-two-phase-commit-coordinator-skill by alphaparkinc

      genpark-distributed-two-phaseofficial

      alphaparkinc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to coordinate atomic distributed transactions across a swarm through a prepare/vote phase, unanimous commit-or-abort consensus, quorum validation, and failure recovery. It also layers in vector-clock causal stamping, LWW CRDT reconciliation, and gossip dissemination so multi-node state converges deterministically without external dependencies.
      7
      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

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct role in the effect lifecycle: prepare initiates, commit reports success, abort reports failure. There is no overlap or ambiguity among them.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'fence_' + verb (prepare, commit, abort). This is uniform and predictable.

    Tool Count5/5

    Three tools is precisely right for the narrow, well-defined domain of effect fencing. Each tool is necessary and none is superfluous.

    Completeness5/5

    The set covers the full lifecycle: prepare to request permission, commit for success, abort for failure. There are no obvious gaps for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources