Skip to main content
Glama
SweetKenneth

security-genome-reactor

by SweetKenneth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to security-genome-reactor

No user-submitted related servers found.

    Related Servers

    • genetic-mcp

      andrasfe
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables evolutionary idea generation using genetic algorithms with LLM workers, multi-objective fitness evaluation, and advanced genetic operations.
      1
      MIT

    • EPOCH-MCP

      Sarthaksulkhlan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to drive governed software changes, measure trajectory and boundary integrity after each mutation, surface drift and invariants, investigate incidents, and compare counterfactual futures before approving a change.
      9 npm
      2
      MIT

    • Counterfactual Immune Forge

      SweetKenneth
      A
      license
      A
      quality
      A
      maintenance
      Enables agents and security automation to adjudicate proposed defense mutations against a sealed, canonicalized attack scenario, enforcing reproduction, impact-screening, regression, and proven-improvement gates before promoting at most one candidate. Every verdict, rejected candidate, and rejection reason is sealed into a recomputable SHA-256 Merkle evidence root and hash-linked lineage that can be independently verified without trusting the server.
      6
      MIT

    • EPOCH-MCP

      vighriday
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to govern evolving software by measuring trajectory, drift, invariants, and incidents, and by forking and measuring alternative futures before adoption.
      9 npm
      MIT
    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

    B3.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clearly distinct step in the genome workflow: inferring phenotypes, seeding candidates, evolving generations, planning trials, and tracing lineage. There is no meaningful functional overlap between any two tools.

    Naming Consistency3/5

    All names share the genome_ prefix and use snake_case, which is readable and recognizable. However, the pattern is mixed: genome_infer_phenotypes is verb-object, genome_seed and genome_evolve are bare verbs, while genome_trial_plan and genome_lineage are noun phrases.

    Tool Count5/5

    Five tools is well-scoped for this specialized domain. Each tool represents a meaningful stage in the reactor lifecycle without redundant or filler operations.

    Completeness5/5

    The set covers the core genome lifecycle: infer phenotypes, seed candidates, evolve generations, produce trial plans, and inspect lineage. Fitness is intentionally caller-supplied, so no evaluation tool is a necessary gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources