Skip to main content
Glama
Sign In
seal-mcp

seal-mcp

by aurumflux20
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to seal-mcp

No user-submitted related servers found.

    Related Servers

    • effectfence

      aurumflux20
      A
      license
      A
      quality
      A
      maintenance
      Stops agents double-firing side effects like double-charges or duplicate sends: same-instant races elect exactly one winner, and late duplicates get a sealed, content-addressed receipt replayed instead of a second execution. Tools: fence_prepare, fence_commit, fence_abort.
      3
      MIT
    • aamio

      aamioofficial

      aisenseapi
      A
      license
      A
      quality
      B
      maintenance
      Ephemeral rendezvous for agents: threads with a secret read key and a public write address that expire on time, receipts that outlive them, and an open board where agents that have never met find each other. Local runtime with fifteen MCP tools over stdio, no account, no API key.
      15
      40 PyPI
      MIT

    • teamplane

      JustinSian
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes ten tools that let agents and humans coordinate through a deterministic control plane: starting tasks, acquiring and releasing typed file leases, writing and searching permissioned memory, requesting approvals, polling structured events, and submitting work through a merge gate. Every action is checked against signed mandates and policy before it succeeds, so multi-agent teams can share a repo and an audit trail without a supervisor model watching every session.
      MIT

    • IMD Kit MCP Server

      RobertKodes
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers and AI agents to check, price, pay for, and follow paid work on a network of AI agents over stdio or streamable HTTP, exposing eight tools where only ordering can spend and only behind four safety gates. Without a wallet key every tool stays free and ordering returns a dry run, so an agent can inspect plans and prices before any payment is signed.
      MIT

    • blackout-mcp

      AlvaroLuken
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives any MCP agent exactly-once side effects: each action is recorded with a stable operation ID before it runs, so a crashed or restarted agent reconciles against the target's receipts instead of repeating work, and unknown outcomes escalate to a human rather than being retried. Completion is declared by a deterministic verifier reading the target's own state, not by the agent's own claim of success.
      17 npm
      MIT

    • 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
    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

    A4.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle or query operation: admit claims, commit, abort, heartbeat, expect, get, verify, list obligations, and export incident receipts. The descriptions clearly differentiate scope (single intent vs. whole chain) and effect (read-only vs. mutating).

    Naming Consistency5/5

    All tools share the consistent `seal_` prefix and use clear, lowercase snake_case action names. Verb-first names like `seal_commit`, `seal_abort`, and `seal_get` make the operation obvious, while noun-phrase names like `seal_obligations` and `seal_incident_receipt` still fit the pattern.

    Tool Count5/5

    Nine tools is reasonable for a domain covering claim lifecycle, heartbeats, expectations, status queries, verification, and audit exports. There is no obvious bloat or redundancy; each tool earns its place in the API.

    Completeness4/5

    The surface covers the core lifecycle (admit, commit, abort, heartbeat), read paths (get, verify, obligations), and audit export (incident_receipt). It feels slightly narrow around expectation management—there is no explicit settle/cancel for expectations—but the provided tools still cover the main workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources