Skip to main content
Glama
utk2103

jev-studio

by utk2103
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to jev-studio

No user-submitted related servers found.

    Related Servers

    • jev-mcp

      walidboulanouar
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that exposes eleven typed decision tools—check, choose, score, judge, route, triage, guard, grep, rank, compact, and ask—so agents can make fast, branchable yes/no, option-pick, score, and filtering decisions on text via TypeSafe's Jev model.
      20 npm
      2
      MIT

    • use-jev

      silkyland
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable agents to run TypeSafe's Jev judgment model as typed yes/no, choice, and score tools, with calibrated probabilities, confidence thresholds, escalation for uncertain or non-judgment tasks, and an optional action gate that fails open.
      1
      MIT

    • jev-answers

      AmooEbrahim
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to send files, globs, directories, and typed yes/no, choice, or score questions to TypeSafe's Jev decision model, returning the provider's raw probabilistic answer unchanged. Each request is stored in its own session folder holding the collected inputs, exact request body, and response.
      627 npm
      1
      MIT

    • mcp-jev

      Chrishow2
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to get machine-readable yes/no, choice, and score decisions from TypeSafe Jev, bridging fast classification to Cursor and other clients.
      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

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlapping purposes. The tool's purpose is singular and unambiguous.

    Naming Consistency5/5

    The single tool name 'jev_instructions' follows a clear pattern with a prefix and a noun. Since there is only one name, there are no inconsistencies to evaluate.

    Tool Count2/5

    A single tool feels too thin for a server named 'jev-studio', which implies a broader set of capabilities. Even for a specific function, one tool is on the extreme low end and likely insufficient for common agent workflows.

    Completeness4/5

    The tool covers all mentioned intensity levels (lite, full, ultra) and fulfills its stated purpose of returning a ruleset. No obvious gaps exist for this narrow scope, though additional related operations (e.g., listing available intensities) could enhance completeness.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources