Skip to main content
Glama
cwen0224

omnistate

by cwen0224
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to omnistate

No user-submitted related servers found.

    Related Servers

    • Hoplon

      justguy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents and hosts to enforce deterministic repository boundaries via MCP, providing structured reads, supervised edits, snapshots, audits, and recovery with machine-readable evidence.
      MIT

    • sofagent

      KongFangXun
      A
      license
      B
      quality
      B
      maintenance
      Commit-time audit engine for AI coding agents. Scans git diffs with 24 audit rules, writes HMAC-signed tamper-evident audit history, and ships MCP tools for governance aggregation.
      104
      55
      MIT

    • Project OS for Codex MCP

      gray451
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to read a project's Git-backed kickoff, acceptance criteria, handoff package, progress, and next step, and to append validated, audited progress events as project records. It provides short-lived scoped credentials and fail-closed tool allowlisting for safe, resumable AI-assisted development.
      -

    • Project OS for Codex

      jvasiliev12931
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to retrieve Git-backed project context, handoff packages, progress, and next steps, and to append validated progress events with matching project-record commits. This supports visible agent progress, resumable work, and safe handoffs while keeping high-risk actions outside the MCP surface.
      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

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools map cleanly to a transaction lifecycle (init, begin, step, audit, finish, abort) with status and inspect_diff as read-only helpers. The main possible confusion is audit vs inspect_diff, both involving scope/anti-laziness checks, and init vs begin, but descriptions distinguish state-changing versus read-only and setup versus transaction start.

    Naming Consistency4/5

    All tools share the omnistate_ prefix and snake_case formatting, making the set highly predictable. Minor deviations exist: status is a noun while most names are verbs, init is abbreviated, and step is less action-specific, but the convention remains readable.

    Tool Count5/5

    Nine tools fit comfortably within the ideal 3-15 range for a transaction-governance server. Each tool corresponds to a distinct lifecycle stage or helper, with no obvious filler.

    Completeness4/5

    The surface covers setup, transaction start, progress recording, auditing, commit clearance, abort/rollback, status, diff inspection, and rule explanation. A minor gap is that archived immutable snapshots are created but no tool lists or retrieves transaction history or past snapshots.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources