Skip to main content
Glama
edwinzhu68-ops

jev-kit

by edwinzhu68-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to jev-kit

No user-submitted related servers found.

    Related Servers

    • Thot

      nobodyohm-web
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables proof-backed code audit via MCP tools for AST-based code maps, symbol lookup, callers, audit commands, and persistent verdict memory.
      MIT

    • CodeGraph

      Phoenixrr2113
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search code by meaning, explore codebase structure, store and query knowledge with temporal facts, and read source code through a set of MCP tools.
      267 npm
      7
      MIT

    • blastmap

      manorfm
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to index codebases into a queryable knowledge model and ask for the smallest architectural surface a task likely touches, with evidence, confidence, and freshness, via MCP tools.
      Apache 2.0

    • 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
    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.4/5.0

    Scored across 13 tools

    Disambiguation3/5

    Several tools occupy overlapping 'select/judge without executing' territory (jev_step vs jev_tool_route vs jev_route_skills; jev_review vs jev_gate; jev_evaluate vs jev_verify). The caveats in the descriptions help, but the boundaries are subtle and an agent would need to read closely to avoid misselection.

    Naming Consistency4/5

    All tools share the jev_ prefix and mostly follow a snake_case verb_noun pattern like jev_prepare_work and jev_route_skills. A few outliers such as jev_coding_loop, jev_tool_route, and jev_step break the verb-first pattern, but the naming is still predictable and readable.

    Tool Count4/5

    13 tools is a reasonable size for a workflow-oriented kit and each tool has a distinct stage in the process. It is slightly heavy because some tools are narrowly scoped variants of similar actions, but none feel redundant enough to remove.

    Completeness4/5

    The tool surface covers preparation, routing, evaluation, review, verification, screening, ranking, gating, code brief generation, and evidence collection, which matches the stated host-advisory role. Execution is deliberately left to the host, so major workflows do not dead-end. Missing task/state management seems out of scope for this kit.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources