Skip to main content
Glama
minhgv

jev-mcp

by minhgv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to jev-mcp

No user-submitted related servers found.

    Related Servers

    • jev-mcp

      arunav25
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to call TypeSafe's JEV classifier and receive structured, typed judgments with probabilities for binary, choice, and scoring questions.
      MIT

    • gitworthy

      trippyogi
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to scout, rank, and preflight software work before implementation, returning evidence-backed ACT, VERIFY, or SKIP decisions for issues and pull requests.
      28 npm
      2
      MIT

    • BountyVerdict Agent Decision

      cristianmoroaica
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides paid decision APIs for autonomous coding agents to diagnose GitHub Actions failures, classify flaky tests, check MCP tool drift, audit agent instructions, and compare bounties.
      MIT
    • Nauro by Nauro-AI

      Nauroofficial

      Nauro-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      The decision system for agentic engineering: keeps your project's decisions, rationale, and rejected paths in plain files and surfaces them to AI coding agents before they plan or change code.
      10
      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

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool has a clearly defined job—risk, classification, verification, review, screening, ranking—so they are mostly easy to distinguish. The main ambiguity is jev_evaluate, which is intentionally an escape hatch and can conceptually overlap with any of the other tools, though its description frames it as a fallback.

    Naming Consistency4/5

    All tools share the jev_ prefix and use snake_case, making the set feel consistent. The only deviation is jev_coding_loop, which is a noun-style name rather than a verb_noun pattern like assess_change_risk or classify_issue.

    Tool Count5/5

    Nine tools is well-scoped for a decision-support/evaluation server. Each tool addresses a distinct stage in the workflow—screening, risk assessment, review, verification, ranking, and a general escape hatch—so none feels redundant or excessive.

    Completeness5/5

    The tool surface covers the full evaluation lifecycle for the stated domain: risk assessment, issue classification, requirement checking, coding-loop guidance, diff review, claim verification, text screening, and ranking. The escape-hatch jev_evaluate also prevents dead ends for questions that don't fit an existing recipe.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources