Skip to main content
Glama
SweetKenneth

Counterfactual Immune Forge

by SweetKenneth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Counterfactual Immune Forge

No user-submitted related servers found.

    Related Servers

    • airlock

      Rohit-ATS
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to open production change dossiers, attach proof certificates, and request human approval through a secure, unforgeable gate—ensuring no irreversible change can proceed until it has been verified against a sandboxed shadow copy.
      140
      1
      MIT
    • weavatrix-quality by Weavatrix

      weavatrix-qualityofficial

      Weavatrix
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to turn OpenSpec intents and Git changes into revision-bound proofs by planning, selecting, and running the smallest safe protection set, then verifying composite verdicts and explaining evidence or unresolved states.
      MIT

    • mcp-nixreview

      pete-builds
      A
      license
      Not graded
      quality
      A
      maintenance
      A safety gate for agent-proposed NixOS configuration changes, grading security-relevant option deltas, attesting closures for vulnerabilities, and requiring human approval with a tamper-evident audit ledger.
      MIT

    • dsh-artifact-promotion-proof

      dongsheng123132
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables offline, deterministic verification that one immutable artifact followed a declared build-to-production promotion chain, using only hash-based evidence and failing closed on incomplete or nonconformant gate records.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation in the evidence lifecycle: adjudicate an episode, verify episode evidence, export lineage, verify lineage, describe policy, and reset session state. The two verification tools are clearly separated by object (episode vs. lineage).

    Naming Consistency5/5

    All tools use snake_case with a verb-first pattern: adjudicate_, verify_, export_, describe_, reset_. Deviations are minor and still fit the same convention.

    Tool Count5/5

    Six tools is well-scoped for this specialized adjudication and verification server. Each tool has a clear, non-redundant role in the workflow.

    Completeness5/5

    The surface covers the full lifecycle: adjudicate and seal an episode, verify its evidence, export and verify lineage, inspect policy, and reset session state. No critical operation appears missing for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources